5 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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. (2 Replies)
Discussion started by: sangea
2 Replies
2. Shell Programming and Scripting
Hi Experts,
I need a script advice to schedule 12 jobs ( SAS Codes execute back ground ).
Algorithem:
1. Script checks first job.
2. Finds first job is done; invoke second job.
3. finds second job is done; invoke third job.
..
Request you to please assist. (3 Replies)
Discussion started by: Jerald Nathan
3 Replies
3. UNIX for Dummies Questions & Answers
I have this box job and it contains only one job under it which is to load a file. I want to insert a "File Watcher", "Copy File" to it? Have no clue how to do that...any help plzzz... (4 Replies)
Discussion started by: xejatt
4 Replies
4. Solaris
Hi,
Thanks in advance.
i need to kill a unix background running job after that job process completes.
i can kill a job by giving the following unix command
kill -9 processid
how to kill the job after the current process run gets completed ?
Appreciate your valuable help.
Thanks... (7 Replies)
Discussion started by: dtazv
7 Replies
5. Shell Programming and Scripting
Hi,
Thanks in advance.
i need to kill a unix background running job after that job process completes.
i can kill a job by giving the following unix command
kill -9 processid
how to kill the job after the current process run gets completed ?
Appreciate your valuable help.
... (1 Reply)
Discussion started by: dtazv
1 Replies
LEARN ABOUT DEBIAN
globus_gram_job_manager_script_interface
globus_gram_job_manager_script_interface(3) globus gram job manager globus_gram_job_manager_script_interface(3)
NAME
globus_gram_job_manager_script_interface - Job Manager Scheduler Interface The GRAM Job Manager interfaces with the job filesystems and
scheduler through scheduler-specific Perl modules.
GRAM provides several Perl modules which can be used to implement scheduler-specific interfaces to the GRAM Job Manager. These are:
Globus::GRAM::Error
This module implements the GRAM error results as objects. Methods in this module will construct a GRAM error with the value matching
the values in the GRAM Protocol library. A scheduler-specific JobManager module may return one of these objects from its methods to
indicate errors to the Job Manager program.
Globus::GRAM::JobState
This module defines the GRAM job state constants. A scheduler-specific JobManager module returns one of these values from its methods
to indicate the managed job's current state.
Globus::GRAM::JobSignal
This module defines the GRAM job signal constant values. The Job Manager uses these values to communicate which signal is being invoked
in the manager's signal method.
Globus::GRAM::JobManager
This module defines the actual implementatoin of the Job Manager scheduler interface. One writing a scheduler-specific GRAM interface
will create a subclass of this object which overrides the default implementation's methods.
Globus::GRAM::JobDescription
This module mimics the RSL job description using perl syntax. The job manager passes an object of this type to the JobManager modules's
constructor. The job manager stores RSL and some configuration values in that JobDescription object. The manager accesses values stored
in the JobDescription by invoking methods containing the RSL attribute's name (example: $description->gram_my_job()). Method names are
handled as if they were based on the canonical RSL representation of the attribute name. For example, the gram_my_job may be
equivalently referred to as GramMyJob, grammyjob, or GRAM_My_Job.
Version 13.33 Mon Apr 30 2012 globus_gram_job_manager_script_interface(3)
