I am facing a scenario where i have an autosys Job A. And jobs B, C, D are dependent on A. When we keep the job A On Ice, B,C,D fail.
We had multiple incidents where A was kept on ice by mistake.
Is there any way that we can restrict the job A from being put On Ice?
I desperately need to avoid such incidents from happening in the future.
Use the permission attribute of the job to restrict who can edit and execute a job. Default permission is that only owner can edit and execute the job. In this case I think the user has logged into the Autosys session using the job's 'owner' credentials, and hence that person would be able to change the job's status. Solution would be to irradicate the need to put the job on ice as suggested by friends above.
OR If the user id is different, check the permission attribute in the job definition, and remove the entry. Valid values are: gx (UNIX only) Assigns group execute permissions to the job. ge (UNIX only) Assigns group edit permissions to the job. me Indicates that any authorized user may edit the job, regardless of the machine they are on. Otherwise, the user must be logged on to the machine specified in the owner field (for example, user@host_or_domain). mx Indicates that any authorized user may execute the job, regardless of the machine they are on. Otherwise, the user must be logged on to the machine specified in the owner field (for example, user@host_or_domain). we Assigns world edit permissions to the job. wx Assigns world execute permissions to the job. The job's owner always has full edit and execute permissions. Example: Set Permissions to Execute and Edit a Job on UNIX This example sets permissions on UNIX so that any user can execute the job, but only members of your group can edit it: permission: ge, wx