not sure what you want to achieve.
Do you want to have the weekday information available while running the job or after it has been executed for analytics ?
If you want to decide in your job what do to depending on the weekday, I would regard that as a poor design.
This would move scheduling functionality into your jobs code which should be avoided because it harms transparency and maintainability.
With schedulix 2.9 you can enable/disable children in a batch based on an interval allowing to select weekdays to execute.
You can use system defined parameters like $SUBMITTIME giving you a string in format YYYYMMDDHHmmss.
There is no weekday function, so you have to use date arithmetics on the timestamp to get the weekday.
What you can do, is to write this once as a utility job called SETSUBMITWEEKDAY which gets the $SUBMITTIME as a parameter and sets a RESULT parameter SUBMITWEEKDAY.
Run this job as first job in batches you need this information.
On the top level batch of those batches you can then create a child reference parameter to the SUBMITWEEKDAY result of the SETSUBMITWEEKDAY.
Now you can use the $SUBMITWEEKDAY in any command line of the other jobs in your batches.
Here is an example of a python script setting the weekday (setsubmitweekday.py):
from datetime import datetime
weekday = datetime.strptime(sys.argv, '%Y%m%d%H%M%S').strftime('%A')
cmd = "sdms-set_variable" + \
" -h '" + os.getenv('SDMSHOST') + "'" + \
" -p " + os.getenv('SDMSPORT') + \
" -j " + os.getenv('JOBID') + \
" -k " + os.getenv('KEY') + \
" SUBMITWEEKDAY " + weekday
print "cmd = " + cmd
The script assumes Env. Mapping as defined for the Scope EXAMPLES to provide SDMSHOST, SDMSPORT, JOBID and KEY to the jobs environment variables.
The run program would look like 'python setsubmitweekday.py $SUBMITTIME'