HCL Workload Automation, Version 9.4

File dependencies definition for database and stream files

About this task

The file dependencies mechanism on IBM i agents is the same as for all other HCL Workload Automation agents, with the exception of the opens keyword in association with IBM i files.

On IBM i agents, you can define file dependences based on two kind of physical files:

Native database files
Stream files (UNIX-like files)

You can use the opens keyword only with the -e %p qualifier for both file types. The rules to be used for the file name set as opens argument varies depending on the file type:

Native database files

Use the following syntax for the path name:

QSYS.LIB/library_name.LIB/file_name.FILE

where:

QSYS: Is the file system that supports the i Series server library structure
library_name: Is the name of the library containing the file.
file_name: Is the name of the database file that is being checked for existence. The file name must be in capital letters.

Stream files (UNIX-like files)

The file name is case-sensitive.

The following example shows the definition of the SKEDSAMPLE schedule to be run on the TWI5 workstation. This schedule includes two jobs, OS4JOB1 and OS4JOB2, each one with file dependency.

OS4JOB1 is submitted on TWI5 if the /usr/unison/components stream file exists, and OS4JOB2 is submitted on TWI5 if the QCLSRC database file exists in the QGPL library:

SCHEDULE TWI5#SKEDSAMPLE
ON RUNCYCLE RULE1 "FREQ=DAILY;"
:
TWA41OS4JOB1
OPENS TWI5#"/usr/unison/components"(-e %p)
TWA41OS4JOB2
OPENS TWI5#"/QSYS.LIB/QGPL.LIB/QCLSRC.FILE"(-e %p)
END

For more information about file dependencies, see the sections about defining dependencies and the opens keyword in HCL Workload Automation: User's Guide and Reference.