USRREC

Purpose

This statement defines the passwords for the users who need to schedule native jobs to run on Windows™ workstations, or who want to use this feature when defining job types with advanced options that will run on workstations based on any operating system.

After you have defined a user and its password, you use these values as follows in the definitions of job types with advanced options:

The value in USRNAM

In the JOBREC job definition statement, it is specified as the value of the JOBUSR keyword.
In the definition panel of the job in the Dynamic Workload Console it is specified in the User Name field of the Credentials section.

The value in USRPSW

Is resolved at run time if you:

Specify Y for the JOBPWD keyword in the JOBREC job definition statement.
Select User in the Password type widget that is displayed by clicking the ellipsis (...) located by the Password field in the Credentials section of the job definition panel in the Dynamic Workload Console.

Format

Parameters

USRCPU(cpu name)

The HCL Workload Automation workstation on which the user can launch jobs. It consists of four alphanumeric characters, starting with a letter.

USRNAM(logon ID)

The user name of a Windows™ workstation or the name of the user authorized to run a job type with advanced options. The name is case-sensitive and can be of up to 47 characters.

If you are defining a user that will run native jobs on Windows workstations, note that:

The name can include a domain name and might be case-sensitive, depending on the Windows™ version.
The user must be able to log on to the computer on which HCL Workload Automation has launched jobs, and must also be authorized to Log on as batch.
If the name is not unique in Windows™, it is considered to be either a local user, a domain user, or a trusted domain user, in that order.
If you are defining a Windows™ domain user and the value contains a backslash (\), then the entire character string must be enclosed by single quotes, for example:
```
USRNAM('XXXXX\user1')
```
If you are defining a Windows™ user in the username@internet_domain format that contains the at sign (@), for example administrator@mywindom.com, you must enclose the entire character string in single quotes:
```
USRNAM('administrator@mywindom.com')
```

USRPSW(password)

The password for the user specified in USRNAM. It can consist of up to 31 characters and must be enclosed in single quotation marks. It is case-sensitive.

The password is stored in the USRINFO member in plaintext, meaning that it is not encrypted. To encrypt it, run the sample EQQE2EPW JCL provided in the EQQBENCR member of the EQQSAMP library. For details about this sample JCL, see HCL Workload Scheduler for Z: Planning and Installation.

If the password is for a user that will run native jobs on Windows workstations, note that:

The password might be case-sensitive, depending on the Windows™ version.
If you are defining a Windows™ domain user and the value contains a backslash (\), then the entire character string must be enclosed by single quotes, for example:
```
USRPSW('XXXXX\password1')
```
If you are defining a password for the Windows™ user in the username@internet_domain format that contains the at sign (@), for example administrator@mywindom.com, you must enclose the entire character string in single quotes:
```
USRPSW('passw0rd')
```
As an alternative to defining the password in the USRREC statement, you can define it in a local file on the Windows™ workstation, by using the user utility, and set LOCALPSW(YES) in the TOPOLOGY statement.