Workload Automation Restart Option for z/OS Schedulers Modernization Guide

Workload Automation Restart Option automates the process of restarting failed batch jobs, minimizing downtime and ensuring timely completion of critical processes. It integrates with existing Workload Automation and Job Management products.

The product can restart jobs at the point of failure, rather than from the beginning, saving significant processing time. This is particularly useful for long-running batch processes.

Workload Automation Restart Option was initially developed as UCC-11 by Uccel Corporation, demonstrating its long-standing presence and reliability in the market.

While specific command details require access to the product documentation, common operations include defining restart rules, monitoring job status, and initiating restarts. Configuration files define the restart behavior.

The product likely exposes APIs for integration with other systems, potentially including REST or SOAP interfaces. Specific API details would be found in the product's API documentation.

The architecture includes components for monitoring job execution, determining failure points, and initiating restart processes. Details on specific component names and communication protocols are available in the product's architectural documentation.

By automating restarts, Workload Automation Restart Option reduces manual intervention, freeing up operations staff for other tasks. This leads to improved resource utilization and reduced operational costs.

Ensuring timely completion of batch jobs is crucial for meeting SLAs and maintaining business continuity. The product helps minimize the impact of job failures on critical business processes.

Restarting jobs from the point of failure minimizes wasted processing time and resources, leading to cost savings and improved efficiency.

The product likely supports standard authentication methods such as LDAP or integration with z/OS security systems like RACF, ACF2, or Top Secret. Specific details are available in the security documentation.

Access control is likely managed through role-based access control (RBAC), allowing administrators to define roles with specific permissions for managing and monitoring restarts.

Audit logging capabilities track user actions and system events related to restarts, providing an audit trail for security and compliance purposes.

The product provides administrative interfaces, potentially including a CLI or web console, for configuring restart rules, monitoring job status, and managing user access. Specific details are available in the administration guide.

User management is typically handled through integration with z/OS security systems or through a dedicated user management interface within the product.

Monitoring and logging capabilities provide insights into job execution, restart activity, and system health. These logs can be used for troubleshooting and performance analysis.