Previous Topic: Example: Batch InputNext Topic: Example


Critical Path Monitoring Corequisite Resources

You can use Critical Path Monitoring with CA WA CA 7 Edition to monitor the progress and status of critical paths in your workload.

To define a critical path flow, you need to connect a unique type of VRM corequisite resource to the first job in the flow. This resource defines the name, end point, and target time for the flow. When the job is run, an active flow element is created when VRM resources are attached in the ready queue.

The resource name has the following format:

FLOW@flowname.endjob.endschid.endtarget.endday
flowname

Defines the 1 to 8 character unique name to assign to this flow.

endjob

Defines the job name of the last job in this flow.

endschid

Defines the schedule ID of the last job in this flow. Use a specific number from 1 to 999 or set to a value of 0 (zero) to indicate the ending job has the same schedule ID as the starting job of the FLOW.

endtarget

Defines the target latest time the ending job should complete (hhmm). Alternately, a time interval can be set from the starting time of the FLOW (+hhmm).

endday

Defines an optional parameter to add days to the target time (.n). You can specify a maximum of 9 days when an ending time (hhmm) is used for the endtarget. If an interval (+hhmm) is used, the maximum endday is 8.