107 lines
9.8 KiB
HTML
107 lines
9.8 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="task" />
|
||
|
|
<meta name="DC.Title" content="Work with command variables" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<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="rzaksajsworkflowabout.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="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="rzaksajs9command" />
|
||
|
|
<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>Work with command variables</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksajs9command"><a name="rzaksajs9command"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Work with command variables</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<div class="section"><p><span class="uicontrol">Command variables</span> (previously known as
|
||
|
|
parameters) are variables that you store in the Advanced Job Scheduler and
|
||
|
|
use in jobs submitted through the Advanced Job Scheduler. Command variables
|
||
|
|
contain information that will be replaced inside the command string of a scheduled
|
||
|
|
job. Examples of command variables include the beginning of each month, a
|
||
|
|
company division number, a company number and so on. You can display command
|
||
|
|
variables, add a new command variable, add a new command variable based on
|
||
|
|
an existing one, or remove a command variable, provided it is not currently
|
||
|
|
in use by a scheduled job.</p>
|
||
|
|
<p>You can select an existing command variable
|
||
|
|
and display its properties to make changes.</p>
|
||
|
|
<p>To add a new command variable,
|
||
|
|
follow these steps:</p>
|
||
|
|
</div>
|
||
|
|
<ol><li><span>Open <span class="uicontrol">Work Management</span> from your iSeries Navigator
|
||
|
|
window.</span></li>
|
||
|
|
<li><span>Right-click <span class="uicontrol">Advanced Job Scheduler</span> and click <span class="uicontrol">Properties</span>.</span></li>
|
||
|
|
<li><span>Click the <span class="uicontrol">Command Variables</span> tab.</span></li>
|
||
|
|
<li><span>Click <span class="uicontrol">New</span> and type a name for the command
|
||
|
|
variable.</span></li>
|
||
|
|
<li><span>Type a description for the command variable.</span></li>
|
||
|
|
<li><span>Type the length of the command variable. The length can range from
|
||
|
|
1 to 90.</span></li>
|
||
|
|
<li><span>Choose how you want to supply the replacement value: </span><ol type="a"><li><span>Specify the data to use for the command variable. You use any
|
||
|
|
character in this field. The number of characters in the data cannot be greater
|
||
|
|
than the length specified in the Length field.</span></li>
|
||
|
|
<li><span>Type a formula to calculate the date. (For examples, see the
|
||
|
|
online Help.)</span></li>
|
||
|
|
<li><span>Type the program name that you use to retrieve the replacement
|
||
|
|
value.</span></li>
|
||
|
|
<li><span>Type the library that you use to retrieve the replacement value.</span></li>
|
||
|
|
<li><span>Choose whether you want the replacement value retrieved from
|
||
|
|
the system operator at run time.</span></li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
<div class="section"></div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<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="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><img src="./delta.gif" alt="Start of change" /><a href="rzaksajsworkflowabout.htm" title="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.">The Work Flow Manager</a><img src="./deltaend.gif" alt="End of change" /></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>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|