Product requirements
This section contains links to the IBM® Workload Scheduler Download Documents, System Requirements, and Release Notes.
Fix Pack readmes
For the latest information about a Fix Pack, see the appropriate Readme File.
Product Library in PDF format
This section contains links to the PDF versions of all the publications provided in IBM Documentation for IBM Workload Automation.
Considerations for GDPR readiness
Overview
Mobile Applications Userʼs Guide
Dynamic Workload Console User's Guide
AI Data Advisor (AIDA) User's Guide
Scheduling Job Integrations with IBM Workload Automation
IBM® Workload Scheduler
Welcome to the IBM® Workload Scheduler documentation, where you can find information about how to install, maintain, and use IBM Workload Scheduler. The documentation has been updated for IBM Workload Scheduler Version 10.1 Fix Pack 6.
IBM® Z Workload Scheduler
Welcome to the IBM® Z Workload Scheduler documentation, where you can find information about how to install, maintain, and use the product.
- Memo to Users
- Program Directory
- Dynamic Workload Console Readmes
  For the latest information about a Dynamic Workload Console fix pack, see the appropriate Readme File.
- Planning and Installation
- Customization and Tuning
- Managing the Workload
  You can plan when and how your workload runs and manage it as part of a plan.
- Scheduling End-to-end with z-centric Capabilities
- Scheduling End-to-end with Fault Tolerance Capabilities
  - About this publication
  - Overview
    An overview of end-to-end scheduling with fault tolerance capabilities.
  - Installing
  - Customizing
  - Managing end-to-end scheduling
    - Defining fault-tolerant workstation jobs
    - Defining file dependencies to check for file changes
    - Creating and activating the current plan
      Daily planning is the process of producing and maintaining the current plan, which is the detailed schedule of the work that IBM Z Workload Scheduler will carry out on your system.
    - Controlling the distributed plan
      - Conventions used for the end-to-end scheduling plan
      - Controlling the plan with conman
        Use conman from the command line interface to start and stop processing, alter and display the production plan, and control workstation linking in a network.
      - Controlling the plan with the Dynamic Workload Console
        As an alternative to using conman, you can control and monitor the plan from a Dynamic Workload Console connected to an IBM Workload Scheduler workstation.
      - Killing jobs on standard agents
        Killing from ISPF
        Killing with the PIF
        Killing with the BCIT
        Killing with the OCL
    - Sizing event files on USS
    - Enabling time zones
      In an end-to-end network, use the CPUTZ keyword to set the local time zone of a workstation when you define the workstation with the CPUREC statement.
    - Switching to a backup domain manager
    - Collecting job metrics
  - Changing the topology of the network
- Quick Reference
- Diagnosis Guide and Reference
- Workload Automation Programming Language for z/OS User's Guide and Reference
- Driving IBM Z Workload Scheduler
Messages and Codes
Glossary
Installing IBM® Workload Scheduler
How to monitor your IBM® Workload Scheduler using the Dynamic Workload Console
How to create your scheduling environment using the Dynamic Workload Console
Notices

Killing jobs on standard agents

When a standard agent is connected to a domain manager, it is easy to kill jobs using the conman kill command from the domain manager. When the standard agent is connected directly to the end-to-end server (OPCMASTER), which does not run conman, you have other options to kill jobs or recovery jobs:

Use the Dynamic Workload Console, with either the Z connector or distributed connector.
Use the IBM Z Workload Scheduler interfaces: ISPF, program interface (PIF), batch command interface tool (BCIT), or control language (OCL).

This action can be taken only on STARTED jobs or recovery jobs that are in the EXECUTING status, so that their JOBID is known. The JOBID is required to identify the operation that is to be killed.

You can kill the same job, while it runs, as many times as required.