Batch Services Quick Start Guide
Batch Services Quick Start Guide
Version 6.1.9
Wednesday, November 16, 2016
Copyright
Copyright © 1994-2016 Intergraph® Corporation. All Rights Reserved. Intergraph is part of Hexagon.
Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains
confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret law, and
international treaty, and may not be provided or otherwise made available without proper authorization from Intergraph Corporation.
Documentation
Documentation shall mean, whether in electronic or printed form, User's Guides, Installation Guides, Reference Guides,
Administrator's Guides, Customization Guides, Programmer's Guides, Configuration Guides and Help Guides delivered with a
particular software product.
Other Documentation
Other Documentation shall mean, whether in electronic or printed form and delivered with software or on Intergraph Smart Support,
SharePoint, or box.net, any documentation related to work processes, workflows, and best practices that is provided by Intergraph
as guidance for using a software product.
Terms of Use
a. Use of a software product and Documentation is subject to the End User License Agreement ("EULA") delivered with the
software product unless the Licensee has a valid signed license for this software product with Intergraph Corporation. If the
Licensee has a valid signed license for this software product with Intergraph Corporation, the valid signed license shall take
precedence and govern the use of this software product and Documentation. Subject to the terms contained within the
applicable license agreement, Intergraph Corporation gives Licensee permission to print a reasonable number of copies of the
Documentation as defined in the applicable license agreement and delivered with the software product for Licensee's internal,
non-commercial use. The Documentation may not be printed for resale or redistribution.
b. For use of Documentation or Other Documentation where end user does not receive a EULA or does not have a valid license
agreement with Intergraph, Intergraph grants the Licensee a non-exclusive license to use the Documentation or Other
Documentation for Licensee’s internal non-commercial use. Intergraph Corporation gives Licensee permission to print a
reasonable number of copies of Other Documentation for Licensee’s internal, non-commercial use. The Other Documentation
may not be printed for resale or redistribution. This license contained in this subsection b) may be terminated at any time and
for any reason by Intergraph Corporation by giving written notice to Licensee.
Disclaimer of Warranties
Except for any express warranties as may be stated in the EULA or separate license or separate terms and conditions, Intergraph
Corporation disclaims any and all express or implied warranties including, but not limited to the implied warranties of merchantability
and fitness for a particular purpose and nothing stated in, or implied by, this document or its contents shall be considered or deemed
a modification or amendment of such disclaimer. Intergraph believes the information in this publication is accurate as of its
publication date.
The information and the software discussed in this document are subject to change without notice and are subject to applicable
technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document.
The software, Documentation and Other Documentation discussed in this document are furnished under a license and may be used
or copied only in accordance with the terms of this license. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL
EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.
Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data.
Users should verify for themselves that the data is accurate and suitable for their project work.
Export Controls
Intergraph Corporation’s software products and any third-party Software Products obtained from Intergraph Corporation, its
subsidiaries, or distributors (including any Documentation, Other Documentation or technical data related to these products) are
subject to the export control laws and regulations of the United States. Diversion contrary to U.S. law is prohibited. These Software
Products, and the direct product thereof, must not be exported or re-exported, directly or indirectly (including via remote access)
under the following circumstances:
a. To Cuba, Iran, North Korea, Sudan, or Syria, or any national of these countries.
b. To any person or entity listed on any U.S. government denial list, including but not limited to, the U.S. Department of Commerce
Denied Persons, Entities, and Unverified Lists, http://www.bis.doc.gov/complianceandenforcement/liststocheck.htm, the U.S.
Department of Treasury Specially Designated Nationals List, http://www.treas.gov/offices/enforcement/ofac/, and the U.S.
Department of State Debarred List, http://www.pmddtc.state.gov/compliance/debar.html.
c. To any entity when Licensee knows, or has reason to know, the end use of the Software Product is related to the design,
development, production, or use of missiles, chemical, biological, or nuclear weapons, or other un-safeguarded or sensitive
nuclear uses.
d. To any entity when Licensee knows, or has reason to know, that an illegal reshipment will take place.
Any questions regarding export or re-export of these Software Products should be addressed to Intergraph Corporation’s Export
Compliance Department, Huntsville, Alabama 35894, USA.
Trademarks
Intergraph, the Intergraph logo, PDS, SmartPlant, FrameWorks, I-Convert, I-Export, I-Sketch, SmartMarine, IntelliShip, INtools,
ISOGEN, MARIAN, SmartSketch, SPOOLGEN, SupportManager, and SupportModeler are trademarks or registered trademarks of
Intergraph Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are registered trademarks
of Microsoft Corporation. Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its
affiliates. MicroStation is a registered trademark of Bentley Systems Inc, all rights reserved. Other brands and product names are
trademarks of their respective owners.
Glossary ..................................................................................................................................................... 45
Index ........................................................................................................................................................... 49
To find information on training for Intergraph products, or to enroll for an available class, go to
http://www.intergraph.com.
In This Section
Batch Services Defined ................................................................. 9
Batch Services Features ............................................................... 9
Batch Services Components ......................................................... 10
Getting Started............................................................................... 10
You can manage batch and pipe queues on remote computers from one location.
You can determine which jobs run at a given time, and in what order.
You do not have to monitor jobs. Batch Services supports SMTP mail or event log
notification when a batch job completes successfully or encounters errors.
Batch Services provides the following additional features:
An application programming interface (API).
Support for multiprocessor systems.
A command-line interface that can be used with scripts.
Job submission to or from Windows systems.
Getting Started
Begin by following the instructions in the next section to install and configure the Batch Services
software on your system. Then refer to the rest of the document as follows:
To remove Batch Services software from your system, see Removing the batch service (on
page 16).
To learn about the Batch Manager interface, see Understanding the Batch Manager
Interface (on page 22).
To grant batch services privileges on your system, see Granting Batch Service Privileges
(on page 23).
To create queues on your system, see Creating and Deleting Queues (on page 27).
To manage and monitor queues on your system, see Specifying Job Notification
Preferences (on page 41).
To learn about scripts, see Creating a Script (on page 37).
To submit a batch job, see Submitting a Job (on page 38).
To manage batch jobs, see Creating and Managing Queues (on page 27).
In This Section
Batch Services Hardware/Software Recommendations ................ 11
Installing Intergraph Batch Services .............................................. 12
Command Line Installation (Silent Install) ..................................... 14
Starting and Stopping Batch Services ........................................... 16
Removing the Batch Service ......................................................... 16
Configuring the Batch Services Server for Drawings Tasks ......... 17
If you want Batch Services to run batch jobs as 64-bit processes, the batch server computer
must run the 64-bit version of the operating system. It must also have the 64-bit version of
the designated Intergraph software installed.
Batch Services software can work with any network adapter supported by Windows. The
network adapter you use must be properly installed and configured for your computer before
you install Batch Services software. Refer to your Windows documentation for a list of
compatible network adapters, and to the documentation for your network adapter for
installation and configuration instructions.
Running batch jobs on the Citrix server is not supported. However, you can pipe queue the
batch processes from the Citrix server to a batch queue on another computer.
6. Type your name and organization name, and then click Next.
8. Click Display. Read the license agreement, and then click Yes.
9. Review the default installation folder ($WindowsDrive:\Win32App\Ingr\Batch\).
If you plan to use this installation of Intergraph Batch Services with Plant
Design System® (PDS), do not install Intergraph Batch Services to a folder path that
contains spaces, such as c:\Program Files (x86)\Batch. Although Intergraph Batch Services
supports spaces in folder paths, PDS does not.
11. Specify whether to run all jobs as the same user or use account mapping.
If you select Set up account mapping per user through Smart Batch Services, you must
configure account mapping before you can submit jobs. Use Batch Manager to configure
account mapping after setup is complete. For more information, see Configure Account
Mappings (on page 25).
If you select Run all jobs as same user to configure account mapping, define the user
name and user name password under which jobs should run.
Required Arguments
SLAACCEPT=yes - Accepts the Software License Agreement.
/v"<arguments>" - Passes options to the Windows Installer setup, Intergraph Batch
Services.msi. There are no spaces after the v.
Optional Arguments
/s - Runs Setup.exe in silent mode.
/qn - Runs the Windows Installer setup, Intergraph Batch Services.msi, in silent mode.
INSTALLDIR=<path> - By default, the product is installed to
the<WindowsVolume>\Win32App\INGR\BATCH folder. To change the location, enter a different
path. For example, enter INSTALLDIR=D:\Intergraph\BatchServices. If spaces exist in the
path, you must add \" before and after the path. For example, enter
INSTALLDIR=\"D:\Intergraph\Batch Services\".
INTERACTIVE_DESKTOP=0 - By default, on Windows XP, the Batch Server service is setup
to interact with the desktop. To disable this behavior, include INTERACTIVE_DESKTOP=0. This
setting is not valid with Vista, Windows 7, or later operating systems, and is ignored.
ACCTMAP_USERNAME=domain\username - To run all jobs as the same user, enter an
existing domain\username.
ACCTMAP_PWD - Password for the username. Used in conjunction with
ACCTMAP_USERNAME.
/Lv*x <path>\Logfilename - Creates a Windows Installer installation log file. If the path or file
name contains spaces, you must put \" in front of the path and after the file name, for example:
/Lv*x \"C:\Installer Log Files\InstallLog.log\". The path must already exist.
Example Command-lines
C:\>"…\BatchServices\Setup.exe" /s /v"SLAACCEPT=yes /qn"
Installs the setup to the default location without account mapping. By default, on Windows XP,
the Batch Server service is set up to interact with the desktop.
C:\>"…\BatchServices\Setup.exe" /s /v"INSTALLDIR=\"C:\Batch Services\"
SLAACCEPT=yes INTERACTIVE_DESKTOP=0 /qn"
Installs the setup to C:\Batch Services without account mapping. On Windows XP, the Batch
Server service is not set up to interact with the desktop.
C:\>"…\BatchServices\Setup.exe" /s /v"INSTALLDIR=\"C:\Batch Services\"
SLAACCEPT=yes INTERACTIVE_DESKTOP=0 ACCTMAP_USERNAME=domain\username
ACCTMAP_PWD=password /qn"
Installs the setup to C:\Batch Services with account mapping. On Windows XP, the Batch Server
service is not set up to interact with the desktop.
C:\>"…\BatchServices\Setup.exe" /s /v"SLAACCEPT=yes INTERACTIVE_DESKTOP=0
ACCTMAP_USERNAME=domain\username ACCTMAP_PWD=password /Lv*x \"C:\Install
Log Files\install.log\" /qn"
Installs the setup to the default location with account mapping, and creates a Windows Installer
installation log file. On Windows XP, the Batch Server service is not set up to interact with the
desktop.
C:\>"…\BatchServices\Setup.exe" /s /x /v"/qn"
Uninstalls Batch Services in silent mode.
The printer name on the client computer must match the printer name on the batch server.
Every mapped account must open Microsoft Excel once on every batch server.
Microsoft Excel must have the same security settings that are necessary for interactive
updates. Excel must be configured correctly for every IBS-mapped account on the batch
server.
You must add the following entries to the system path for 3D model data documents to
update:
[Product Folder]\Core\Runtime
[Product Folder]\GeometryTopology\Runtime
You must run the ConfigureDrawingsBatch utility each time you change mapped account
settings.
If you are running 64-bit drawings batch services and Oracle, you must install the 64-bit
Oracle client on the computer running the batch services.
Paper Size – Displays the paper sizes supported by the selected printer.
Use 64-bit if available
Updates drawings with 64-bit processes. This option is only available for Update actions
performed on composed drawings.
If you select Use 64-bit if available and run Update on a folder component
containing composed drawings and other drawing types, the composed drawings are
updated with 64-bit processes. All other drawings are updated with 32-bit processes.
Schedule
Creates the job and opens the Schedule Batch dialog box.
If you click Schedule with no actions in Actions to Queue, you receive a
message, and the dialog box remains open.
2. Select the action, and click Add to move it into Actions to Queue.
You can add actions to the queue in any order, but the software processes the actions
in the following order: Refresh, Update, and then all other actions. If you add Update,
but you do not add Refresh, Update is the first action processed.
You can only add one Save As action to the queue.
3. Define any action options. For more information, see Batch Processing - Intergraph Smart
Batch Services (on page 17).
4. Click Schedule to create the job and open the Schedule Batch dialog box.
Multiple documents:
1. Do one of the following:
a. Right-click a set of multi-selected documents or components in the Detail View, and
select Batch.
b. Right-click a component in the Management Console, Detail View, or Drawings
Console, and select Batch.
2. Select the action, and click Add to move it into Actions to Queue.
You can add actions to the queue in any order, but the software processes the actions
in the following order: Refresh, Update, and then all other actions. If you add Update,
but you do not add Refresh, Update is the first action processed.
You can only add one Save As action to the queue.
3. Define any action options. For more information, see Batch Processing - Intergraph Smart
Batch Services (on page 17).
4. Click Schedule to create the job and open the Schedule Batch dialog box.
Create a Template
Templates are user-parameterized actions that are saved in the session file and available for
future batch jobs. You can only create templates based on the Print action.
Create a new template:
1. Select the Print action, and click Add to move it to Actions to Queue.
2. In Action Options, make the necessary changes to the action.
3. Type a new Template Name for the action.
4. Click Save Settings As Template.
Delete a template:
1. Select the template to delete.
2. In Action Options, click Delete.
Specifies how many weeks pass between job runs. In addition, you can select on which
days the job runs. This option is available when you select Weekly from Run job.
Day X of the month
Specifies on which day of the month the job runs. This option is available when you select
Monthly from Run job.
The X Y of the month
Specifies on which day of the month the job runs. For example, you can select the last
Monday of the month. This option is available when you select Monthly from Run job.
Job Start
Notifies you when the job starts, if Outlook is set up.
Job Completion
Notifies when the job completes, if Outlook is set up.
Job Abort
Notifies you if the job aborts, if Outlook is set up.
Address Book
Selects the name of the person to be notified by e-mail of the job status, if Outlook is set up.
If Outlook is not available, this option does not work. You can also type the address
manually. The person you define here receives an email with the job log files after the job
finishes.
The Batch Services SMTP option must be configured on the batch server for this to work.
For more information, see the Intergraph Smart Batch Services documentation.
The WinZip application is no longer required on the batch server to compress any emailed
attachments. Compression is now done with functionality included in Intergraph Batch
Services.
In This Section
Understanding the Batch Manager Interface ................................. 22
Granting Batch Service Privileges ................................................. 23
Configure Account Mappings ........................................................ 25
The Batch Manager toolbar, located below the Batch Manager menus, provides shortcuts to the
following tasks. Position the cursor over a toolbar button to display a tip describing the command
associated with that button. Buttons are provided for the following tasks:
Submitting and deleting jobs
Holding and releasing jobs
Creating and deleting queues
Operators list.
5. Click Add, and then type the username of a user into the Add Names box, or the group
name of a group, to which you want to grant privileges.
6. Specify local users and groups (on your computer) by username or group name only. Use
one of the following formats when keying in a username or group name:
domain_name\username or system_name\username
domain_name\group_name or system_name\group_name
Separate multiple users or groups with a semicolon (;).
7. Select the type of privilege you want to grant the user or group (Manager or Operator).
8. Click OK.
9. Repeat steps 5 through 8 for each user or group to which you want to grant privileges.
10. When you have finished assigning privileges to users or groups, click OK on the Server
Properties dialog box.
5. In the Managers and Operators list, select the user or group for which you want to remove
privileges.
6. Click Remove.
7. Repeat steps 5 and 6 for each user or group from which you want to remove privileges.
8. When you have finished removing privileges from users and groups, click OK.
To change a user’s or group’s privileges, first remove the current privileges from the
user or group; then re-add the user or group to the privilege list with the new privilege.
6. In the Map To Account Domain/Host box, select the domain of the Windows user account
you want to run jobs as.
7. In the Map To Account User box, type the user name to use.
8. Click Add.
9. Type and confirm the password for the "to account" user name.
10. Click OK.
The ConfigureDrawingsBatch utility must be run each time mapped account
settings are changed. For more information, see Configuring the Batch Services Server for
Drawings Tasks (on page 17).
In This Section
Creating and Deleting Queues ...................................................... 27
Changing Queue Properties .......................................................... 30
Setting the Default Queue ............................................................. 31
Adding Shells to a Batch Queue .................................................... 33
Adding Destinations to a Pipe Queue............................................ 34
Enabling and Disabling a Queue ................................................... 34
Starting and Stopping a Queue ..................................................... 35
Displaying Queue Status ............................................................... 36
Refer to Adding Shells to a Batch Queue (on page 33) for more information on batch queues.
3. Click OK in the confirmation box to stop and restart the Intergraph Batch Services.
Run this tool at least once on the computer on which the job needs to be submitted,
or on the computer where the job needs to be run. This tool sets some environment
variables as well as creating the batch queues.
4. Open Control Panel > Administrative Tools > Services.
5. In Services, select Intergraph Batch Server from the list, and then click Stop.
6. With Intergraph Batch Server service still selected, click Start.
7. To verify that the batch queues were created, open Intergraph Batch Manager and then
select your server in the tree view.
The WinZip application is no longer required on the batch server to compress any emailed
attachments. Compression is now done with functionality included in the Intergraph Smart
3D delivery.
This tool cannot create pipe queues. Use Intergraph Batch Services to create pipe queues.
Verify that the C:\Windows\SysWOW64\config\systemprofile\Desktop folder exists if you are
using a 64-bit or Windows Server operating system. Ask your system administrator create
the Desktop folder with full permissions if it does not exist.
3. Select Queue > Create, or click Create Queue from the toolbar.
4. Key the queue name into the Queue Name box.
5. Optionally, key a description of the batch queue into the Description box.
6. Under Queue Type, select Pipe.
7. Click OK.
Refer to Adding Destinations to a Pipe Queue (on page 34) for more information about pipe
queues.
Deleting a Queue
Before you can delete a queue, the queue cannot contain any jobs and must be disabled and
stopped. You must have manager privileges to delete a queue. You can delete queues on
remote Windows computers. To delete a queue from your system:
1. Open Intergraph Batch Manager.
2. Click on the queue listed in the server view, or select the queue view for that queue.
3. Select Queue > Delete, or click Delete Queue from the toolbar.
4. When prompted, click Yes to confirm that you want to delete the queue.
Security Queue Access Unrestricted Determines who can gain access to the
queue. To restrict access to specific users or
groups of users, select Restricted. To open
access to the queue to all users, select
Unrestricted.
Authorized Groups None Lists users or groups of users that can gain
and Users access to the queue if it is restricted. Select
Add to add users or groups to the access
list. Select a user or group, and then select
Remove, to remove that user or group from
the access list.
When keying in a username or group name,
use the format for usernames and group
names described in Granting Batch Service
Privileges (on page 23).
Ensure that the default queue is configured for a job in Project Management, and that
the configured queue exists on all client computers.
For pipe queues, you need to add the required destinations to the queue. For more
information, see Creating and Configuring Pipe Queues in the Smart 3D Intergraph
Batch Services User’s Guide.
Optional Queues
Displays the Configure Optional Queues dialog box.
Configure Optional Queues Dialog Box
Maximum Allowed Time
Specifies the maximum allowed time to process a job type in the queue. If the job is not
completed in the allowed time, it terminates and the software sends a time-out notification to
the mailing list specified at the time that you submitted the job. By default, the Maximum
Allowed Time is not specified, and the job runs without any time limit. To specify a
Maximum Allowed Time, you must first select Is TimeOut Supported.
When queue times are defined on the Configure Optional Queues dialog box, Maximum
Allowed Time displays the total of those times.
Set a value for Maximum Allowed Time that allows enough time for each job to
execute.
If a job is submitted on a pipe queue but is executed on a different queue, the
Maximum Allowed Time for the job is read from the submitted pipe queue.
Is TimeOut Supported
Enables Maximum Allowed Time functionality. This option is not selected by default.
You can create custom batch jobs. For more information, see Creating and
Scheduling Custom Batch Jobs in the Smart 3D Reference Data Guide.
To enable a queue:
1. Open Intergraph Batch Manager.
2. Click on the queue listed in the server view, or select the queue view for that queue.
3. Select Queue > Enable, or click Enable Queue from the toolbar.
The queue should now show as ENABLED in its listing in the server view.
The availability of the Enable and Disable menu and toolbar commands toggles,
depending on the current inflow state of the queue.
To disable a queue:
1. Open Intergraph Batch Manager.
2. Click on the queue listed in the server view, or select the queue view for that queue.
3. Select Queue > Disable, or click Disable Queue from the toolbar.
The queue should now show as DISABLED in its listing in the server view.
To start a queue:
1. Open Intergraph Batch Manager.
2. Click on the queue listed in the server view, or select the queue view for that queue.
3. Select Queue > Start, or click Start Queue from the toolbar.
The queue should now show as STARTED in its listing in the server view.
The availability of the Start and Stop menu and toolbar commands toggles, depending on the
current outflow state of the queue.
To stop a queue:
1. Open Intergraph Batch Manager.
2. Click on the queue listed in the server view, or select the queue view for that queue.
3. Select Queue > Stop, or click Stop Queue from the toolbar.
The queue should now show as STOPPED in its listing in the server view.
The availability of the Start and Stop menu and toolbar commands toggles, depending on the
current outflow state of the queue.
In This Section
Creating a Script ............................................................................ 37
Submitting a Job ............................................................................ 38
Saving and Restoring Named Batch Jobs ..................................... 43
Creating a Script
A batch job reads a script and performs the instructions in it, using the appropriate shell (the
program that runs the instructions in the script). Scripts can take many forms, including .bat files
and Perl scripts. A script can also be an executable program (.EXE file) if the queue has no
default shell, or if the shell is set to CMD.EXE.
The following example is a .bat script that backs up a directory on the batch server to a shared
drive that has been locally mounted from a remote system. To use the script, ensure that a local
batch queue has been created, enabled, and started, and that the queue’s default shell is the
cmd.exe program.
REM This script will do the following:
REM
REM 1. Mount the shared drive \\machine\share
REM 2. Copy everything in c:\users\default to the shared drive.
REM 3. Unmount the shared drive.
REM
net use p: \\machine\share
xcopy c:\users\default p: /e /i
net use /delete p:
The following example is a .bat script that prints all PostScript files in the c:\temp directory on
the batch server to a printer on a remote Windows system. To use the script, ensure that a local
batch queue has been created, enabled, and started; that the queue’s default shell is the
cmd.exe program; and that your system has access to the printer on the remote Windows
system.
REM This script will do the following:
REM
REM 1. Associate a remote printer on a Windows system
REM (\\machine\printer) with a local printer port.
REM 2. Copy files in c:\temp that end in .ps to the local printer
REM port.
REM 3. Remove the printer association.
REM
net use lpt1: \\machine\printer
cd c:\temp
for %%I in (*.ps) do copy %%I lpt1:
net use /delete lpt1:
Submitting a Job
To submit a job to be run on the batch server on your system:
1. Open Intergraph Batch Manager.
2. Select a queue listed in the server view, or select the queue view for that queue.
3. Ensure that the selected queue is enabled and started.
Scheduling Sets the parameters associated with scheduling the job for execution.
File Staging Describes how necessary files for the job are handled.
The following sections describe basic operational parameters found in the Job Submit dialog,
along with brief instructions for using them when submitting a job.
Queue
Specifies the queue to which the job is submitted.
Job Name
Specifies the drawing name for the job. It also displays the model name and the Drawing
Console path, up to 250 characters. If the name surpasses the character limit, it is
truncated. For example, the full path for the drawing name JUB_ATP, 3D Model
Data\Piping Drawings Metric\3D Model Data Piping\3D Model Data Piping-1-0001 can
be shortened to its drawing name, 3D Model Data Piping-1-0001, then to its model name
and drawing name, 3D Model Data Piping\3D Model Data Piping-1-0001.
Script File
Specifies the shell script submitted for execution.
Account Name
Specifies a user-defined string describing the account.
Size
Shows the size of the shell file.
Shell
Displays the currently selected shell for the job. A blank value indicates the default shell for
the queue. This value can be set only at job submission.
Restartable
Controls whether the job is restarted after a system crash, system shutdown, or batch
service shutdown while the job is running.
Specifies how many times the job is run before its execution series ends
No End Date
Sets the recurring job to run indefinitely.
End By
Specifies an end date for the execution series of the job.
Start Time
Specifies the time the job is allowed to start. These fields can be changed at job submission
and at any time before the end date for submitted recurring jobs.
Current Time
Uses the submission time of the job as its start time. This field can be changed at job
submission and at any time before the end date for submitted recurring jobs.
Next Occurrence
Shows the date and time of the next occurrence of the recurring job. This read-only field
appears only for recurring jobs (on page 47). It is calculated by Batch Services.
\\host\pathname\filename format.
Keep Output on Execution Host
Specifies whether the output is kept on the execution host.
No Spooling
Specifies whether output is to be created directly in the specified pathname, rather than
spooling (on page 48) the output and waiting until the job is completed. Spooling is not
supported on remote computers.
Join Output in One File
Disables the Standard Error group box and sends all output to the standard output.
1. Select Submit from the Job menu to display the Submit dialog box. See Submitting a Job
(on page 38) for more information about the Submit dialog box.
2. Enter the job parameters that you wish to save as a named job.
3. Select Save As to name and save your job.
hold
A delay in running a job submitted to a queue. A held job will not run until the hold is released, or
the job is deleted from the queue.
A user hold may be placed on a job submitted by that user when the job is submitted. A user
hold can be released either by the submitting user, or by a user with operator or manager
privileges on the server.
A user with operator or manager privileges may place an operator hold on a job, after the job is
submitted but before it runs. Only a user with operator or manager privileges can release an
operator hold.
When a job is being held, the job will remain in the queue until it is deleted or released. It will not
run while the hold is in place. See also privilege.
inflow state
The state of a queue with regard to accepting jobs. See also queue state, enable, disable.
job
A set of instructions needed to perform a given task or set of tasks on a computer system. See
also batch job and shell.
job identifier (job ID)
A unique alphanumeric string that identifies a job. A batch job ID is in the form jobid.orighost,
where jobid is a sequentially assigned number up to 5 digits in length, and orighost is the name
of the system from which the batch job originated.
When a job is successfully submitted, it is assigned a unique job-id. The job-id can be used to
reference the job. No two jobs will have the same job-id.
manager
See privilege.
operator
See privilege.
outflow state
The state of a queue with regard to processing jobs. See also queue state, started, stopped.
per-process file size limit
The file size limit indicates the maximum total file size used by a request. This value is not used
in Windows.
pipe queue
A pipe queue routes requests to another queue. Pipe queues can accept either a batch request,
or a request from another pipe queue. A pipe queue receives the request and sends it to the first
available queue in its destination list that will accept the request. The destination list may contain
any queue type. Pipe queues are normally used to create a connection to a remote batch
queue.
privilege
An operational permission level assigned to every Batch Services user. Non-privileged users
can submit jobs to queues to which they have been granted access; operators can issue
commands that directly affect queue management; and managers can control all aspects of
Batch Service operation.
queue
A queue is a waiting line in which job requests reside until they are processed. A queue can
control the number of jobs submitted to it, the number of simultaneous jobs, and the execution
priority of those jobs. A queue can also restrict the users and groups that have access to it. The
batch system supports batch queue and pipe queue.
queue state
A queue has two states: the inflow state and the outflow state.
Inflow State - The inflow state is either enabled or disabled. An enabled queue will accept new
jobs that are submitted or transferred to it; a disabled queue will not.
Outflow State - The outflow state is either stopped, started, or stopping. A stopped queue will
not run the jobs it contains. A queue must be started in order to run jobs.
Example
An "enabled/stopped queue" is a queue that will accept jobs but not run them.
See also enabled, disabled, started, stopped.
queue view
The view in Batch Manager that shows information on the jobs in a queue.
recurring jobs
Jobs scheduled to run more than once at a regular interval. Use the Job Submit\Scheduling tab
in Batch Manager to submit recurring jobs. Hourly, daily, weekly, monthly, and yearly intervals
are available.
scheduling priority
The scheduling priority, or "intra-queue priority," is used for scheduling the order of job execution
within the queue. The priority value must be in the range of [-1024..1023].
script
A file that contains instructions for the execution of a batch job.
server view
The view in Batch Manager that shows information about the operation of one or more queues.
shell
An executable program that can be used to run a script. For example, cmd.exe is a shell that
can be used to run .bat scripts. See also script.
spooling
The process of storing a file internally by Batch Services until a batch job ends, and then
returning the files to the intended directories. Spooling is not supported on remote computers.
started
A queue state in which the queue will run jobs submitted to it.
stdin, stderr, stdout
These are standard streams for input, output, and error output.
By default, standard input (stdin) is read from the keyboard, while standard output (stdout) and
standard error output (stderr) are printed to the screen.
stopped
A queue state in which the queue will not run jobs submitted to it.
D N
default queue • 45, 48 named batch job • 43
default shell • 33, 45, 48 creating • 27
Deleting a Queue • 29 submitting • 44
desktop access • 12 network adapters and Batch Services • 11
disabled • 45
disabling queues • 34
Displaying Queue Status • 36 O
DNS • 11 online documentation • 6
Drawings Batch Dialog Box • 18 operator • 46
Optional Schedule Properties Dialog Box •
E 21
outflow state • 46, 48
enabled • 45 started • 48
Enabling and Disabling a Queue • 34
S
Saving and Restoring Named Batch Jobs •
43
Schedule [Task] Dialog Box • 20
scheduling priority • 47
script • 47, 48
server view • 47, 48
Setting Basic Job Information • 38
Setting Job Scheduling Information • 39
Setting the Default Queue • 31
shell • 47, 48
Specifying How to Handle Job Output • 41