Validity keywords
In this topic you can find the list of validity keywords.
This topic lists the keywords that you can use when planning a job stream. You can find the syntax of the scheduling keywords and related examples.
validfrom / validto
You can use these keywords to specify a time frame in which a job stream has to be included in the preproduction plan, that is a validity time.
Syntax
validfrom date
Arguments
- validfrom date
- Using this keyword, you can define from which date the job stream has to be included in the production plan, and the first date in which the instances in the preproduction plan must be included in the current plan.
Comments
You can define different versions of the same job stream by creating other job streams with the same name and workstation, but with different validity intervals. The job stream identified as the dependency is the one that has a validity interval coincident with the period in which the dependency is active. When you define a job stream version, you must enter the validfrom date only. The validto value is automatically set according to the validfrom date of the following version.
The validto date specified in the run cycle is not included in the run cycle, so the job stream does not run on that date.
The validto date is shown when issuing list and display command when MAESTROCOLUMNS is set to 120.
- In the following example, the JOBSTREAM1 job stream, which contains the
JOB_1 job, is active from December 1, 2022.
SCHEDULE WS_AGT_1#JOBSTREAM1 VALIDFROM 12/01/2022 : WS_AGT_0#JOB_1 END
draft
You can use this keyword to save the job stream as a draft so that it is not included in the plan generation process. If the job stream is referenced by dependencies, such job stream is not considered.
Syntax
draft
Comments
If you save as draft an existing job which has already been referenced, all the istances of that job do not run and the dependencies are realeased.
SCHEDULE WS_AGT_1#JOBSTREAM1 VALIDFROM 12/01/2022
DRAFT
:
WS_AGT_0#JOB_2
END