Environment file: /etc./auto.profile C programs: $AUTOSYS/code Where to change AutoSys screen fonts: /usr/openwin/lib/app-defaults Where to look for troubleshooting: Chapter 15 Summary of commands: Appendix C $AUTO_JOB_NAME: when naming a file dynamically using as prefix AutoSys's job name...
Environment file: /etc./auto.profile C programs: $AUTOSYS/code Where to change AutoSys screen fonts: /usr/openwin/lib/app-defaults Where to look for troubleshooting: Chapter 15 Summary of commands: Appendix C $AUTO_JOB_NAME: when naming a file dynamically using as prefix AutoSys's job name...
SUCCESS : The job exited with an exit code equal to or less than the “maximum exit code for success.” By default, only the exit code “0” is interpreted as “success.” If the job is a box job, this value means that all the jobs within the box have finished with the status SU...
Since Open Systems maintains the same Unix ID number across all hosts, there is no need to specify a “@machine” in the “owner” JIL code parameter. Autosys will put “@machine” in automatically for anyone not a superEDIT user. When JIL code is migrated from AutoDEV to AutoQAD the ...
execute process task error ; exit code 7 expected was 0 execute process task error; exit code was 16 expected was 0 Execute Process Task: Accessing Return Value and Saving in the database. EXECUTE SQL AGENT JOB task - How to make package wait till task 1 completes before calling task 2 ...
execute process task error ; exit code 7 expected was 0 execute process task error; exit code was 16 expected was 0 Execute Process Task: Accessing Return Value and Saving in the database. EXECUTE SQL AGENT JOB task - How to make package wait till task 1 completes before calling task 2 ...
“maximum exit code for success.” By default, only the exit code “0” is interpreted as “success.” If the job is a box job, this value means that all the jobs within the box have finished with the status SUCCESS (the default), or the “Exit Condition for Box Success” evaluated...