This is a control statement for setting message events.
Synopsis
MSG ---------- (1) jobnetname Job net name ---------- (2) (*) (Note 1) messagemode Message condition ---------- (3) carryover Carryover processing ---------- (4) (Note 2) messagename Message event name ---------- (5) ;
The jobnetname operand should be specified immediately after the MSG keyword.
The carryover operand should be specified immediately after the messagemode operand.
This must be specified.
About This Control Statement
(1) MSG
This is the keyword which indicates the beginning of a message event control statement.
(2) jobnetname Job net name
Specify the name of a job net for which message events are to be set.
When you specify a startup days control statement and a temporary changes control statement along with this statement, specify the same job net name across those statements.
(3) messagemode Message condition
When you specify this operand, combine the message event waiting condition (AND/OR), execution condition (ORD/COG/BOT/UNC), and the condition with the execution time (ANDTIME/ORTIME). If this operand is omitted, it is defaulted to "AND,UNC,ORTIME" as its parameter. "Valid during job net execution" ("ORD" and "BOT") cannot be specified for the "execution condition" if "ANDTIME" is specified as the "condition with the execution time" or if the job net belongs to a group. When the job net belongs to a group, the value specified for the "condition with the execution time" is ignored.
Starts the job net if all of the registered message events are generated.
Starts the job net if at least one of the registered message events is generated.
"Valid during job net execution" is specified. Message events generated while the job net is being executed become valid as the execution condition. Therefore, as soon as the job net is terminated, it is restarted as many times as the message events were generated during execution. The message events generated during execution of the job net become invalid as the execution condition if this parameter is not specified.
"Valid only on startup days" is specified. Starts the job net only if the specified message event is generated on a selected startup days.
"Valid during job net execution & Valid only on startup days" is specified. If the specified message event is generated on a selected startup days, the job net is executed as many times as the number of message events generated.
Specify this parameter when the execution condition is not set.
Starts the job net when the scheduled startup time is reached and the awaiting message event occurs. This parameter is valid only when the startup condition of the job net is set to "single startup" ("single startup (temporary change)" during a temporary change period).
Starts the job net either when the scheduled startup time is reached or the awaiting message event is generated.
(4) carryover Carryover processing
Specifies that processing be carried over when the day change time is reached. This can be specified if the job net waits for the startup time to arrive ("ANDTIME" is specified in the messagemode operand), or if the startup conditions are for the job net to start only when a certain message event has occurred ("ON" is specified in the msgonly operand). The default value is "RESET".
Carrying over the job net process is not performed when the day change time is reached.
Carrying over the job net process is performed when the day change time is reached.
(5) messagename Message event name
Specify a message event that triggers startup of the job net, using up to 12 bytes. The message event name cannot contains a comma (,), a colon (:), a blank, and a user-defined character. If using a function (jobschdeftocsv command, jobschcsvtodef command, Job Designer, Import, Export) that handles message event names in a CSV file, the message event name cannot contain a semicolon (;). Up to 70 message event names per one job net can be registered.
Example of message event setting
To register three message events, MSG1, MSG2 and MSG3:
messagename MSG1,MSG2,MSG3
