Forecast of jobs


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting Forecast of jobs
# 1  
Old 06-28-2017
Forecast of jobs

Hello,
I'm looking for forecast of Autosys Jobs, along with their status, in a specific time period.

I tried job_depends and autorep.
  1. Problem with autorep is, I Cannot use from and to time, like I can use with job_depends, but the results are in a simple single line format for each job, with when they were last run etc.

    Provided '-r 7' I can retrieve jobs for past 7 days, but I need for future or past, depending on the time, which the user specifies from the app.
  2. Problem with job_depends, is that, it gives me lot of unwanted(in my case) information, like dependant jobs and atomic conditions etc., which is really hard to filter the results.

All I need is JobName, current job status(hold, ice, terminated, etc.), in a specified time period.


Thanks, in advance.

Last edited by rbatte1; 06-29-2017 at 12:31 PM..
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Shell script to run multiple jobs and it's dependent jobs

I have multiple jobs and each job dependent on other job. Each Job generates a log and If job completed successfully log file end's with JOB ENDED SUCCESSFULLY message and if it failed then it will end with JOB ENDED with FAILURE. I need an help how to start. Attaching the JOB dependency... (3 Replies)
Discussion started by: santoshkumarkal
3 Replies

2. Shell Programming and Scripting

waiting on jobs in bash, allowing limited parallel jobs at one time, and then for all to finish

Hello, I am running GNU bash, version 3.2.39(1)-release (x86_64-pc-linux-gnu). I have a specific question pertaining to waiting on jobs run in sub-shells, based on the max number of parallel processes I want to allow, and then wait... (1 Reply)
Discussion started by: srao
1 Replies

3. Solaris

Cron jobs and at jobs

There are two jobs in Solaris , Cron and at jobs.. I know how to disable or enable cron jobs. How can I enable at jobs and disable it. Kindly help. Rj (2 Replies)
Discussion started by: jegaraman
2 Replies

4. Shell Programming and Scripting

Shell script for weather / forecast

#!/bin/sh #Argentina Only :s # This script requires curl and iconv, iconv is because they do not use Weather Service utf-8 ¬¬ # 87938 = Ushuaia # 87934 = Rio Grande # 87418 = Mendoza # 87582 = Capital Federal # 87692 = Mar del Plata # 87480 = Rosario # 87344 = Cordoba # 87371 = Santa Fe ... (8 Replies)
Discussion started by: yamirokuay
8 Replies

5. Shell Programming and Scripting

at jobs.

Please suggest how can i modify or change the at jobs ? (4 Replies)
Discussion started by: anupdas
4 Replies

6. Solaris

at jobs

how to schedule a reboot using the at jobs ? (3 Replies)
Discussion started by: priky
3 Replies

7. Shell Programming and Scripting

background jobs exit status and limit the number of jobs to run

i need to execute 5 jobs at a time in background and need to get the exit status of all the jobs i wrote small script below , i'm not sure this is right way to do it.any ideas please help. $cat run_job.ksh #!/usr/bin/ksh #################################### typeset -u SCHEMA_NAME=$1 ... (1 Reply)
Discussion started by: GrepMe
1 Replies

8. UNIX for Advanced & Expert Users

jobs

I am running this script below as a cron job for user root. In fact I set this job early last week and expected it to delete archive logs older than 7 days, but doesn't work - just displays the echo messages and no error. Can somebody advise me the probable causes ?? DAY_AFTER=7; export... (1 Reply)
Discussion started by: vbaskar
1 Replies
Login or Register to Ask a Question
IONADMIN(1)							  ICI executables						       IONADMIN(1)

NAME
ionadmin - ION node administration interface SYNOPSIS
ionadmin [ commands_filename | . ] DESCRIPTION
ionadmin configures, starts, manages, and stops the ION node on the local computer. It configures the node and sets (and reports on) global operational settings for the DTN protocol stack on the local computer in response to ION configuration commands found in commands_filename, if provided; if not, ionadmin prints a simple prompt (:) so that the user may type commands directly into standard input. If commands_filename is a period (.), the effect is the same as if a command file containing the single command 'x' were passed to ionadmin -- that is, the ION node's rfxclock task is stopped. The format of commands for commands_filename can be queried from ionadmin by entering the command 'h' or '?' at the prompt. The commands are documented in ionrc(5). Note that ionadmin always computes a congestion forecast immediately before exiting. The result of this forecast -- maximum projected occupancy of the DTN protocol traffic allocation in ION's SDR database -- is retained for application flow control purposes: if maximum projected occupancy is the entire protocol traffic allocation, then a message to this effect is logged and no new bundle origination by any application will be accepted until a subsequent forecast that predicts no congestion is computed. (Congestion forecasts are constrained by horizon times, which can be established by commands issued to ionadmin. One way to re-enable data origination temporarily while long-term traffic imbalances are being addressed is to declare a congestion forecast horizon in the near future, before congestion would occur if no adjustments were made.) EXIT STATUS
0 Successful completion of ION node administration. EXAMPLES
ionadmin Enter interactive ION configuration command entry mode. ionadmin host1.ion Execute all configuration commands in host1.ion, then terminate immediately. FILES
Status and diagnostic messages from ionadmin and from other software that utilizes the ION node are nominally written to a log file in the current working directory within which ionadmin was run. The log file is typically named ion.log. See also ionconfig(5) and ionrc(5). ENVIRONMENT
Environment variables ION_NODE_LIST_DIR and ION_NODE_WDNAME can be used to enable the operation of multiple ION nodes on a single workstation computer. See section 2.1.3 of the ION Design and Operations Guide for details. DIAGNOSTICS
Note: all ION administration utilities expect source file input to be lines of ASCII text that are NL-delimited. If you edit the ionrc file on a Windows machine, be sure to use dos2unix to convert it to Unix text format before presenting it to ionadmin. Otherwise ionadmin will detect syntax errors and will not function satisfactorily. The following diagnostics may be issued to the log file: Can't open command file... The commands_filename specified in the command line doesn't exist. ionadmin SDR definition failed. A node initialization command was executed, but an SDR database already exists for the indicated node. It is likely that an ION node is already running on this computer or that destruction of a previously started the previous ION node was incomplete. For most ION installations, incomplete node destruction can be repaired by (a) killing all ION processes that are still running and then (b) using ipcrm to remove all SVr4 IPC objects owned by ION. ionadmin can't get SDR parms. A node initialization command was executed, but the ion_config_filename passed to that command contains improperly formatted commands. Please see ionconfig(5) for further details. Various errors that don't cause ionadmin to fail but are noted in the log file may be caused by improperly formatted commands given at the prompt or in the commands_filename. Please see ionrc(5) for details. BUGS
If the ion_config_filename parameter passed to a node initialization command refers to a nonexistent filename, then ionadmin uses default values are used rather than reporting an error in the command line argument. Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> SEE ALSO
ionrc(5), ionconfig(5) perl v5.14.2 2012-05-25 IONADMIN(1)