USSF Client of CA GTS › Configuration › File to be Tracked Entry Format

File to be Tracked Entry Format

Use the following format to track files:

Filename,Scheduling System;Command

Filename

Defines a fully qualified path name to the file on the USS file system.

Example:

/u/user/joeuser/payroll.file

Note: The leading forward slash "/" is required in the path name.

Scheduling System

Defines the scheduling system; valid values are the following:

7; (or null)

Send the command to CA 7 (default)

J;

Send the command to CA Jobtrac

S;

Send the command to CA Scheduler

Command

Specifies any valid command format that is supported by the specified scheduling system. For CA Jobtrac or CA Scheduler, see the appropriate documentation.

For CA 7, commands are directed to U7SVC. For documentation on supported U7SVC commands, see the CA 7 Interfaces Guide.

For example, you can use:

TEST=YES

Directs the CA 7 command to the "Test" copy of CA 7 in compatibility mode. Use the TEST=YES keyword after the filename.

CA7=aaaa

In CA 7 r11 and above environments, the CA7= keyword can be used to direct the command to one of the eight possible CA 7 instances on a given LPAR. The instance name is a maximum of four characters and can be the alias name.

Note: The file to be tracked entry can be up to 5000 characters in length.

Example: UFINIT Member

Interval=0003

/u/user/system/payroll.file,7;TEST=YES;/login master;demand,job=jobtest1;/logoff

In the preceding example, USSF scans the file system for file name of payroll.file in the "/u/users/system/" directory every three seconds. If found, the CA 7 Login, Demand, and Logoff commands will be issued to the "test" copy of CA 7 through the U7SVC interface.