Day_of_the_week Post: 302529102

Sponsored Content

Top Forums UNIX for Dummies Questions & Answers Day_of_the_week Post 302529102 by ctsgnb on Wednesday 8th of June 2011 01:37:52 PM

06-08-2011

Registered User

If you run it in control-M, you should be able to run it in the desired time frame, without of taking care of the start time inside the script

You could just add at the beginning of your script :

Code:

[[ -f /tmp/flag/MAINTENANCE ]] && exit 1

And before beginning your maintenance :

Code:

touch /tmp/flag/MAINTENANCE

and remove that flag at the end of your maintenance

Otherwise, schedule it in Control-M and before starting your maintenance, freeze it / unschedule it temporary until you get finished with your maintenance.

I don't know Control-M but i am almost 100% sure such kind of scheduler has some option or other ways for calendar based schedule or time frame windows definition/exclusion, that would make possible to set up such a schedule constraints in one way or another.

I think you should investigate on Control-M possibilities at first since those sort of tools have been design to achieve exactly this kind of task.

Last edited by ctsgnb; 06-08-2011 at 02:56 PM..

ctsgnb

View Public Profile for ctsgnb

Find all posts by ctsgnb

LEARN ABOUT HPUX

u3b

machid(1)						      General Commands Manual							 machid(1)

NAME

       machid: hp9000s200, hp9000s300, hp9000s400, hp9000s500, hp9000s700, hp9000s800, hp-mc680x0, hp-pa, pdp11, u370, u3b, u3b10, u3b2, u3b5, vax
       - provide truth value about processor type

SYNOPSIS

DESCRIPTION

       The following commands return a true value (exit code 0) if the a processor type matches the command name.  Otherwise a false  value  (exit
       code  nonzero)  is returned.  These commands are commonly used within makefiles and shell procedures to improve portability of applications
       (see make(1)).

				       +-----------+-------------------------++--------+--------------------------+
				       |Command    | True for		     ||Command | True for		  |
				       +-----------+-------------------------++--------+--------------------------+
				       |hp9000s200 | Series 200 	     ||pdp11   | PDP-11/45 or PDP-11/70   |
				       |hp9000s300 | Series 300 	     ||u3b     | 3B20 computer		  |
				       |hp9000s400 | Series 400 	     ||u3b2    | 3B2 computer		  |
				       |hp9000s500 | Series 500 	     ||u3b5    | 3B5 computer		  |
				       |hp9000s700 | Series 700 	     ||u3b10   | 3B10 computer		  |
				       |hp9000s800 | Series 800 or 700	     ||u370    | IBM System/370 computer  |
				       |hp-mc680x0 | Series 200, 300, or 400 ||vax     | VAX-11/750 or VAX-11/780 |
				       |hp-pa	   | Series 700 or 800	     ||        |			  |
				       +-----------+-------------------------++--------+--------------------------+
EXAMPLES

       Given a shell script that must behave differently when run on an HP 9000 Series 700 or 800 system, select the correct code  segment  to	be
       executed:

WARNINGS

       always  returns	true on both Series 800 and Series 700 systems.  Therefore, when using this command in scripts to determine hardware type,
       always use both and in the appropriate sequence to ensure correct results (see

       machid(1) will no longer provide support for future machines beyond the Series 800 and Series 700 systems.  Decisions should  be  based	on
       the hardware and software configuration information returned by getconf(1).

SEE ALSO

       getconf(1), make(1), sh(1), test(1), true(1).

																	 machid(1)