Welcome
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.
Scheduling End-to-end with Fault Tolerance Capabilities
Managing end-to-end scheduling
Defining file dependencies to check for file changes
Maintaining the filewatch log database
The log database is used to store filewatch activity data. This log is located in the TWA_home/TWS/mozart directory. The default name is filewatchdb.

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
      - Syntax
      - Arguments
      - Maintaining the filewatch log database
        The log database is used to store filewatch activity data. This log is located in the TWA_home/TWS/mozart directory. The default name is filewatchdb.
        Syntax
        Arguments
      - Usage Notes
      - Examples
    - 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
    - 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

Maintaining the filewatch log database

The log database is used to store filewatch activity data. This log is located in the TWA_home/TWS/mozart directory. The default name is filewatchdb.

When processing a file, filewatch uses it to store records with information about:

File name.
File status. The allowed values are Exist, Created, Running, Completed, RunningCompleted, or Deleted.
Date and time of file creation at the entry update time.
Date and time of the last file modification at the entry update time.
Date and time of the last entry update.

Note: The log contains only one entry for each file.

To maintain the log database, use the filewatchdb utility.