now, I tried looking at the User manuals I can find on the internet concerning autosys but these manuals seem to be quite confusing to me.
My question is, does anyone have a straight forward explanation on how to modify and/or create jobs in autosys??? (3 Replies)
I need to search for a failed status of 2 autosys jobs which write to the same logfile. Is there any way to do that on one line? I already know the following doesn't work, but is there a way to get it to work, or will I have to do a loop?
RUN_STATUS=autorep -J jobname jobname
if
then
... (1 Reply)
hello There,
I am pretty much new to Shell Scripting and also to AutoSys. I would like to know how to list the Autosys jobs in FA status using shell scripting. I would like to get an email alert as and when any Autosys job fails. Also, it should give the path of the Log file.
Could you please... (0 Replies)
I need to list out all the AutoSys jobs that are referencing a particular AutoSys global variable.
I know the autorep command will definitely need to be used here, and maybe grep as well, but I can't figure out exactly how it's to be done. For example, "autorep -q -J %jobnamewildcard% | grep... (1 Reply)
Hi
I have 2 autosys jobs (JobA and JobB) both are in different boxes but part of one big box. I want to make them mutually exclusive so that when JobA is running then JobB should not run and wait for jobA to finish/fail/terminate and vice versa.
Both jobs have their own starting conditions... (1 Reply)
Can anyone please tell me how to refresh the jobs in Autosys Scheduler?
---------- Post updated at 03:19 PM ---------- Previous update was at 03:18 PM ----------
I need a command to refresh it. (2 Replies)
I have been working on to neatly present the job dependency lineage in autosys through ksh/perl and I am having trouble in recursively finding the dependency.
it will be great if anyone could share their thoughts on this. (2 Replies)
I have been working on to neatly present the job dependency lineage in autosys through ksh/perl and I am having trouble in recursively finding the dependency.
it will be great if anyone could share their thoughts on this.?
I know that job_depends in autosys will help me give first level of... (0 Replies)
Hi Gurus,
below list is autosys job output stats, it includes boxes, sub-boxes and detail jobs. detail jobs are most right indented ones in each box. the requests is to get all these detail jobs list.
the only way to identify the "detail job", is intend.
auto_job ... (2 Replies)
Discussion started by: green_k
2 Replies
LEARN ABOUT V7
pts_chown
PTS_CHOWN(1) AFS Command Reference PTS_CHOWN(1)NAME
pts_chown - Changes the owner of a Protection Database entry
SYNOPSIS
pts chown -name <group name> -owner <new owner>
[-cell <cell name>] [-noauth] [-localauth] [-force] [-help]
pts cho -na <group name> -o <new owner>
[-c <cell name>] [-no] [-l] [-f] [-h]
DESCRIPTION
The pts chown command designates the user or group named by the -owner argument as the owner of the group named by the -name argument, and
records the new owner in the owner field of the group's Protection Database entry.
In the case of regular groups, this command automatically changes the group name's owner prefix (the part of the group name before the
colon) to match the new owner. If the new owner is itself a group, then only its owner prefix, not its complete name, becomes the owner
prefix in the new name. The change to the owner prefix does not propagate to any groups owned by the group, however. To make the owner
prefix of such group-owned groups reflect the new owning group, use the pts rename command.
It is not possible to change a user or machine entry's owner from the default set at creation time, the system:administrators group.
CAUTIONS
While designating a machine as a group's owner does not cause an error, it is not recommended. The Protection Server does not extend the
usual privileges of group ownership to users logged onto the machine.
OPTIONS -name <group name>
Specifies the current name of the group to which to assign a new owner.
-owner <new owner>
Names the user or group to become the group's owner.
-cell <cell name>
Names the cell in which to run the command. For more details, see pts(1).
-force
Enables the command to continue executing as far as possible when errors or other problems occur, rather than halting execution at the
first error.
-help
Prints the online help for this command. All other valid options are ignored.
-localauth
Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. Do not combine this flag with the -cell or
-noauth options. For more details, see pts(1).
-noauth
Assigns the unprivileged identity anonymous to the issuer. For more details, see pts(1).
EXAMPLES
The following example changes the owner of the group "terry:friends" from the user "terry" to the user "pat". A side effect is that the
group name changes to "pat:friends".
% pts chown -name terry:friends -owner pat
The following example changes the owner of the group "terry:friends" from the user "terry" to the group "pat:buddies". A side effect is
that the group name changes to "pat:friends".
% pts chown -name terry:friends -owner pat:buddies
PRIVILEGE REQUIRED
The issuer must belong to the system:administrators group or currently own the group.
SEE ALSO pts(1), pts_rename(1)COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas
Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.
OpenAFS 2014-04-08 PTS_CHOWN(1)