Login or Register to Ask a Question and Join Our Community


Windows & DOS: Issues & Discussions

Requirements for running an autosys job on Windows server

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums Windows & DOS: Issues & Discussions Requirements for running an autosys job on Windows server
# 1  
Old 10-15-2009
Requirements for running an autosys job on Windows server
Hi, I have created an autosys job which calls an exe and updates its output files. The job is failing without updating the output and error files.
I if restart the usvmapgrnd01.pc.ml.com machine, the job runs successful for first time and fails rest of the time. Please let me know what might be the solution for this issue.

The definition of the autoys job is as follows:

Code:
/* ----------------- GSRW_CD_AUTOSYS_DEV ----------------- */ insert_job: GSRW_CD_AUTOSYS_DEV job_type: c 
command: d\:\apps\CPM5.0\web\GreensheetDotNet\AutoExe\bin\Debug\SampleTestForAutosys.exe machine: usvmapgrnd01.pc.ml.com 
owner: gstautos@amrs 
permission: ge, gx,me,mx 
date_conditions: 1 
days_of_week: mo,tu,we,th,fr,sa,su 
start_mins: 00, 15, 30, 45 
term_run_time: 60 
std_out_file: >>d\:\apps\CPM5.0\web\GreensheetDotNet\Autoexe\bin\debug\GSRW_CD_AUTOSYS_DEV.out std_err_file: >>d\:\apps\CPM5.0\web\GreensheetDotNet\Autoexe\bin\debug\GSRW_CD_AUTOSYS_DEV.err alarm_if_fail: 0

On usvmapgrnd01.pc.ml.com machine, the user gstautos has full access. If I run the exe, it is running fine. Please let me know what might be the reason.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Job Run Slower using Autosys than running through terminal

Hi All, We run Many jobs evryday using Autosys. Sometimes due to various reason we got to run the job from terminal as well (using nohup). We observed that the job running through terminal(nohup) takes much less time then the autosys (for same job). What can be the possible reason for such... (1 Reply)
Discussion started by: kg_gaurav
1 Replies

2. 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... (0 Replies)
Discussion started by: jnrohit2k
0 Replies

3. UNIX for Advanced & Expert Users

Autosys Scheduler- Running job at particular time

Hi Experts, I am new to Autosys. I created a Autosys box job to run at 10 AM daily. As scheduled, the job starts on time. There is another box job inside the box. I have scheduled it to run at 11 AM but it kicks off automatically with the main job at 10 AM. insert_job: Main-job ... (2 Replies)
Discussion started by: pk_bohra
2 Replies

4. UNIX for Advanced & Expert Users

Autosys Job Running every 5th Day of Month

Hi, Is there a way to schedule a job in Autosys to run every 5th Day of Month without using custom calendar? Thanks. (1 Reply)
Discussion started by: vbhatnag
1 Replies

5. 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. (2 Replies)
Discussion started by: sangea
2 Replies

6. UNIX for Advanced & Expert Users

report of autosys job in RUNNING state

I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB). What I am after is the list of all the jobs that ran between AND during timeA and timeB. Jobs within the timeframe could either: A: STARTING --> RUNNING --> SUCCESS/FAILURE etc.. B: ... (1 Reply)
Discussion started by: rgilan01
1 Replies

7. Solaris

report of autosys job in RUNNING state

I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB). What I am after is the list of all the jobs that ran between AND during timeA and timeB. Jobs within the timeframe could either: A: STARTING --> RUNNING --> SUCCESS/FAILURE etc.. B: ... (2 Replies)
Discussion started by: rgilan01
2 Replies

8. Programming

report of autosys job in RUNNING state

I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB). What I am after is the list of all the jobs that ran between AND during timeA and timeB. Jobs within the timeframe could either: A: STARTING --> RUNNING --> SUCCESS/FAILURE etc.. B: ... (0 Replies)
Discussion started by: rgilan01
0 Replies

9. Shell Programming and Scripting

report of autosys job in RUNNING state

I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB). What I am after is the list of all the jobs that ran between AND during timeA and timeB. Jobs within the timeframe could either: A: STARTING --> RUNNING --> SUCCESS/FAILURE etc.. B: ... (0 Replies)
Discussion started by: rgilan01
0 Replies

10. 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) (0 Replies)
Discussion started by: gram77
0 Replies
Login or Register to Ask a Question

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)