Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Getting the date and time
- Thread starter bcbm
- Start date
Is the script going to run constantly during the day, or does it just need to check on startup?
Probably the easiest way to do this is to use the ltimemisc command to have the script determine what day it is and then use ltimeints command with the $LTIME system variable to get the current minute, hour, etc.
The waituntil command might be useful in this situation as well. You can use it to pause your script (instead of closing it outright) until the specified time and day.
aspect@aspectscripting.com
Probably the easiest way to do this is to use the ltimemisc command to have the script determine what day it is and then use ltimeints command with the $LTIME system variable to get the current minute, hour, etc.
The waituntil command might be useful in this situation as well. You can use it to pause your script (instead of closing it outright) until the specified time and day.
aspect@aspectscripting.com
- Thread starter
- #3
The script will be running 24 hours a day. I did figure out from looking at your site how to get the script to check if it is a week day, just need to figure out about the time issue now.
Could I use the ltimestrs $LTIME DateString TimeString and do an if statement for the TimeString ?
Also could you point me to information on how to write and call parts of the script as procedures, right now everything is all grouped togeter and I think it would work better if I did calls of procedure.
Could I use the ltimestrs $LTIME DateString TimeString and do an if statement for the TimeString ?
Also could you point me to information on how to write and call parts of the script as procedures, right now everything is all grouped togeter and I think it would work better if I did calls of procedure.
In that case, I think using ltimeints like I mentioned above would be the easiest way to do this. The script would run the command to break the time value into its component parts (the help file has a sample script that shows how to do this) and you could check the value of the integer variable holding the hours value. If it is less than 7 or greater than 18, then the script should pause until the proper time is reached. I think this would be easier than getting the value from ltimestrs in a string format and trying to do a compare in that manner.
The help file probably explains it better than I can here (check out the Procedures and Functions topic in the help file for starters) but here are the basics. The format for a procedure is:
proc procname
code...
endproc
where procname is the name of the procedure. To call this procedure, you would use this syntax:
procname()
When procname was done executing, it would return to where it was called from.
Procedures are not able to access variables from other procedures or the main procedure directly unless you either declare the variable as a global (meaning it is declared above proc main in your script) or you pass its value to the procedure. Again, since the help file explains it better than I can, check out the discussion of the param command in the help file.
aspect@aspectscripting.com
The help file probably explains it better than I can here (check out the Procedures and Functions topic in the help file for starters) but here are the basics. The format for a procedure is:
proc procname
code...
endproc
where procname is the name of the procedure. To call this procedure, you would use this syntax:
procname()
When procname was done executing, it would return to where it was called from.
Procedures are not able to access variables from other procedures or the main procedure directly unless you either declare the variable as a global (meaning it is declared above proc main in your script) or you pass its value to the procedure. Again, since the help file explains it better than I can, check out the discussion of the param command in the help file.
aspect@aspectscripting.com
- Thread starter
- #5
teletubby5e
Technical User
sounds like quite a bit of work ... one fun thing i liked adding to my scripts, right before i compiled them into a wax file for distribution was this ...
a shelf life so to speak ...
ltimeints $LTIME iYear iMonth iDay iHour iMin iSec
if iYear > 2005
halt
endif
useful in case of downsizing, but on a more serious note, you can make it where your script will only be able to be run during the maintenance hours ...
for example
if iHour < 0700
halt
endif
if iHour > 1800
halt
endif
a shelf life so to speak ...
ltimeints $LTIME iYear iMonth iDay iHour iMin iSec
if iYear > 2005
halt
endif
useful in case of downsizing, but on a more serious note, you can make it where your script will only be able to be run during the maintenance hours ...
for example
if iHour < 0700
halt
endif
if iHour > 1800
halt
endif
- Status
