Sponsored Content
Top Forums UNIX for Advanced & Expert Users creating and modifying jobs in autosys Post 34446 by dangral on Friday 21st of February 2003 11:55:32 AM
Old 02-21-2003
Suppose that you save the code into code.txt you would do the following;
jil < code.txt

and if you wanted a log:
jil <code.txt >code.log

This has to be done from an autosys command line.
Once the code is in the autosys database, you can use autorep to check the status of a job or box. For example, to check the status of sample_ls you would type:

autorep -j sample_ls

And to view the underlying JIL code, you would type:

autorep -j sample_ls -q

There are numerous other options and you really should read an Autosys guide to get an uderstanding of the relationships between jobs and boxes, runstatus, etc.
As far as troubleshooting batch problems, autosys writes an autoremote log file, and that file is placed where you specify in your setup of autosys. For example, the file might be in the /tmp directory and called auto_rem.389743.93299.1
The file should always start with auto_rem and the numbers that follow will correspond to the job ID in the database.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Searching Status for 2 Autosys jobs

I need to search for a failed status of 2 autosys jobs which write to the same logfile. Is there any way to do that on one line? I already know the following doesn't work, but is there a way to get it to work, or will I have to do a loop? RUN_STATUS=autorep -J jobname jobname if then ... (1 Reply)
Discussion started by: tekster757
1 Replies

2. Shell Programming and Scripting

Repeated execution of Autosys Jobs

post deleted ... (2 Replies)
Discussion started by: Data469
2 Replies

3. Shell Programming and Scripting

How to list the Autosys jobs thats in failure status using Shell Script

hello There, I am pretty much new to Shell Scripting and also to AutoSys. I would like to know how to list the Autosys jobs in FA status using shell scripting. I would like to get an email alert as and when any Autosys job fails. Also, it should give the path of the Log file. Could you please... (0 Replies)
Discussion started by: supragna
0 Replies

4. UNIX for Dummies Questions & Answers

How to list the Autosys jobs thats in failure status using Shell Script

Hello There, I am pretty much new to Shell Scripting and also to AutoSys. I would like to know how to list the Autosys jobs in FA status using shell scripting. I would like to get an email alert as and when any Autosys job fails. Also, it should give the path of the Log file. Could you please... (5 Replies)
Discussion started by: supragna
5 Replies

5. Shell Programming and Scripting

How to find out which jobs are referencing my AutoSys variable?

I need to list out all the AutoSys jobs that are referencing a particular AutoSys global variable. I know the autorep command will definitely need to be used here, and maybe grep as well, but I can't figure out exactly how it's to be done. For example, "autorep -q -J %jobnamewildcard% | grep... (1 Reply)
Discussion started by: dazzwater
1 Replies

6. UNIX for Advanced & Expert Users

Mutually Exclusive Autosys jobs

Hi I have 2 autosys jobs (JobA and JobB) both are in different boxes but part of one big box. I want to make them mutually exclusive so that when JobA is running then JobB should not run and wait for jobA to finish/fail/terminate and vice versa. Both jobs have their own starting conditions... (1 Reply)
Discussion started by: SPJ47
1 Replies

7. UNIX for Dummies Questions & Answers

Autosys jobs

Hi, I have a script that take one parameter as an input. for example: ./clean.sh <foldername> There are 7 different folder names that we can provide to my script and my script would delete the contents of that folder that was passed as an argument. Inorder to have this script... (3 Replies)
Discussion started by: shifahim
3 Replies

8. UNIX for Dummies Questions & Answers

Refresh the jobs in Autosys Scheduler

Can anyone please tell me how to refresh the jobs in Autosys Scheduler? ---------- Post updated at 03:19 PM ---------- Previous update was at 03:18 PM ---------- I need a command to refresh it. (2 Replies)
Discussion started by: Lakme Pemmaiah
2 Replies

9. Shell Programming and Scripting

Help required in Identifying child jobs in autosys recursively.

I have been working on to neatly present the job dependency lineage in autosys through ksh/perl and I am having trouble in recursively finding the dependency. it will be great if anyone could share their thoughts on this.? I know that job_depends in autosys will help me give first level of... (0 Replies)
Discussion started by: Vhunt
0 Replies

10. Shell Programming and Scripting

How to list autosys detail jobs?

Hi Gurus, below list is autosys job output stats, it includes boxes, sub-boxes and detail jobs. detail jobs are most right indented ones in each box. the requests is to get all these detail jobs list. the only way to identify the "detail job", is intend. auto_job ... (2 Replies)
Discussion started by: green_k
2 Replies
globus_gram_job_manager_configuration(3)		      globus gram job manager			  globus_gram_job_manager_configuration(3)

NAME
globus_gram_job_manager_configuration - Job Manager Configuration The Job Manager is generally configured using the setup-globus-gram-job- manager setup script. This section of the Job Manager manual describes all options which may be passed to the GRAM Job Manager in the configuration file $GLOBUS_LOCATION/etc/globus-job-manager.conf. Configuration File Options -k Indicate that the job manager was built with the kerberos GSSAPI instead of GSI. This disables checks for a delegated GSI credential. -home GLOBUS_LOCATION Set the GLOBUS_LOCATION environment variable to the specified Globus-Location. -target-globus-location GLOBUS_LOCATION Set the GLOBUS_LOCATION environment variable to the execution node's GLOBUS_LOCATION, if different than the GRAM node's GLOBUS_LOCATION -type JOB_MANAGER_TYPE Set the type of scheduler interface to use for this job manager. A similarly named Perl module in the $GLOBUS_LOCATION/lib/perl/Globus/GRAM/JobManager/ directory is needed. -history PATH Set the path to the directory to store job history files. -cache-location PATH Set the path for the GASS cache. This path must be unique for each user. RSL substitutions (such as /tmp/buildd and pbuilder) may be used in this path. See RSL Substitions for a list of available RSL substitutions. -extra-envvars VAR1[=VAL],VAR2,... The Job manager will attempt to get the listed VARs from its environment and set them the same for the job's environment. For example, -extra-envvars LD_LIBRARY_PATH,GLOBUS_TCP_PORT_RANGE -scratch-dir-base PATH Set the default scratch directory root for the job manager. Job-specific scratch directories will be created as a subdirectory of this directory. RSL substitutions (such as /tmp/buildd and pbuilder) may be used in this path. See RSL Substitions for a list of available RSL substitutions. If this option is not present in the configuration file, then the job manager will create scratch directories as subdirectories of the user's home directory. -condor-arch ARCH Set the condor architecture for this job manager to be the specified ARCH. This is optional when the job manager type is condor. -condor-os OSNAME Set the condor operating system name for this job manager to be the specified OSNAME. This is optional when the job manager type is condor. -globus-gatekeeper-host HOST Set the name of the gatekeeper host. This will be made available in the GLOBUS_GATEKEEPER_HOST RSL substitution. -globus-gatekeeper-port PORT Set the TCP port of the gatekeeper. This will be made available in the GLOBUS_GATEKEEPER_PORT RSL substitution. -globus-gatekeeper-subject SUBJECT Set the GSI subject name of the gatekeeper. This will be made available in the GLOBUS_GATEKEEPER_SUBJECT RSL substitution. -globus-host-manufacturer MANUFACTURER Set the manufacturer name of the host machine. This will be made available in the GLOBUS_HOST_MANUFACTURER RSL substitution. -globus-host-cputype CPUTYPE Set the cpu type of the host machine. This will be made available in the GLOBUS_HOST_CPUTYPE RSL substitution. -globus-host-osname OSNAME Set the operating system name of the host machine. This will be made available in the GLOBUS_HOST_OSNAME RSL substitution. -globus-host-osversion OSVERSION Set the operating system version of the host machine. This will be made available in the GLOBUS_HOST_OSVERSION RSL substitution. -globus-tcp-port-range RANGE Set the range of TCP port numbers which the job manager will use. This will also be made available in the GLOBUS_TCP_PORT_RANGE environment variable and RSL substitution. -globus-tcp-source-range RANGE Set the range of TCP source port numbers which the job manager will use. This will also be made available in the GLOBUS_TCP_SOURCE_RANGE environment variable and RSL substitution. -state-file-dir PATH Set the path to store job manager state files (used for restarting a job manager which fails). If this is not set, then job state files will be stored in the $GLOBUS_LOCATION/tmp/gram_job_state directory. -x509-cert-dir PATH Set the path to the X.509 trusted certificate directory on the job execution hosts. If not present, then the trusted certificate directory used by the job manager (usually set by the Gatekeeper) will be used -seg-module MODULE Use the named module as a way to interact with the scheduler instead of polling for job status. -audit-directory DIRECTORY Store job auditing records in DIRECTORY. This directory should be sticky and group writable but not group readable. Audit records can be uploaded to a database by using the globus-gram-audit command. -globus-toolkit-version VERSION-STRING Use the string VERSION-STRING as the toolkit version in audit records. -enable-syslog Send log messages to the system log. -stdio-log LOG_DIRECTORY Obsolete way to set the directory for writing log messages. Messages will be written to LOG_DIRECTORY/gram_DATE.log. Use -log-pattern instead -log-pattern PATTERN RSL-substituted pattern for naming log files. Possible variables are HOME, LOGNAME, DATE. The -stdio-log is equivalent to -log-pattern /tmp/buildd/gram_.log -log-levels [FATAL|ERROR|WARN|DEBUG|INFO|TRACE] List of log levels to enable site-wide. These may be joined by the '|' character. Version 13.33 Mon Apr 30 2012 globus_gram_job_manager_configuration(3)
All times are GMT -4. The time now is 07:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy