What infrastructure is required?

IWS/Graph requires IBM Workload Scheduler running on z/OS. It also needs a Microsoft Windows workstation to run the graphical interface. Communication between the workstation and the z/OS system is necessary.

Does this extend/enhance another product?

IWS/Graph enhances IBM Workload Scheduler by providing a graphical view of its configurations. It does not replace or duplicate the core scheduling functionality but rather provides a more user-friendly interface for managing and monitoring workloads.

How does this improve business efficiency?

IWS/Graph simplifies the management of complex IBM Workload Scheduler environments by providing a visual representation of schedules and dependencies. This can lead to improved efficiency, reduced errors, and faster problem resolution.

What is the business value of using IWS/Graph?

By providing a clear graphical view of workload dependencies, IWS/Graph helps organizations optimize their batch processing and reduce the risk of delays or failures. This can lead to improved service levels and reduced operational costs.

How does IWS/Graph help with user training?

IWS/Graph helps reduce the learning curve for new users of IBM Workload Scheduler by providing a more intuitive interface. This allows them to quickly understand and manage complex schedules, reducing the need for extensive training.

How does IWS/Graph ensure security?

IWS/Graph leverages the security features of IBM Workload Scheduler and z/OS. Access to scheduling information is controlled through the existing security mechanisms of these systems.

What authentication methods are used?

Authentication is handled by IBM Workload Scheduler and z/OS. IWS/Graph uses the existing authentication mechanisms to verify user identities before granting access to scheduling data.

What access control model is used?

Access control is managed through the Role-Based Access Control (RBAC) model in IBM Workload Scheduler. Users are assigned roles that determine their level of access to scheduling objects and functions.

What ongoing operational requirements exist?

IWS/Graph requires ongoing monitoring to ensure that the connection to IBM Workload Scheduler is maintained and that the graphical interface is functioning correctly. Regular maintenance may be needed to apply updates or fix any issues.

What level of technical expertise is required to implement it?

Implementing IWS/Graph typically requires technical expertise in both IBM Workload Scheduler and Microsoft Windows environments. Familiarity with z/OS security concepts is also beneficial.

What are common implementation challenges?

Common implementation challenges include configuring the communication between the Windows workstation and the z/OS system, ensuring proper security settings, and customizing the graphical display to meet specific user needs.

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

IWS/Graph

HORIZONT Active z/OS

Legacy Application/Data Access Administration Batch

Vendor

HORIZONT

Product Overview

IWS/Graph is an application that visualizes IBM Workload Scheduler configurations as graphs on Microsoft Windows workstations. It allows architects to see schedules and applications in a graphical format, making it easier to understand dependencies and workflows. This tool enhances the usability of IBM Workload Scheduler by providing a visual representation of batch schedules and application dependencies, aiding in the design and optimization of workload automation processes.

From an architectural perspective, IWS/Graph runs on a Microsoft Windows workstation and connects to IBM Workload Scheduler on z/OS. The z/OS component typically runs within an LPAR and relies on z/OS subsystems for communication and data access. The main components include the IWS/Graph client on the Windows workstation and the communication interface to the IBM Workload Scheduler server on z/OS.

The client retrieves data from the server and displays it graphically. This architecture allows for a clear separation of concerns, with the visualization component running on a separate platform from the core scheduling engine. Access control is managed through the Role-Based Access Control (RBAC) model in IBM Workload Scheduler.

Frequently Asked Questions

What does IWS/Graph do?

IWS/Graph visualizes IBM Workload Scheduler configurations as graphs on Microsoft Windows workstations. It provides a graphical representation of schedules and applications, making it easier to understand dependencies and workflows.

Is this a system, application, or tool?

IWS/Graph is an application that enhances the usability of IBM Workload Scheduler. It provides a graphical interface to visualize and manage batch schedules and application dependencies.

What types of organizations use this?

Organizations that use IBM Workload Scheduler on z/OS and need a visual representation of their schedules and application dependencies benefit from IWS/Graph. These organizations are often in industries such as banking, finance, insurance, and retail.

When should we consider IWS/Graph?

Consider IWS/Graph when you need a graphical view of your IBM Workload Scheduler environment to simplify understanding and management of complex schedules and application workflows. It is especially useful when troubleshooting or optimizing batch processing.

What are the alternatives to IWS/Graph?

Alternatives to IWS/Graph include other workload automation visualization tools or custom scripting to extract and display schedule information. However, these alternatives may not offer the same level of integration with IBM Workload Scheduler or the same ease of use.

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

Are You a Vendor? Claim Your Listing

IWS/Graph

Product Overview

Frequently Asked Questions

What does IWS/Graph do?

Is this a system, application, or tool?

What types of organizations use this?

When should we consider IWS/Graph?

What are the alternatives to IWS/Graph?

What infrastructure is required?

For mainframe products: Does this run in an LPAR?

Does this extend/enhance another product?

What are the main system components?

How does this improve business efficiency?

What is the business value of using IWS/Graph?

How does IWS/Graph help with user training?

How does IWS/Graph ensure security?

What authentication methods are used?

What access control model is used?

What ongoing operational requirements exist?

What level of technical expertise is required to implement it?

What are common implementation challenges?

Related Products

More from HORIZONT

DSN/Change

IWS/Audit

IWS/BatchAD

IWS/BatchCP

IWS/WebAdmin

ProcMan

Similar Products

_beta access admin

_beta access audit

_beta access easy

_beta access monitor

ACI Proactive Risk Manager

Adabas Manager

Help Improve This Directory

Share Your Product Experience