3.1.3.3 Granting rights with the NTRights.exe Utility. 3–3 3.2 CREATING NT JOBS 3–3 3.2.1 Windows NT Execution Methods 3–3 3.2.2 Windows NT Example Job 3–3 CHAPTER 4 GETTING STARTED ON UNIX 4–1 4.1 GETTING READY FOR UNIX 4–1 4.1.1 Deﬁne Unix Usernames in JAMS 4–1 4.1.2 Verify that the rexec daemon is enabled on your target 4–1. Ntrights is utility to manually add user rights (google it). Sanur is utility to force runas to accept password from pipe (google it). Service name, database NT user account, and database NT password are all 'PostgreSQL' override as necessary. To trouble shoot initdb problems run cmd from within runas line. Network Monitor Capture Utility Nltest Domain Utility NTRights Utility Office 97 Unique Identifier Removal Tool OLE/COM Object Viewer Open Handles Open XML SDK Orca Outlook Express Outlook HTML Form Converter Page Fault Monitor Pandora's Box Path Manager Performance Data Block Dump Utility PerfVis NT Performance Tool PEX Phone Book Administrator.

Contents

Index

JAMS Home

Support

Contents

Index

This chapter provides a step by step guide to getting started running JAMS jobs on Microsoft Windows NT/2000.

There are a number of tasks which must be completed before you can run jobs under Windows NT/2000. These tasks include:

Install and Configure the JAMS Agent
Define NT Usernames in JAMS
Grant 'Log on as a batch job' to NT accounts or groups

3.1.1 Install and Configure the JAMS Agent

The JAMS Agent for Windows NT must be installed on any Windows NT/2000 machine which will run JAMS Jobs. The Agent can be installed on any class of NT system, from Workstation to Datacenter Server. Refer to the JAMS Installation Guide for a detailed explanation of the Agent installation procedure.

Installing the Agent also installs a JAMS Control Panel applet which is used to configure the Agent. This control panel applet lets you configure three settings:

Temporary Directory

The temporary directory is used to store temporary command procedures. These command procedures are deleted when a job completes. For Windows NT V4.0, the default can be used. For Windows 2000, you must specify a directory which can be accessed by the JAMS Agent and the accounts which jobs will run under.

Requester Secret

The Requester Secret is used to authenticate JAMS Servers before they can even attempt to run a job. The default is blank which disables this check. If you use requester authentication you must set the same secret here and on the server. You set the requester secret on the server with the JAMS SET AGENT/SECRET='secret' command.

TCP/IP Port

The Agent will listen for requests on the TCP/IP port specified. The default is port 77 which is reserved for private RJE systems. The port on the agent must match the port on the server. You set the TCP/IP port on the server with the JAMS SET AGENT/PORT=n command.

Allow Interactive

If checked, the Agent will allow jobs to run with interactive access to the desktop. Interactive access must be requested by setting the INTERACTIVE option in the job's execution method.

3.1.2 Define NT Usernames in JAMS

In order to run a job under Windows NT, the JAMS server must supply a valid NT username and password. You must use the SET USERNAME command to define the username/password combinations. You can also specify an access control list (ACL) which is used to determine who can use the username.

Here is an example of an NT user definition:

This example defines the NT username 'Administrator'. The password must be the correct password for the Administrator account but, the password isn't checked until a job is run under this username. Note that the password is enclosed in quotes to preserve the case. The ACL will allow OpenVMS users that are in the [1,*] UIC group to specify 'Administrator' as the username in a job or system definition.

3.1.3 Grant 'Log on as a batch job' to NT accounts or groups

JAMS jobs run as batch processes under Windows NT. The NT account that the batch job will run as must have the 'Log on as a batch job' user right. You can grant this right to specific accounts or, grant the right to a group and make the accounts members of the group.

3.1.3.1 Granting rights under Windows NT V4.0

Under Windows NT V4.0, you must grant the 'Log on as a batch job' right on each machine which will be running the JAMS Agent. You only have to grant the right on one domain controller and it will propagate to the other domain controllers in the domain. It will not propagate to member servers or workstations, you must grant the right on each of those machines.

You can use User Manager for Domains to grant the right for both the domain and individual machines. Select the User Rights option from the Policy menu. You must check the 'Show Advanced User Rights' check box to display the 'Log on as a batch job' user right.

To manage user rights on member servers and workstations, select the Select Domain.. option from the User menu. Enter 'machinename' in the Domain field and click Ok. You will then be connected to the specified machine and you will be able to manage the user rights on that machine.

3.1.3.2 Granting rights under Windows 2000

Under Windows 2000, you can grant the 'Log on as a batch job' right at the domain level or local level.

To manage rights under Windows 2000 you use the 'Local Security Policy' or 'Domain Security Policy' Administrator Utilities.

3.1.3.3 Granting rights with the NTRights.exe Utility

The NTRights.exe utility is included in the Windows NT Server 4.0 Resource Kit supplement 3 and in the Windows 2000 Resource Kit. If you have this utility you can grant the 'Log on as a batch job' right with a command like this:

Note that the rights name is case sensitive.

Once you've completed the initial setup required to run jobs on Windows NT/2000, defining jobs is simple. There is essentially no difference between an NT and an OpenVMS job definition. The key differences are:

An NT job must use NT commands rather than DCL.
An NT job must specify an execution method which is designed for NT.
An NT job should specify an agent node name.

3.2.1 Windows NT Execution Methods

JAMS ships with three Windows NT specific execution methods. You can create additional execution methods with the CREATE METHOD command. The three Windows NT execution methods are:

Method	Description
NT	Runs an NT command file.
NTCMD	Runs a single NT command.
NTPARSE	Runs an NT command file which has been parsed for JAMS parameter references.

3.2.2 Windows NT Example Job

Let's take the DEMOJOB1 from the Chapter 2 and make it into a Windows NT job.

Ntrights Utility Download Software

Notice that the only difference between the NT and OpenVMS version of this job is METHOD and AGENT