25.01.2015 Views

Managing Ensemble Productions - InterSystems Documentation

Managing Ensemble Productions - InterSystems Documentation

Managing Ensemble Productions - InterSystems Documentation

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

What to Manage<br />

the item to be stopped and started at specific times and on specific days of the week, month, or year. When it is time to<br />

start, if the item is enabled, the scheduler starts it; when it is time to stop, if the item is running, the scheduler stops it.<br />

The Schedule string is a comma-separated list of event specifications. Each event specification has the following format:<br />

action:YYYY-MM-DDThh:mm:ss<br />

Where each item in the event specification, from left to right, has the described values:<br />

Item<br />

action<br />

:<br />

YYYY-MM-DD<br />

Possible Values<br />

START or STOP indicates the desired action<br />

Required separator<br />

Either:<br />

• YYYY is the year as 4 numerals<br />

• MM is the month as 2 numerals<br />

• DD is the day of the month as 2 numerals<br />

• Any of these fields may be the single character * (asterisk) indicating all years,<br />

all months, or all days<br />

Or:<br />

• YYYY is the word WEEK<br />

• MM is the specific occurrence of the day of the week (indicated by DD) in the<br />

month (01 = first occurrence of the specific day of the week in the month, 02 =<br />

second occurrence in the month, etc.)<br />

• DD is a specific day of the week (00 = Sunday, 01 = Monday, etc.)<br />

• MM may be * for all occurrences and DD may be * for all days<br />

Once a field is specified as *, all fields to the left of it are also assumed to be *.Thus,<br />

if the DD value is *, the MM value is treated as * even if it has a specific numeric<br />

value. Similarly, if MM is *, YYYY is treated as *.<br />

T<br />

hh:mm:ss<br />

,<br />

Required separator<br />

Hour, minute, and second<br />

Use the comma separator only if there is another event specification after the current<br />

one. Do not use it at the end of the Schedule string.<br />

If your schedule contains recurring events, the Schedule setting requires both START and STOP actions. If your schedule<br />

setting is an absolute one time event, then you need only use the appropriate single START or STOP action. In most cases,<br />

Schedule strings should contain both a START and a STOP action.<br />

Some examples of Schedule strings follow:<br />

• Start the configuration item every day at 8 a.m. and stop it every day at 5 p.m.<br />

START:*-*-*T08:00:00,STOP:*-*-*T17:00:00<br />

• Stop every year on January 2 at 7 a.m. and start again on January 3 at 7 a.m.<br />

STOP:*-01–02T07:00:00,START:*-01-03T07:00:00<br />

26 <strong>Managing</strong> <strong>Ensemble</strong> <strong>Productions</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!