Requirements for running an autosys job on Windows server

 
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
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)