Sponsored Content
Top Forums Shell Programming and Scripting Repeated execution of Autosys Jobs Post 302171499 by gnom on Thursday 28th of February 2008 03:20:41 PM
Old 02-28-2008
Hi

I would execute this script via a cronjob at exactely the desired time and u can do it manually.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

creating and modifying jobs in autosys

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)
Discussion started by: TRUEST
3 Replies

2. UNIX for Dummies Questions & Answers

Searching Status for 2 Autosys jobs

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)
Discussion started by: tekster757
1 Replies

3. Shell Programming and Scripting

How to list the Autosys jobs thats in failure status using Shell Script

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)
Discussion started by: supragna
0 Replies

4. Shell Programming and Scripting

How to find out which jobs are referencing my AutoSys variable?

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)
Discussion started by: dazzwater
1 Replies

5. UNIX for Advanced & Expert Users

Mutually Exclusive Autosys jobs

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)
Discussion started by: SPJ47
1 Replies

6. UNIX for Dummies Questions & Answers

Autosys jobs

Hi, I have a script that take one parameter as an input. for example: ./clean.sh <foldername> There are 7 different folder names that we can provide to my script and my script would delete the contents of that folder that was passed as an argument. Inorder to have this script... (3 Replies)
Discussion started by: shifahim
3 Replies

7. UNIX for Dummies Questions & Answers

Refresh the jobs in Autosys Scheduler

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)
Discussion started by: Lakme Pemmaiah
2 Replies

8. Shell Programming and Scripting

Urgent. Script to identify child jobs in autosys recursively

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)
Discussion started by: Vhunt
2 Replies

9. Shell Programming and Scripting

Help required in Identifying child jobs in autosys recursively.

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)
Discussion started by: Vhunt
0 Replies

10. Shell Programming and Scripting

How to list autosys detail jobs?

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
vm-install-jobs(8)					      System Manager's Manual						vm-install-jobs(8)

NAME
vm-install-jobs - queries and manages VM creation jobs that were started by vm-install SYNOPSIS
vm-install-jobs [options ...] DESCRIPTION
VMs may be created by vm-install interactively, or as backgrounded jobs. The vm-install-jobs command manages backgrounded VM creation jobs. OPTIONS
--cancel job-id Cancels the specified job. If the VM is still running, it is stopped. This command may return before the VM is completely stopped or the vm-install process has completely exited. The job is not implicitly deleted, so that the cancelation progress may be observed. --delete job-id Deletes the specified job. The job must be in one of the FINISHED, FAILED, or CANCELED states. The VM's configuration is deleted, as are any disks that were created during the job. --detach job-id Detaches the created VM from the specified job. The job must be in the FINISHED state. The job is deleted, but the VM's configura- tion and its disks are left intact. --list Lists all known VM creation jobs, by ID. One job ID is output per line. --status job-id Outputs the status of the specified job. JOB STATES
Every job is always in one of the following states: 0: SETTINGS 1: PREP_INSTALL 2: INSTALL 3: POST_INSTALL 4: RUNTIME_CONF 5: RUNTIME 6: FINISHED 7: FAILED 8: CANCELED The normal progression is from state 0 to state 6. States 6, 7, and 8 are terminal states. JOB STATUS
Querying the job status will print (to stdout) a number of key/value pairs. The possible keys and their meanings are: exit The exit code of the VM creation job. This key is only present once the job is in one of the states FINISHED, FAILED, or CANCELED. To interpret the meaning of the exit code, see vm-install(8) id The job ID. Always present. inotify A filename to monitor (via inotify(7) ) for state changes. The recommended inotify mask to use is IN_CLOSE_WRITE. Always present. log The location of the log file. Always present. pid The process ID of the VM creation job. This key is only present if the VM creation process is still running. The PID is used internally to cancel the job. state The job's current state. See JOB STATES. Always present. uuid The VM's UUID. This key is only present once all of the VM's settings have been gathered. vnc The last known location to view the VM's console via VNC. Note that the presence of this key does not guarantee that the VM is cur- rently running. When no authentication is necessary, the URL will be ip::port. If authentication is necessary, the URL will be username:password@ip::port. DIAGNOSTICS
A zero exit code indicates success; non-zero indicates failure. Note that the exit code of this tool indicates the success of the job management command. It does not represent the success or failure of the job itself. SEE ALSO
To interpret the exit code of a job or of this command, see vm-install(8) To monitor state changes of jobs, see inotify(7) To report problems with this software or its documentation, visit http://bugzilla.novell.com 2007-02-01 vm-install-jobs(8)
All times are GMT -4. The time now is 10:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy