Job Management Partner 1/Automatic Job Management System 3 Command Reference 2
This paragraph explains how to specify a file monitoring job definition.
The following gives the format of, and the parameters for a file monitoring job definition.
- Format
[flwf="name-of-file-to-be-monitored";] [flwc=c[:d[:{s|m}]];] [flwi=monitoring-interval;] [flco={y|n};] [jpoif=?macro-variable-name?:take-over-information-name;] [etm=n;] [fd=time-required-for-execution;] [ex="execution-agent-name";] [ha={y|n};] [eu={ent|def};] [ets={kl|nr|wr|an};]
- Parameters
- flwf="name-of-file-to-be-monitored";
- Define the name of a file to be monitored.
- You can set a character string of 1 to 255 bytes. You can specify a full-path file name or wildcard characters using the wildcard (*). However, you cannot use the wildcard for wildcard characters when you specify 1 to 9 as the monitor interval in the flwi parameter.
- If you want to use a double quotation mark (") or a number sign (#) as a character, prefix the character by #. That is, use #" instead of " and use ## instead of #.
- flwc=c[:d[:{s|m}]];
- Define the monitoring conditions. You can specify multiple items. However, you cannot specify s together with m. The default is c.
- c: Monitors file creation.
- d: Monitors file deletion.
- s: Monitors file resizing.
- m: Monitors for a change in the writing time of the last file.
- flwi=monitoring-interval;
- Define a time interval to monitor a file.
- You can set 1 to 600 (seconds). However you cannot use the wildcard for wildcard characters when you specify a value of 1 to 9 as the monitor interval in the flwi parameter. The default is 60.
- flco={y|n};
- Defines whether or not to make monitor conditions true if c is specified in the flwc parameter and if the file to be monitored exists when the file monitoring job is executed. You can specify this parameter only when c is specified in the flwc parameter. The default is n.
- y: Makes the monitor conditions true, thus terminating the job normally.
- n: Monitors how a monitor target file is created after the file monitoring job is executed.
- jpoif=?macro-variable-name?:take-over-information-name;
- Define a macro variable name in the ?AJS2xxxxxxxxx? format. That is, the character string xxxxxxxxx is preceded by AJS2 and the entire string is enclosed in a pair of question marks (?). Note that only uppercase alphabetic and numeric characters and periods (.) can be used in the xxxxxxxxx part.
- You can set a character string of 1 to 64 bytes as the macro variable name, which corresponds to the ?AJS2xxxxxxxxx? part.
- This parameter can contain up to 2,048 bytes in the "jpoif=?macro-variable-name?:take-over-information-name;" format.
- This parameter makes it possible to take over event information of subsequent Unix jobs, PC jobs, and action jobs.
- etm=n;
- Define the time-out period using the relative minutes from the start time. You can set 1 to 1,440 minutes. This parameter is invalid for a job within the start condition.
- fd=time-required-for-execution;
- Define the time-required-for-execution within which the job is expected to be terminated.
- You can specify a decimal value between 1 and 1,440 (minutes).
- ex="execution-agent-name";
- Define the name of the execution agent that is used to execute jobs. You can set a character string of 1 to 255 bytes.
- ha={y|n};
- Define whether to suspend job execution. The default is n. This parameter is invalid for a job within the start condition.
- y: Suspends jobnet execution.
- n: Does not suspend jobnet execution.
- eu={ent|def};
- Define the JP1 user who executes the job. The default is ent. This parameter is ignored in an event job.
- ent: The JP1 user who registered the jobnet executes the job.
- def: The JP1 user who owns the job executes the job.
- ets={kl|nr|wr|an};
- Define the state of the event job after the execution time-out period elapses. The default is kl. This parameter is invalid for a job within the start condition.
- kl: Killed
- nr: Ended normally
- wr: Ended with warning
- an: Ended abnormally
Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.