Home
HCL Workload Automation
Welcome to the HCL Workload Automation documentation, where you can find information about how to install, maintain, and use HCL Workload Automation. The documentation has been updated for HCL Workload Automation Version 9.5 Fix Pack 6.
User's Guide and Reference
Getting reports and statistics
Command descriptions
Rep8

HCL Workload Automation
Welcome to the HCL Workload Automation documentation, where you can find information about how to install, maintain, and use HCL Workload Automation. The documentation has been updated for HCL Workload Automation Version 9.5 Fix Pack 6.
- Fix Pack readmes
  For the latest information about a Fix Pack, see the appropriate Readme File.
- Planning and Installation
- User's Guide and Reference
  - HCL Workload Automation
  - Understanding basic processes and commands
  - Configuring the job environment
  - Managing the production cycle
  - Using workload service assurance
    Workload service assurance is an optional feature that provides the means to flag jobs as mission critical for your business and to ensure that they are processed in a timely manner. Using this function benefits your scheduling operations personnel by enhancing their ability to meet defined service levels.
  - Customizing your workload using variable tables
    This chapter introduces the concept of variable tables to group global parameters, from now on called variables, to customize your workload.
  - Condition-based workload automation
  - Running event-driven workload automation
  - Defining objects in the database
  - Managing objects in the database - composer
  - Managing workload applications
    Workload applications can be created and then exported so that they can be shared with other HCL Workload Automation environments. In the new environment, the workload application can be subsequently updated, replaced, or deleted.
  - Managing objects in the plan - conman
  - Monitoring with Prometheus
    Access metrics that provide insight into the state, health, and performance of your workload environment and infrastructure.
  - Predicting job duration
  - Extending HCL Workload Automation capabilities
    You can extend HCL Workload Automation capabilities by integrating with IBM and third-party products, such as IBM Sterling Connect:Direct or MS SQL. This integration allows you to easily start HCL Workload Automation jobs on external products, while using HCL Workload Automation scheduling capabilities. HCL Workload Automation also provides jobs that perform everyday operations, such as file transfer and web services, and utility jobs that automate and simplify operations such as the centralized agent update.
  - Managing dynamic scheduling
    This section explains how you can manage dynamic scheduling capabilities in your environment to schedule both existing HCL Workload Automation jobs and job types with advanced options, both those supplied with the product and the additional types implemented through the custom plug-ins.
  - Using utility commands
  - Using utility commands in the dynamic environment
  - Getting reports and statistics
  - Managing time zones
  - Defining access methods for agents
  - Managing internetwork dependencies
  - Applying conditional branching logic
    With HCL Workload Automation you can define jobs to run when and as often as necessary. Sometimes some jobs might have to wait for other jobs to finish successfully before they start. Add even more flexibility to your job flows by choosing which job to run depending on the result of the job status or output of a previous job. Whenever you have conditions that specify whether or not a segment of your job flow should run, then that is a conditional dependency.
  - Defining and managing cross dependencies
  - Managing an IBM i dynamic environment
  - Event-driven workload automation event and action definitions
  - Job Submission Description Language schema reference
    This reference section specifies the semantics and structure of the Job Submission Description Language (JSDL) that apply specifically for use with dynamic workload broker. The JSDL schema is used to describe the job requirements for submission to resources. dynamic workload broker analyzes the IT environment and assigns the best available resource to run the job, based on the requirements you specify.
  - Quick reference for commands
  - Accessibility
- Administration Guide
- Scheduling with the Agent for z/OS
- Database Views
- Integrating
- High Availability Cluster Environment
- Driving HCL Workload Automation
- Extending HCL Workload Automation

rep8

This command prints Report 08-Job Histogram.

Syntax

rep8 -V|-U

rep8
     [-f date -b time -t date -e time]
     [-i file]
     [-p ]

rep8
     [-b time -e time]
     [-i file]
     [-p ]

Run the command from the TWS_home directory.

Arguments

-U: Displays the command usage information and exits.
-V: Displays the command version and exits.
-f date: Specifies to print job history from this date forward. Enter the date as yyyymmdd. The default is today's date.
-b time: Specifies to print job history from this time forward. Enter the time as hhmm. The default is the HCL Workload Automation startOfDay.
-t date: Specifies to print job history up to this date. Enter the date as yyyymmdd. The default is the most recent date.
-e time: Specifies to print job history up to this time. Enter the time as hhmm. The default is the HCL Workload Automation start of day time.
-i file: Specifies the name of the log file from which job history is extracted. Note that log files are stored in the schedlog directory. The default is the current Symphony file.
Note: Ensure that the time range specified by the [-f date -b time -t date -e time] arguments is within the date and time range defined in the -i file log file name.
-p: Specifies to insert a page break after each run date.

Comments

Any time you run rep8 the output of the command contains the information stored until the last time you run JnextPlan, the information related to the run of the current production plan will be contained in the rep8 output the next time you run JnextPlan. For this reason if you run rep8 after having generated the production plan for the first time or after a ResetPlan command, the output of the command contains no statistic information.

Examples

Print a job histogram which includes all information in the current plan (Symphony file):

rep8

Print a job histogram beginning at 6:00 a.m. on 1/25/2005, and ending at 5:59 a.m. on 1/26/2005:

rep8 -f 20050125 -b 0600 -t 20050126 -e 0559 -i schedlog/M199801260601

Print a job histogram, from the current plan (Symphony file), beginning at 6:00 am, and ending at 10:00 pm:

rep8 -b 0600 -e 2200

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.