Sponsored Content
Special Forums Windows & DOS: Issues & Discussions AutoSys Job not waiting for script to complete Post 302736519 by ajomarquez on Tuesday 27th of November 2012 12:00:57 PM
Old 11-27-2012
The job is being submitted to a Windows server.
 

10 More Discussions You Might Find Interesting

1. 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

2. Programming

parent not waiting until child complete executing another program through execl()

Hi, I am calling a program that greps and returns 72536 bytes of data on STDOUT, say about 7000 lines of data on STDOUT. I use pipe from the program am calling the above program. Naturally, I execute the above program (through execl() ) throught the child process and try to read the... (4 Replies)
Discussion started by: vvaidyan
4 Replies

3. Shell Programming and Scripting

autosys job name in the called script

Hi, i have an autosys job 'AUTJOBA' that calls a script script1.sh Now, inside the script i would like to know the autosys job that kicked off this script. When AUTJOBA runs script1.sh, will it set an environmental variable for this shell session that can be accessed within this script? ... (1 Reply)
Discussion started by: ysrinu
1 Replies

4. Solaris

Timed out waiting for Autonegotiation to complete

Received the Timed out message consistently when I tried to jumpstart an M5000 with: boot jsnet:speed=1000,duplex=full - install Made the error go away by adding link-clock parameter: boot jsnet:speed=1000,duplex=full,link-clock=master - install "link-clock=master" disables... (1 Reply)
Discussion started by: markoakley
1 Replies

5. UNIX for Dummies Questions & Answers

Shell script - Finding Autosys job status

Hi, There are 2000 jobs in the list and i need to draw their status. I put all the jobs in the list and trying to read one by one from the list and to find out the status. Help me out in correcting the script. #!/bin/csh for a in $(cat Jobs_List.txt); do source <<path>> autorep -j $a... (1 Reply)
Discussion started by: venkatesht
1 Replies

6. Shell Programming and Scripting

Please help me to develop this script for autosys job

:wall:Hi All, I want to build script to force start the list of child jobs under a box. I prepared this below script, but this script need to some bug fix at run time. Please help me to to develop this script. Please let me know if any thing require for this script. Advance thank for all.. ... (3 Replies)
Discussion started by: pradipta_pks
3 Replies

7. Shell Programming and Scripting

Waiting for a process to complete in shell script

Hi, I need to initiate a process script which will start and do some processing and then shuts down. Then i need to other verifications. But the the process takes around 25 to 3o minutes. One thing i can monitor the nohup.out file for this process where i can wait for shutting down statement to... (3 Replies)
Discussion started by: Prashanth19
3 Replies

8. UNIX for Dummies Questions & Answers

To run ksh script via autosys job without asking password for file transfer

I've K shell script. It will transfer the files from one server to other server using 'SCP' command. While running the script alone as a command line in UNIX ssh terminal its running with out asking password and files are transferred with out asking for password. But by running the script using... (6 Replies)
Discussion started by: maheshbabu
6 Replies

9. UNIX for Beginners Questions & Answers

Automation script for email alert when a job get complete with status successful.

Guyz, Please let me know about script which is to be sending an automatic email to particular mail id's when a monotoring job get complete with status successful. (1 Reply)
Discussion started by: Rehan Ahmad
1 Replies

10. Shell Programming and Scripting

Subprocess.popen() should write to log without waiting for process to complete

Here is my test code process = sp.Popen( + , bufsize=1, universal_newlines=True, stdout=sp.PIPE, stderr=sp.STDOUT, cwd=src_home) output, _ =... (2 Replies)
Discussion started by: ezee
2 Replies
BACKUP_JOBS(8)						       AFS Command Reference						    BACKUP_JOBS(8)

NAME
       backup_jobs - Lists pending and running operations in interactive mode

SYNOPSIS
       jobs [-help]

       j [-h]

DESCRIPTION
       The backup jobs command lists the job ID number and status of each backup operation running or pending in the current interactive session.

       This command can be issued in interactive mode only. If the issuer of the backup interactive command included the -localauth flag, the
       -cell argument, or both, those settings apply to this command also.

       To terminate operations that appear in the output, issue the backup kill command and identify the operation to cancel with the job ID
       number from this command's output.

       To check the status of a Tape Coordinator, rather than of a certain operation, use the backup status command.

OPTIONS
       -help
	   Prints the online help for this command. All other valid options are ignored.

OUTPUT
       The output always includes the expiration date and time of the tokens that the backup command interpreter is using during the current
       interactive session, in the following format:

	  <date>   <time>: TOKEN EXPIRATION

       If the execution date and time specified for a scheduled dump operation is later than <date time>, then its individual line (as described
       in the following paragraphs) appears below this line to indicate that the current tokens will not be available to it.

       If the issuer of the backup command included the -localauth flag when entering interactive mode, the line instead reads as follows:

	  :  TOKEN NEVER EXPIRES

       The entry for a scheduled dump operation has the following format:

	  Job <job_ID>:  <timestamp>:  dump  <volume_set>  <dump_level>

       where

       <job_ID>
	   Is a job identification number assigned by the Backup System.

       <timestamp>
	   Indicates the date and time the dump operation is to begin, in the format month/date/year hours:minutes (in 24-hour format)

       <volume_set>
	   Indicates the volume set to dump.

       <dump_level>
	   Indicates the dump level at which to perform the dump operation.

       The line for a pending or running operation of any other type has the following format:

	  Job <job_ID>:  <operation>  <status>

       where

       <job_ID>
	   Is a job identification number assigned by the Backup System.

       <operation>
	   Identifies the operation the Tape Coordinator is performing, which is initiated by the indicated command:

	   Dump (dump name)
	       Initiated by the backup dump command. The dump name has the following format:

		   <volume_set_name>.<dump_level_name>

	   Restore
	       Initiated by the backup diskrestore, backup volrestore, or backup volsetrestore command.

	   Labeltape (tape_label)
	       Initiated by the backup labeltapen command. The tape_label is the name specified by the backup labeltape command's -name or -pname
	       argument.

	   Scantape
	       Initiated by the backup scantape command.

	   SaveDb
	       Initiated by the backup savedb command.

	   RestoreDb
	       Initiated by the backup restoredb command.

       <status>
	   Indicates the job's current status in one of the following messages. If no message appears, the job is either still pending or has
	   finished.

	   number Kbytes, volume volume_name
	       For a running dump operation, indicates the number of kilobytes copied to tape or a backup data file so far, and the volume
	       currently being dumped.

	   number Kbytes, restore.volume
	       For a running restore operation, indicates the number of kilobytes copied into AFS from a tape or a backup data file so far.

	   [abort requested]
	       The backup kill command was issued, but the termination signal has yet to reach the Tape Coordinator.

	   [abort sent]
	       The operation is canceled by the backup kill command.  Once the Backup System removes an operation from the queue or stops it from
	       running, it no longer appears at all in the output from the command.

	   [butc contact lost]
	       The backup command interpreter cannot reach the Tape Coordinator. The message can mean either that the Tape Coordinator handling
	       the operation was terminated or failed while the operation was running, or that the connection to the Tape Coordinator timed out.

	   [done]
	       The Tape Coordinator has finished the operation.

	   [drive wait]
	       The operation is waiting for the specified tape drive to become free.

	   [operator wait]
	       The Tape Coordinator is waiting for the backup operator to insert a tape in the drive.

EXAMPLES
       The following example shows that two restore operations and one dump operation are running (presumably on different Tape Coordinators) and
       that the backup command interpreter's tokens expire on 22 April 1999 at 10:45 am:

	  backup> jobs
	  Job 1: Restore, 1306 Kbytes, restore.volume
	  Job 2: Dump (user.sunday1), 34 Kbytes, volume user.pat.backup
	  Job 3: Restore, 2498 Kbytes, restore.volume
		 04/22/1999 10:45: TOKEN EXPIRATION

PRIVILEGE REQUIRED
       None. However, queuing any operation requires privilege, and it is possible to issue this command only within the interactive session in
       which the jobs are queued.

SEE ALSO
       backup(8), backup_interactive(8), backup_kill(8), backup_quit(8)

COPYRIGHT
       IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.

       This documentation is covered by the IBM Public License Version 1.0.  It was converted from HTML to POD by software written by Chas
       Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.

OpenAFS 							    2012-03-26							    BACKUP_JOBS(8)
All times are GMT -4. The time now is 11:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy