How to findsuccessful job status completion in Autosys, programatically

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Autosys Job: Job did not start

I have submitted an autosys job and force start it. Autosys hit the job 4 times to restart but it did not start and finally I terminate the job. Any idea why the job did not start. Below is the code I executed. 1214 missun0ap /export/home/bzn97r/develop/dswi/jil$ sendevent -E FORCE_STARTJOB...

2. UNIX for Dummies Questions & Answers

Shell script - Finding Autosys job status

Hi, There are 2000 jobs in the list and i need to draw their status. I put all the jobs in the list and trying to read one by one from the list and to find out the status. Help me out in correcting the script. #!/bin/csh for a in $(cat Jobs_List.txt); do source <<path>> autorep -j $a...

3. Shell Programming and Scripting

autosys job configuration for job failure.

We need to configure autosys that when a job fails continously for 3 times, we need to call another job. Is this possible in Autosys, or can anyone advice on the alternative.

4. UNIX for Advanced & Expert Users

Completion time of a cron job ?

how can we identify the task completion time which was initiated by CRON. we have 1000 of jobs whihc are runing from cron so it is not feasable to edit every cron entry or every script to add the respective code to find teh completion time. Can some one please provide a inut to find the task...

5. Windows & DOS: Issues & Discussions

Autosys unable to set the job to the status of FAILED

Hi The Autosys job that call DOS batch file which in turn calls java and this java program has successful completion though there are series of exception occurred in the data it handles and want the job to be set to Fail in its autosys, how could it be done? a.bat { java sample.class ...

6. UNIX for Dummies Questions & Answers

cron job not running to completion

am running a cron job to do a backup of all user files. the script runs properly in the terminal but only backups about 20% of the files when run by cron. the Linux system is running BASH as far as I can tell. the symbols $FILE and $DIRECTORY are defined properly and the following is the...

7. UNIX for Advanced & Expert Users

Documentation and books on Autosys Job Control Tool from Autosys

My project uses Autosys. I am new to this product and I don't know where to start from. Q1. Please provide me the link where I can get Autosys documentation Q2. Please refer a good book on Autosys. (Beginner/Intermediate Level)

8. 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 ...

9. UNIX for Dummies Questions & Answers

Job Completion Information?

Hi, I am trying to get some information on the jobs that are running. I have used the "ps" command, to get information such as 'cpu usage', 'username', 'pid', etc., I've also used the "bjobs" command to get information such as 'submit time' and 'start time'. The only thing I need now is to...

10. UNIX for Dummies Questions & Answers

Cron Sends mail to root on completion of job.

All I am running a few scripts through a cron job. This is for checking some key services that are running on by box. The problem is, everytime the cron runs, it sends a mail to the root account. The root account mails need to cleared every now and then. Is there some way I can stop these...

LEARN ABOUT DEBIAN

globus_gram_protocol_job_signal

GRAM 
Signals(3) 					       globus gram protocol						   GRAM Signals(3)

NAME

       GRAM Signals -

   Enumerations
       enum globus_gram_protocol_job_signal_t { GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_CANCEL = 1, GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_SUSPEND = 2,
	   GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_RESUME = 3, GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_PRIORITY = 4,
	   GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_COMMIT_REQUEST = 5, GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_COMMIT_EXTEND = 6,
	   GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_STDIO_UPDATE = 7, GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_STDIO_SIZE = 8,
	   GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_STOP_MANAGER = 9, GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_COMMIT_END = 10 }

Detailed Description
Enumeration Type Documentation
   enum globus_gram_protocol_job_signal_t
       GRAM Signals.

       Enumerator:

       GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_CANCEL
	      Cancel a job.

       GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_SUSPEND
	      Suspend a job.

       GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_RESUME
	      Resume a previously suspended job.

       GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_PRIORITY
	      Change the priority of a job.

       GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_COMMIT_REQUEST
	      Signal the job manager to commence with a job submission if the job request was accompanied by the (two_state=yes) RSL attribute.

       GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_COMMIT_EXTEND
	      Signal the job manager to wait an additional number of seconds (specified by an integer value string as the signal's argument)
	      before timing out a two-phase job commit.

       GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_STDIO_UPDATE
	      Signal the job manager to change the way it is currently handling standard output and/or standard error. The argument for this
	      signal is an RSL containing new stdout, stderr, stdout_position, stderr_position, or remote_io_url relations.

       GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_STDIO_SIZE
	      Signal the job manager to verify that streamed I/O has been completely received. The argument to this signal contains the number of
	      bytes of stdout and stderr received, separated by a space. The reply to this signal will be a SUCCESS message if these matched the
	      amount sent by the job manager. Otherwise, an error reply indicating GLOBUS_GRAM_PROTOCOL_ERROR_STDIO_SIZE is returned. If standard
	      output and standard error are merged, only one number should be sent as an argument to this signal. An argument of -1 for either
	      stream size indicates that the client is not interested in the size of that stream.

       GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_STOP_MANAGER
	      Signal the job manager to stop managing the current job and terminate. The job continues to run as normal. The job manager will send
	      a state change callback with the job status being FAILED and the error GLOBUS_GRAM_PROTOCOL_ERROR_JM_STOPPED.

       GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_COMMIT_END
	      Signal the job manager to clean up after the completion of the job if the job RSL contained the (two-phase = yes) relation.

Author
       Generated automatically by Doxygen for globus gram protocol from the source code.

Version 11.3							  Mon Apr 30 2012						   GRAM Signals(3)

UNIX for Dummies Questions & Answers