We have a problems with the processing day that one rule applies.
The name of the rule is MT3SAMES, and here is it's configuration.
Period : 1 Month
Position in period : 15 Calendar
Days of the week: Saturday
If a job is using this rule, for February, we expect this job to be scheduled for 21.02.2009 (this is the first Saturday after the 15-th of February). The schedule is correct, but the processing date is 15.02.2009, not what we expect 21.02.2009
1
1 votes
Solved : Strange processing date with rule simulation
Started by blablabla, Feb 23 2009 03:21 PM
2 replies to this topic
#2
-
- Root Admin
-
- 4,389 posts
Hero Member
- Gender:Male
- Location:Europe
Posted 23 February 2009 - 03:33 PM
Hello,
please post a uxshw of the RUL and of the Uproc and a screenshot of the simulation.
Michel
please post a uxshw of the RUL and of the Uproc and a screenshot of the simulation.
Michel
#3
-
- Root Admin
-
- 4,389 posts
Hero Member
- Gender:Male
- Location:Europe
Posted 25 February 2009 - 11:25 AM
Hello,
the Rule could be defined as "1st Saturday of the Month after the 15th (15th included)".
So the job will be scheduled for instance on the 21st for February or March 2009.
The processing date is linked to the Functional Period of the Uproc.
If you are unsure about the difference, check the Tutorial at http://www.orsypforu...p?showtopic=130.
What happens here - from what you describe, the Uproc has a functional period day - the processing date is calculated for the first possible day for the Rule (the 15th). As this day is not possible (not a Saturday), the offset is used until Saturday 21 is reached but by design Dollar Universe keeps the initial processing date - which remains the 15th.
It is possible to change this through the definition of a special variable called a "Logical Name" in a Dollar Universe specific file.
*** Before undertaking this change, do note that ***:
- you should backup the file uxlnm<Company>.dat, as making a mistake in the file can prevent your Company from starting or working correctly!
- this variable will impact all Tasks, which may cause unwanted changes to your existing jobs
- you will have to stop / restart $U to take the change into account when you have made the update
Add the following line at the bottom of the file uxlnm<Company>.dat (adapt it to your Company name, and do not delete the empty line at the bottom of the file if present):
/TABLE="LNM_<Company>"/NAME="S_CALC_REP"/VALUE="O"
Michel
the Rule could be defined as "1st Saturday of the Month after the 15th (15th included)".
So the job will be scheduled for instance on the 21st for February or March 2009.
The processing date is linked to the Functional Period of the Uproc.
If you are unsure about the difference, check the Tutorial at http://www.orsypforu...p?showtopic=130.
What happens here - from what you describe, the Uproc has a functional period day - the processing date is calculated for the first possible day for the Rule (the 15th). As this day is not possible (not a Saturday), the offset is used until Saturday 21 is reached but by design Dollar Universe keeps the initial processing date - which remains the 15th.
It is possible to change this through the definition of a special variable called a "Logical Name" in a Dollar Universe specific file.
*** Before undertaking this change, do note that ***:
- you should backup the file uxlnm<Company>.dat, as making a mistake in the file can prevent your Company from starting or working correctly!
- this variable will impact all Tasks, which may cause unwanted changes to your existing jobs
- you will have to stop / restart $U to take the change into account when you have made the update
Add the following line at the bottom of the file uxlnm<Company>.dat (adapt it to your Company name, and do not delete the empty line at the bottom of the file if present):
/TABLE="LNM_<Company>"/NAME="S_CALC_REP"/VALUE="O"
Michel
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
