03-17-2013
Autosys Chase Error
Hi All,
We use Autosys to schedule and report job which runs in UNIX machine. Most of the job runs fine. But we have problem with one of the file watcher job . The Job is defined to run from 2nd to 10th Business day of every month starting 06:00 PT to 17:00 PT. It watches for a file in a directory. It's in running state for a long time then suddenly the job fails with chase error.
Chase error being remote agent not available in the machine. Can you please tell me how to trap this issue and avoid it.
This job is running in the same machine where rest of the jobs are running fine.
Thanks,
Lokesh Kumar C
6 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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) (0 Replies)
Discussion started by: gram77
0 Replies
2. UNIX for Advanced & Expert Users
Hi All,
I am working for all the days to find out the error . Checked in Google as well . No hope ..
I am getting the below error
ALARM: EVENT_HDLR_ERROR JOB
When i run a job in AUTOSYS . After that the total queue is blocked . Can any one please let me know what this error... (1 Reply)
Discussion started by: arunkumar_mca
1 Replies
3. UNIX for Dummies Questions & Answers
(sys10:pt:/pf>) cat 122974qqq.s
RUNAS Version 2007.10.07 Run on Dec 11 2008 10:09:36 AM
UNIX Process: 26021
Login User : root
PFW User : s08280
Not a terminal
stty: : Not a typewriter
stty: : Not a typewriter
ksh: jil: not found
ksh: sendevent: not found... (1 Reply)
Discussion started by: arunkumar_mca
1 Replies
4. Shell Programming and Scripting
Hi All
Something really weird happened, I have an autosys job:
insert_job: CAT_LDN_BaseCorrs job_type: c
command: $$(LDNFIRC)\CAT_LDN_BaseCorrs.bat -modeldate $$MODEL_DATE -cutdate $$CUT_DATE
permission: gx, mx, wx
description: "Rerun=0;625;#CAT_Autosys"
std_out_file:... (0 Replies)
Discussion started by: evilsmile2004
0 Replies
5. UNIX for Dummies Questions & Answers
All the autosys jobs are on server-1 and server-1 has been crashed due to some reason, Now I have to run 5 autosys jobs on server-2 (failover server) which are on server 1.
How to do with Autosys command (which command needs to fired on JIL) (0 Replies)
Discussion started by: tp2115
0 Replies
6. UNIX and Linux Applications
Just had a migration from Autosys 4.5 to R11.3.
After the migration to R11.3, Autosys jobs have been failing when the log file reaches a size of 800 MB.
This did not happen before the migration, when Autosys 4.5 was used.
Is there a way to configure the file size limit/cap in Autosys... (1 Reply)
Discussion started by: kimo222
1 Replies
LEARN ABOUT DEBIAN
globus_gram_protocol_job_state
GRAM Job States(3) globus gram protocol GRAM Job States(3)
NAME
GRAM Job States -
Enumerations
enum globus_gram_protocol_job_state_t { GLOBUS_GRAM_PROTOCOL_JOB_STATE_PENDING = 1, GLOBUS_GRAM_PROTOCOL_JOB_STATE_ACTIVE = 2,
GLOBUS_GRAM_PROTOCOL_JOB_STATE_FAILED = 4, GLOBUS_GRAM_PROTOCOL_JOB_STATE_DONE = 8, GLOBUS_GRAM_PROTOCOL_JOB_STATE_SUSPENDED = 16,
GLOBUS_GRAM_PROTOCOL_JOB_STATE_UNSUBMITTED = 32, GLOBUS_GRAM_PROTOCOL_JOB_STATE_STAGE_IN = 64, GLOBUS_GRAM_PROTOCOL_JOB_STATE_STAGE_OUT
= 128, GLOBUS_GRAM_PROTOCOL_JOB_STATE_ALL = 0xFFFFF }
Detailed Description
The globus_gram_protocol_job_state_t contains information about the current state of the job as known by the job manager.
Job state changes are sent by the Job Manager to all registered clients. A client may ask for information from the job manager via the
status request.
Enumeration Type Documentation
enum globus_gram_protocol_job_state_t
GRAM Job States.
Enumerator:
GLOBUS_GRAM_PROTOCOL_JOB_STATE_PENDING
The job is waiting for resources to become available to run.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_ACTIVE
The job has received resources and the application is executing.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_FAILED
The job terminated before completion because an error, user-triggered cancel, or system-triggered cancel.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_DONE
The job completed successfully.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_SUSPENDED
The job has been suspended. Resources which were allocated for this job may have been released due to some scheduler-specific
reason.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_UNSUBMITTED
The job has not been submitted to the scheduler yet, pending the reception of the GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_COMMIT_REQUEST
signal from a client.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_STAGE_IN
The job manager is staging in files to run the job.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_STAGE_OUT
The job manager is staging out files generated by the job.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_ALL
A mask of all job states.
Author
Generated automatically by Doxygen for globus gram protocol from the source code.
Version 11.3 Mon Apr 30 2012 GRAM Job States(3)