185 lines
15 KiB
HTML
185 lines
15 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="The Work Flow Manager" />
|
||
|
|
<meta name="abstract" content="As of V5R4, the Work Flow Manager lets you define units of work that consist of automated or manual steps. These units of work can then be scheduled or run interactively. The Work Flow Manager is located in the Advanced Job Scheduler container in the iSeries Navigator interface." />
|
||
|
|
<meta name="description" content="As of V5R4, the Work Flow Manager lets you define units of work that consist of automated or manual steps. These units of work can then be scheduled or run interactively. The Work Flow Manager is located in the Advanced Job Scheduler container in the iSeries Navigator interface." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajsmanagejobs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajsschedulejob.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajsnewjobgroup.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajspredefinedschedules.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajsscheduletempjob.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajsjobdependencies.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajsmonitor.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajsmonitormsg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajslocaldata.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajs5custapp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajswrkwinotification.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajs8library.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajs9command.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajscreateworkflow.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajsstartworkflow.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksajsworkflowstatus.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004-2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004-2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzaksajsworkflowabout" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>The Work Flow Manager</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksajsworkflowabout"><a name="rzaksajsworkflowabout"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">The Work Flow Manager</h1>
|
||
|
|
<div><p>As of V5R4, the Work Flow Manager lets you define
|
||
|
|
units of work that consist of automated or manual steps. These units of work
|
||
|
|
can then be scheduled or run interactively. The Work Flow Manager is located
|
||
|
|
in the Advanced Job Scheduler container in the iSeries™ Navigator interface.</p>
|
||
|
|
<p> Each step within the work flow can have one or more predecessor Advanced
|
||
|
|
Job Scheduler jobs and one or more successor Advanced Job Scheduler jobs.
|
||
|
|
When a work flow starts, the first step is flagged to run. When it completes,
|
||
|
|
the next step is flagged to run, and so on. </p>
|
||
|
|
<div class="p">The following are some additional considerations when using the Work Flow
|
||
|
|
Manager:<ul><li>You can manually start a work flow at any step. When you do so, you bypass
|
||
|
|
all previous steps in the work flow.</li>
|
||
|
|
<li>Automatic steps complete after all prior steps have completed. This includes
|
||
|
|
all predecessor Advanced Job Scheduler jobs.</li>
|
||
|
|
<li>After a step completes, the successor Advanced Job Scheduler jobs are
|
||
|
|
flagged to run.</li>
|
||
|
|
<li>Manual steps can complete in any sequence as long as the step's predecessor
|
||
|
|
jobs have finished.</li>
|
||
|
|
<li>You can mark completed manual steps as not complete and run them again
|
||
|
|
as long as there are no subsequent incomplete automatic steps.</li>
|
||
|
|
<li>You can cause a step to wait until the job completes before notifying
|
||
|
|
of the step's completion by specifying predecessor jobs that are the same
|
||
|
|
as the successor jobs of the previous step.</li>
|
||
|
|
<li>You can notify other users when a particular step starts, stops, did not
|
||
|
|
start by a specific time, or is taking too long. For example you can notify
|
||
|
|
a user who is responsible for a particular manual step that the previous automated
|
||
|
|
steps have completed.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p>When you use work flows, the activity log displays when the work flow started,
|
||
|
|
the steps that were run, the status of automated steps (success or fail),
|
||
|
|
when the work flow ended, and the final status of the work flow. </p>
|
||
|
|
<div class="p">
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><caption>Table 1. Work Flow Example</caption><thead align="left"><tr valign="bottom"><th valign="bottom" width="19.19191919191919%" id="d0e46">Work Flow</th>
|
||
|
|
<th valign="bottom" width="80.8080808080808%" id="d0e48">PAYROLL</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="19.19191919191919%" headers="d0e46 ">Scheduled</td>
|
||
|
|
<td valign="top" width="80.8080808080808%" headers="d0e48 ">Every Friday at 1:00 p.m.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="19.19191919191919%" headers="d0e46 ">Notification</td>
|
||
|
|
<td valign="top" width="80.8080808080808%" headers="d0e48 ">Clerk - Payroll work flow has started</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="19.19191919191919%" headers="d0e46 ">Step 1</td>
|
||
|
|
<td valign="top" width="80.8080808080808%" headers="d0e48 ">Automatic - Specifies a successor job to initialize
|
||
|
|
payroll files</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="19.19191919191919%" headers="d0e46 ">Step 2</td>
|
||
|
|
<td valign="top" width="80.8080808080808%" headers="d0e48 ">Automatic: <ul><li>Specifies the successor job from step 1 as a predecessor job for this
|
||
|
|
step</li>
|
||
|
|
<li>Notifies Clerk that timecards can be entered</li>
|
||
|
|
</ul>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="19.19191919191919%" headers="d0e46 ">Step 3</td>
|
||
|
|
<td valign="top" width="80.8080808080808%" headers="d0e48 ">Manual:<ul><li>Clerk completes after timecards are entered</li>
|
||
|
|
<li>Specifies a successor job to process timecard files and print timecard
|
||
|
|
report</li>
|
||
|
|
<li>Notifies Supervisor if step is not completed within 120 minutes</li>
|
||
|
|
</ul>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="19.19191919191919%" headers="d0e46 ">Step 4</td>
|
||
|
|
<td valign="top" width="80.8080808080808%" headers="d0e48 ">Automatic: <ul><li>Specifies successor job from previous step as a predecessor job</li>
|
||
|
|
<li>No Successor jobs</li>
|
||
|
|
<li>Notifies Clerk to check timecard report</li>
|
||
|
|
</ul>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="19.19191919191919%" headers="d0e46 ">Step 5</td>
|
||
|
|
<td valign="top" width="80.8080808080808%" headers="d0e48 ">Manual:<ul><li> Clerk will complete after checking reports</li>
|
||
|
|
<li>Specifies a successor job to process payroll</li>
|
||
|
|
</ul>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="19.19191919191919%" headers="d0e46 ">Step 6</td>
|
||
|
|
<td valign="top" width="80.8080808080808%" headers="d0e48 ">Automatic:<ul><li> Specifies the successor job from previous step as a predecessor job</li>
|
||
|
|
<li>No Successor jobs</li>
|
||
|
|
<li>Notifies Clerk and Supervisor that payroll has completed</li>
|
||
|
|
</ul>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<p>In this example the work flow PAYROLL starts every Friday at 1:00 p.m.
|
||
|
|
A notification is sent to the Clerk that the work flow has started. </p>
|
||
|
|
<p>Because Step 1 is automatic and does not have any predecessor jobs, it
|
||
|
|
flags the successor job that initializes the payroll files to run and then
|
||
|
|
complete. Step 2 has the successor job for Step 1 as its predecessor. Step
|
||
|
|
2 waits for the job that initializes the payroll files to complete. After
|
||
|
|
it has completed, Step 2 notifies the Clerk that he can enter timecards.
|
||
|
|
There are no successor jobs to flag to run. </p>
|
||
|
|
<p>The Clerk manually completes Step 3 after all of the timecards are entered.
|
||
|
|
The successor job that processes the timecard file and prints a timecard
|
||
|
|
report is flagged to run. As a precaution, the Supervisor is notified if
|
||
|
|
the step is not completed within 120 minutes. Because the predecessor job
|
||
|
|
for Step 4 is the successor for Step 3, Step 4 waits until the job that processes
|
||
|
|
the timecard file and prints a timecard report has completed. </p>
|
||
|
|
<p>After the job completes the Clerk is notified that the timecard report
|
||
|
|
can be checked. There are no successor jobs to flag to run. After the timecard
|
||
|
|
report is checked, the Clerk manually completes Step 5. The successor job
|
||
|
|
that processes the payroll and produces the checks is flagged to run. </p>
|
||
|
|
<p>Because the predecessor job for Step 6 is the successor for Step 5, Step
|
||
|
|
6 waits until the job that processes the payroll and produces the checks has
|
||
|
|
completed. After the job completes, it notifies the Clerk and Supervisor that
|
||
|
|
Payroll has completed. The checks can now be printed and distributed.</p>
|
||
|
|
<p>For more detailed information about the Work Flow Manager see the online
|
||
|
|
help. </p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><img src="./delta.gif" alt="Start of change" /><strong><a href="rzaksajscreateworkflow.htm">Create a new work flow</a></strong><img src="./deltaend.gif" alt="End of change" /><br />
|
||
|
|
When you create a new work flow you will specify how the work flow is started, it's maximum process time, the task steps and their run sequence, scheduling, notification and documentation details.</li>
|
||
|
|
<li class="ulchildlink"><img src="./delta.gif" alt="Start of change" /><strong><a href="rzaksajsstartworkflow.htm">Start a work flow</a></strong><img src="./deltaend.gif" alt="End of change" /><br />
|
||
|
|
When you start a work flow, you can choose whether you want the work flow to start on the first sequence or on a specific sequence.</li>
|
||
|
|
<li class="ulchildlink"><img src="./delta.gif" alt="Start of change" /><strong><a href="rzaksajsworkflowstatus.htm">Work with work flows</a></strong><img src="./deltaend.gif" alt="End of change" /><br />
|
||
|
|
You can control and monitor the work flow as it runs by using the Work Flow Status window.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksajsmanagejobs.htm" title="The following information will help you manage the Advanced Job Scheduler. First you need to schedule jobs using the Advanced Job Scheduler. Then, use the rest of the tasks to manage the jobs.">Manage the Advanced Job Scheduler</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzaksajsschedulejob.htm" title="Schedule a job and specify the commands that are associated with the job. You can also specify starting and ending commands to run a special version of a scheduled job.">Create and schedule a job</a></div>
|
||
|
|
<div><a href="rzaksajsnewjobgroup.htm" title="Set up and schedule a series of jobs that run consecutively in a specified order. Jobs within a job group require completion before the next job is submitted for processing.">Create and schedule a job group</a></div>
|
||
|
|
<div><a href="rzaksajspredefinedschedules.htm" title="Create schedules that contain information needed to schedule a job or calculate exception dates within a holiday calendar.">Predefined schedules</a></div>
|
||
|
|
<div><a href="rzaksajsscheduletempjob.htm" title="At times it might be necessary to run a scheduled job now or in the future in addition to its normal schedule. Use the Submit Job using Job Scheduler (SBMJOBJS) command, option 7 from Work with Jobs display, or the Run option from iSeries Navigator. It might also be necessary to process only a portion of the commands in the command list when setting up this special run.">Create a temporary scheduled job</a></div>
|
||
|
|
<div><a href="rzaksajsjobdependencies.htm" title="Set up jobs or groups of jobs that are dependent on each other. You can select the type of dependency that reflects how jobs are processed in your environment.">Schedule job dependencies</a></div>
|
||
|
|
<div><a href="rzaksajsmonitor.htm" title="Use Advanced Job Scheduler to view a job or a job group's history or status. You can also set up the activity retention, which is how long you want to retain the activity records for a job.">Monitor job activity for the Advanced Job Scheduler</a></div>
|
||
|
|
<div><a href="rzaksajsmonitormsg.htm" title="Add message identifiers to any command within the command list of a job to monitor messages.">Monitor for messages with Advanced Job Scheduler</a></div>
|
||
|
|
<div><a href="rzaksajslocaldata.htm" title="A local data area is a portion of space that is allocated for a job. Not all jobs use their local data area but some do. Each command within a job has access to the job's local data area. You might want to use a local data area if you are scheduling a job that previously required you to manually specify additional parameters. Use the local data area to specify the additional parameters so you do not need to manually specify them each time the job starts.">Create and work with local data area</a></div>
|
||
|
|
<div><a href="rzaksajs5custapp.htm" title="Applications are jobs that are grouped for processing. They are broader than job groups and do not necessarily process sequentially. Jobs in applications can process simultaneously and one job does not need to wait for another to process. All jobs within the application can be worked with and can have their own set of job defaults. Job controls are the defaults assigned to a job as you add it to the job scheduler as well as defaults used when the job is submitted.">Create and work with applications/job controls</a></div>
|
||
|
|
<div><a href="rzaksajswrkwinotification.htm" title="This information describes how to use the notification function of Advanced Job Scheduler.">Work with notification</a></div>
|
||
|
|
<div><a href="rzaksajs8library.htm" title="Library lists are user-defined lists of libraries that are used by the Advanced Job Scheduler when a job is processing.">Work with library lists</a></div>
|
||
|
|
<div><a href="rzaksajs9command.htm" title="A command variable (previously known as a parameter) is a variable you can store and use in jobs submitted through the Advanced Job Scheduler. Examples of command variables include the beginning of each month, a division number, a company number, and so on.">Work with command variables</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|