Autosys Job Running every 5th Day of Month

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

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

3. UNIX for Dummies Questions & Answers

Running Script via Crontab on 2nd Working day each month

Hello Guys, I have a questions regarding running a shell script every second working day each month. I have no clue how solve this problem :wall:. Important is that it has to be the second working (Mo-Fr). Example: If 1st and 2nd Days of month are Sat and Sun the script must run on 4th day...

4. Shell Programming and Scripting

Need help in running script on last day of month

Hello Experts/Guru, I need a help in running the script on every month last day.... PS: due to some constrain I can't schedule in crontab Requirement: On Jan 31st i want to run some script, similarly on Feb 28th, March 31st, April 30th......till Dec 31st. Please help me by providing...

5. Shell Programming and Scripting

Autosys job scheduling on specific day

Below is the requirement i am trying to do using auto sysjob. I need to create a JOB or script which will do the below things for me I have a box and there corresponding jobs as below BOX_1 JOB_1 JOB_2 BOX_2--- SU(JOB_2), this will run only on completion (Success) of JOB_2 ...

6. Windows & DOS: Issues & Discussions

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

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

8. Solaris

report of autosys job in RUNNING state

9. Programming

report of autosys job in RUNNING state

10. Shell Programming and Scripting

report of autosys job in RUNNING state

LEARN ABOUT DEBIAN

mhc

mhc(5)								File Formats Manual							    mhc(5)

NAME

       mhc - Message Harmonized Calendaring system

DESCRIPTION

       This  manual  page  documents  briefly the mhc file format.  This manual page was written for the Debian GNU/Linux distribution because the
       original program does not have a manual page.

FIELDS

       Mhc file format is based on STD11/RFC822: Standard for the format of ARPA Internet text messages.  In mhc file, the following extra  header
       fields are used.

       X-SC-Day:
	      Date of event in format yyyymmdd.  You can specify multiple date with space separated like:

		 X-SC-Day: 19990409 19990413

	      which means April 9th 1999 and April 13th 1999.

       X-SC-Time:
	      Time of event in format hh:mm-hh:mm or hh:mm.  For event which has no meanings about time, you can leave it empty in this field.

       X-SC-Duration:
	      Period  of event in yyyymmdd-yyyymmdd.  You can omit start date or end date, like "19991121-".  X-SC-Duration: is used only to limit
	      date specified by X-SC-Day: or X-SC-Cond, so you can't describe event date only by X-SC-Duration:.  If X-SC-Duration: is	empty,	it
	      means no limit.

       X-SC-Cond:
	      Condition of event date by using following keyword.

		 00-31 Day of month.

		 1st 2nd 3rd 4th 5th Last Week in month.

		 Sun Mon ... Sat Day of week.

		 Jan Feb ... Dec Month

	      Examples,

		 X-SC-Cond: Tue Fri
			Every Tuesday and Friday.

		 X-SC-Cond: 31 Aug
			Every August 31th.

		 X-SC-Cond: 1st 3rd Fri
			Every 1st and 3rd Friday.

		 X-SC-Cond: Fri
		 X-SC-Day: !19990409
			Every Friday, but except April 9th 1999.

		 X-SC-Cond: Fri 13
			Every 13th and Every Friday, not 13th Friday.

       X-SC-Alarm:
	      Hint  for alarm of event.  Currently, mhc.el doesn't alaram, but gemcal will pop-up alarm window.  It will be useful if you transfer
	      this event to PalmOS.  In X-SC-Alarm:, you can specify the number (1 to 99) with suffix such as minute, hour or day.  For example,

		 X-SC-Alarm: 10 minutes
			Alarm 10 minutes before event.

		 X-SC-Alarm: 3 hour
			Alarm 3 hours before event.

		 X-SC-Alarm: 3 day
			Alarm 3 day before event.

       X-SC-Subject:
	      Subject of event. unstructured?

       X-SC-Location:
	      Location of event. unstructured?

       X-SC-Category
	      Category of event.  Any keyword, space separeated.  Case ignored.

       X-SC-Recoard-Id:
	      Internal use only.

SEE ALSO

       adb2mhc(1) gemcal(1), mhc-sync(1), mhc2palm(1), palm2mhc(1), today(1).

AUTHOR

       This program was written by Yoshinari Nomura <nom@quickhack.net> and this manual page was written by  Fumitoshi	UKAI  <ukai@debian.or.jp>,
       for the Debian GNU/Linux system (but may be used by others).

								    23 Jun 2000 							    mhc(5)

UNIX for Advanced & Expert Users