3 replies to this topic

[kyfbof]

Hi,

"upd_calendarsV10.ksh" is one of several scripts provided to us during the implementation and we now must maintain. With little or no document going with this, I need you experts out there to help me to understand what it is doing.

${UXEXE}/uxupd CAL NODE=${B_NODE} ${B_APP} MU=\" 00\" dsince="2005/01/01" dbefore="2015/12/31" attr=h to=w

Q1: Is it better to use MU=" " rather than MU=\" 00\"?
Q2: Is it better to use SINCE=2005 BEFORE=2016 rather than DSINCE ... DBEFORE ...?
Q3: How can we use MU=" 00" the default calendar, and update every Holiday to Workingday? Which operation will be the last?
Q4: Without MU=" 00", would we get the default calendar anyway ... when we first install the node?

Thanks!

[kenny]

Hi,

The General Calendar is defined as linked to MU " 00" (space zero zero).

So I would say:

Q1: Is it better to use MU=" " rather than MU=\" 00\"? No

Q2: Is it better to use SINCE=2005 BEFORE=2016 rather than DSINCE ... DBEFORE ...? No. SINCE & BEFORE are available for the uxadd CAL command, not the uxupd CAL.

Q3: How can we use MU=" 00" the default calendar, and update every Holiday to Workingday? Which operation will be the last?
This is basically what the command is doing. For the General Calendar and for the selected period, change all holidays to working days.

Q4: Without MU=" 00", would we get the default calendar anyway ... when we first install the node? I don't think so.

Kenny

[kyfbof]

kenny, on March 2 2010, 08:03 AM, said:

Hi,

The General Calendar is defined as linked to MU " 00" (space zero zero). So I would say:

Q1: Is it better to use MU=" " rather than MU=\" 00\"? No

Q2: Is it better to use SINCE=2005 BEFORE=2016 rather than DSINCE ... DBEFORE ...? No. SINCE & BEFORE are available for the uxadd CAL command, not the uxupd CAL.

Q3: How can we use MU=" 00" the default calendar, and update every Holiday to Workingday? Which operation will be the last?
This is basically what the command is doing. For the General Calendar and for the selected period, change all holidays to working days.

Q4: Without MU=" 00", would we get the default calendar anyway ... when we first install the node? I don't think so.

For A1: Hmm! From the U_command_manual_en.chm help file, under Parameter commands -> Scheduling -> Calendars -> Description of items, it said: The default calendar may be reached using the management unit " 00" (blank 0 0) or " " (blank).

So " " got less key strokes and should be fine. By the way, Q1a: why back slash quote on MU? Other commands, or other fields use quote directly.

For A2: So the default cal has holidays in it ... and it's very likely that our calendar does not match.

In summary:
A node after installed, has no calendar entries. This statement creates a calendar for the node using the default calendar, which could base on ... say Russian calendar. Hence, it would have to change all Russian's holidays to working days.

[kenny]

Hi,


For A1: Yes " " also works, if you are using a recent release of DU (533 for example). You may need a backslash to protect characters. Some commands / OSs will require it, some not, but I usually use it to avoid bad surprises.

For A2: During a node installation, the General Calendar is always created. If memory serves, by default, French Holidays are created. So we need this kind of script/command to reset these days as working days when out of France (something that is done in certain regions through the univkit).

Kenny