I have an autosys box job and 2 command jobs. When i force start the box job the command jobs are moving to 'Active' state but are not running. I have tried various options for the start times and run windows but doesnt seem to work. Any help is appreciated
The command jobs by themselves run successfully but not when i put them in a box job.
Appreciate any help.
Thanks,
Last edited by Scott; 01-11-2010 at 04:37 PM..
Reason: Please use code tags
Hi,
I have a cron schedule like this
04,16,28,40,52 * * * * /nag/startProcessABatch (unix script)
i want to add new lines in this file (like Logging), i just copy this file into a /tmp folder (for backup copy), and i have edited this file (added few lines of code for logging).
... (1 Reply)
Sir,
I using the following commands in a file (part of a bigger script):
#!/bin/bash
cd /opt/oracle/bin
ls -lt | tail -1 | awk '{print $6}' >> /tmp/ramb.out
If I run this from the command prompt the result is:
2007-05-16
if I run it as a cron job then... (5 Replies)
Hi All,
The script which i am using to SSH to remote server is working fine when i run is using ./ but when cron runs it it gives error that "ssh: not found"
please help!!! (3 Replies)
Hi all,
down here part of the scheduled job in crontab (AIX Version 5)
i have problem running jspPRE-ALL.
i verrify permissions and privileges (the others job are working good)
if i run the job in command line it work correctly
#
# Aggiornamento doni e continuity
00 02 * * 2-6... (5 Replies)
cron job not running the sqlplus command in shell script but the shell script works fine from command line..
Cronjob:
5 * * * * /home/dreg/script.sh
script.sh:
#!/bin/ksh
/oracle/u000/app/oracle/product/10204/GEN/bin/sqlplus -s <user>/<pass>@<sid/home/dreg/sqlscript.sh
... (18 Replies)
Hi All,
I am editing crontab using -e option to add a new job
Below is the line
30 * * * * scriptpath
This job is not executing every thirty minutes.
I have checked, cron daemon is running.
What did I miss? Can some one help?
I am using cron shell..ksh (7 Replies)
Hi,
I have set up the crontab as follows.
root@IDC4VASAPP07 # crontab -l
0-59 * * * * /var/tmp/r.sh
0-59 * * * * date >> /var/tmp/log
root@IDC4VASAPP07 #
r.sh is as follows.
root@IDC4VASAPP07 # cat r.sh
#!/bin/bash
dt1=$(perl -e 'use POSIX;print strftime... (10 Replies)
I have a parameter A
its value is given below
A= 'Hi Hello'
When I am trying to use this parameter in my script to call the job,its giving me invalid parameters due to space between Hi & Hello
-param A=$A
param A=Hi Hello.
in above since there space after hi it will give invalid... (9 Replies)
Hi All,
I am writing a script that will eventually be executed by a cron job every 15 minutes. I want to make sure that my logic/script doesn't get executed if a previous job is still running. What would be the best way to handle that scenario? I was thinking to make my script create a temporary... (1 Reply)
Discussion started by: rdogadin
1 Replies
LEARN ABOUT SUSE
vm-install-jobs
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)