AppWorx, Dollar Universe and Sysload Community

 View Only
  • 1.  Adding rule to TSK in command line

    Posted May 12, 2025 03:46 PM

    Hi,

    I'm running DUAS 7, and when I try to add rule to a newly defined task on command line, I get an error.

    ./uxupd TSK APP SES=SESSION1 UPR=UPROC1 MU=MU1A  IMPL ADD rule="((CAL,01/01/2023,01/01/2036,0800,99))"
     Command : uxupd tsk app ses=SESSION1 upr=UPROC1 mu=MU1A ttype="*" tsk=* vupr=* nomodel nopartage impl add rule=((CAL,01/01/2023,01/01/2036,0800,99))
     
     
    command in error!!
    Any help is appreciated :-)
    Kind regards,
    Yves


  • 2.  RE: Adding rule to TSK in command line

    Posted May 13, 2025 04:25 AM

    Can you share what your session looks like and whether this is adding a rule to a secondary task and also the curent task and the new rule.




  • 3.  RE: Adding rule to TSK in command line

    Posted May 13, 2025 05:28 AM

    Had a look at your command and this all that is missing is the rule name needs to be in quotes

    ./uxupd TSK APP SES=SESSION1 UPR=UPROC1 MU=MU1A  IMPL ADD rule="((CAL,01/01/2023,01/01/2036,0800,99))"

    becomes

    ./uxupd TSK APP SES=SESSION1 UPR=UPROC1 MU=MU1A  IMPL ADD rule="(("CAL",01/01/2023,01/01/2036,0800,99))"




  • 4.  RE: Adding rule to TSK in command line

    Posted May 13, 2025 10:20 AM

    Hi Angus,

    I tried also.

    This is how to reproduce my setup:

    ./uxadd UPR APP upr=UPROC1 LABEL='Test UPROC' UPT=CL_INT CL_INT=/tmp/toto APPL=A0
    ./uxadd SES APP SES=SESSION1 LABEL='Test Session' HEADER=UPROC1
    ./uxadd TSK APP LABEL="Test task" SES=SESSION1 UPR=UPROC1 MU=MU1A TECHINF MULT PARALLEL type=S USER=user1
    ./uxupd TSK APP SES=SESSION1 UPR=UPROC1 MU=MU1A IMPL ADD rule="(("CAL",01/01/2023,01/01/2036,0800,99))"
    Answer is:
     Command : uxupd tsk app ses=SESSION1 upr=UPROC1 mu=MU1A ttype="*" tsk=* vupr=* nomodel nopartage impl add rule=((CAL,01/01/2023,01/01/2036,0800,99))
     
     
    command in error!!
    Kind regards,
    Yves



  • 5.  RE: Adding rule to TSK in command line

    Posted May 14, 2025 09:46 AM

    Are you able to describe what is being attempted in plain language?  Seems the error is coming from this part of the command 01/01/2023,01/01/2036,0800,99. Need to understand what the rule is meant to be doing.




  • 6.  RE: Adding rule to TSK in command line

    Posted May 14, 2025 10:03 AM

    Hi Angis,

    I simply try to add a rule for the task start every days at 8 in the morning, for a possible duration of 99 hours.

    Coming from the documentation:

    IMPL Items
    RULE=
    Rule(s) associated with the task. Allows the task to be associated (IMPL add) with one or more new scheduling or exclusion rules or to disassociate them from the task (IMPL dlt).
    Format: (([+|-]
    rule,start date[,end date,time,duration hours,duration minutes]
    )([+|-]
    rule,start date[,end date,time, duration hours,duration minutes]
    )...)
    The module ([+|-]
    rule,start date[,end date,time,duration hours,duration minutes]
    ) may be repeated a maximum of seven times in the same command.
    + or - (optional)
    , + by default, indicates a scheduling rule. - indicates an exclusion rule.
    rule
     is the code of the rule in question. If the specified rule code already begins with + or -, it is mandatory to add, to the beginning of the rule code, the + sign for a scheduling rule or the - sign for an exclusion rule
    . For example:
    RULE=((++CAL...: +CAL is a scheduling rule.
    RULE=((-+CAL...: +CAL is an exclusion rule.
    RULE=((+CAL...: CAL is a scheduling rule.
    start date
     is the application date of the rule to the task, in the format indicated by the variable U_FMT_DATE. The number of characters must be exactly respected.
    end date
     is the application end date of the rule to the task, in the format indicated by the variable U_FMT_DATE. The number of characters must be exactly respected.
    time (optional)
     in HHMM format, is the start time of the launch window. If this value is entered, duration in hours and minutes are required. Incompatible with an exclusion rule.
    duration in hours (optional)
     in HHH format, indicates the number of hours of the launch window. If this value is entered, the start time of the launch window and the duration in minutes are required. Incompatible with an exclusion rule.
    duration in minutes (optional)
     in MM format, indicates the number of additional minutes of the launch window. If this value is entered, the start time of the launch window and the duration in hours are required. Incompatible with an exclusion rule. 
    For compatibility reasons, (
    rule,date
    ) format is accepted for scheduling rules, it is equivalent to (
    rule,start date,,,,
    ). For an exclusion rule, the only parameters are (
    rule,date
    ).
    Examples
    :
    uxupd TSK EXP SES=D_LOAD_BCK UPR=D_LOAD_FIL MU=HEADQUART IMPL add rule="(("LWDM",20020701)("5DMO+",20200101,20201231,1200,01,000))"
    uxupd TSK EXP SES=D_LOAD_BCK UPR=D_LOAD_FIL MU=HEADQUART IMPL add rule="(("++FWDM",01/01/2010))"
    uxupd TSK EXP SES=D_LOAD_BCK UPR=D_LOAD_FIL MU=HEADQUART IMPL add rule="(("-+FWDM",01/01/2010))"
    uxupd TSK EXP SES=D_LOAD_BCK UPR=D_LOAD_FIL MU=HEADQUART IMPL dlt rule="("5DMO+",20020701)"