Home
HCL Workload Automation for Z
Welcome to the HCL Workload Automation for Z documentation, where you can find information about how to install, maintain, and use the product.
Scheduling End-to-end with z-centric Capabilities
Defining and managing jobs
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 directory. The default name is filewatchdb.

HCL Workload Automation for Z
Welcome to the HCL Workload Automation for Z documentation, where you can find information about how to install, maintain, and use the product.
- 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
  - About this publication
  - Configuring
  - Customizing the HTTP connections
    The communication between the HCL Workload Automation Agents and the HCL Workload Automation for Z controller is direct, through the HTTP or HTTPS protocol.
  - Defining user IDs and passwords with the USRREC statement
    Use the USRREC initialization statement to define the passwords for the users who need to schedule jobs to run on Windows™ workstations. You do not need to do this if you run native job types on non-Windows workstations.
  - Defining variables and passwords for local resolution
  - Defining and managing HCL Workload Automation Agent workstations in the database
    After defining the destinations of your HCL Workload Automation Agents, you need to define the HCL Workload Automation Agents as HCL Workload Automation for Z computer automatic workstations.
  - Defining and managing dynamic workstations
    When you add dynamic capabilities to your environment, you can schedule your workload dynamically.
  - Setting the security features
  - Defining and managing jobs
    - Defining jobs from the Dynamic Workload Console
      How to define a new job definition using the Dynamic Workload Console.
    - Defining a job in the JOBLIB data set
      You define the jobs to be run on HCL Workload Automation Agent workstations in a job definition member of the JOBLIB data set. In the JOBLIB member, you can either define the job contents or invoke a script or an executable that is stored locally on the HCL Workload Automation Agent workstation.
    - Using variable substitution
      The variable substitution mechanism that is used in HCL Workload Automation for Z native job types works the same way when scheduling jobs on HCL Workload Automation Agents. The variable substitution mechanism changes when you define job types with advanced options, such as Java™ jobs that run a Java class, or file transfer jobs that transfer files to and from a server, to name a few. These types of jobs are created and edited using the Dynamic Workload Console.
    - 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 directory. The default name is filewatchdb.
    - Checking for file changes with filemonitor
    - Promoting critical jobs
      An overview of the mechanism that is behind the promotion of critical jobs, or of their predecessors, running on HCL Workload Automation Agents, including pools and dynamic pools.
    - Killing operations
  - Administering IBM i dynamic environment
    On overview on how to administer the HCL Workload Automation IBM i dynamic environment.
  - Monitoring and recovering jobs
  - Running a script when a job completes
  - Viewing the job logs from the host
    An overview on how to view or retrieve the job logs issued in the z-centric environment and how to attach a header with job run information on top of each log.
  - Troubleshooting
    Troubleshooting agent problems
  - Configuring to schedule J2EE jobs
  - Security order of precedence used for the execution of J2EE tasks
  - Configure to schedule job types with advanced options
  - Managing return codes
  - Collecting job metrics
- Quick Reference
- Diagnosis Guide and Reference
- Workload Automation Programming Language for z/OS User's Guide and Reference
- Driving HCL Workload Automation for Z

Maintaining the filewatch log database

The log database is used to store filewatch activity data. This log is located in the TWA_home/TWS 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.

Syntax

filewatchdb -v | -u | -?

filewatchdb -c[ondition] condval
[-f[ilename] file_path
[-dat[abase] log_extension]

The arguments are not positional.

Arguments

-v

Returns the command version and exits.

-u

Returns command usage information and exits.

-?

Same as -u

-condition

The condition to be checked. Valid values are:

bld| build: Rebuild the log database.
dlt | delete: Delete the log database record corresponding to the filename argument value.
gls | getLastStatusChange: Gets and returns the log database record corresponding to the filename argument value.

-filename

Use this argument to delete the entry corresponding to the specified value. You can embed blank or special characters, by using double quotation marks. Use * as wildcard character. This argument is required if you specify dlt (delete) or gls (getLastStatusChange) as condition value.

-database

Optional extension of the log database to be accessed. If you specify this value, filewatchdb accesses the TWA_home/TWS/filewatchdb.log_extension database, otherwise TWA_home/TWS/filewatchdb is accessed.