- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Running MONITOR IO in a batched command file
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2010 05:38 AM
тАО06-03-2010 05:38 AM
Thanks for taking the time to read my concern.
SCENARIO:
When I run MONITOR IO I see IO stats as they occur. When I am finished, I choose CTRL Z and the session ceases.
If I wanted to grab 5 min intervals every hour for 24 hours - I need to submit this to a batch queue in a .COM file. This is fine.
QUESTION:
How do I handle the (CTRL Z) in the .COM file?
Is there something like e.g. /TIME=5 command that will run MONITOR IO for 5 minutes. At which point I /OUTPUT the screen to a text file. The job exits and I can start again in an hour.
Or am I barking up the wrong tree & there is a better way of capturing this information.
Thanks as always.
Neal Kirby
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2010 06:08 AM
тАО06-03-2010 06:08 AM
Re: Running MONITOR IO in a batched command file
for all kinds of batches like this (and even more: if a procedure might get to hang and needs stopping if not finished before a certain time, especially UNattended ones) I created a little procedure which accepts absolute time OR delta time as a parameter.
This procedure is SPAWNed. It finds out its MASTERPID, and just waits until the specified time. IF the spawned process is still around at the specified time, it notifies SYSTEM MGT, and kills its parent.
If the intended process has done its task, it stops the supprocess. Very little overhead, and quite robust.
Proven VERY effective for unattended BACKUPs; especially before MiniMerge became available, and ca. 1 hour of IO intensive ShadowCopy needed to be finished well before the earliest office workers became active. :-)
( In your case, the starting again should, and can easily) be implemented separately.
hth
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2010 06:08 AM
тАО06-03-2010 06:08 AM
SolutionThe /RECORD stuff can then be played back (using MONITOR and its /INPUT qualifier) at your leisure.
http://h71000.www7.hp.com/doc/83final/6048/6048pro_046.html#bottom_046
Or have a look at installing and using the (free) T4 tools, which uses MONITOR for you, and is set up for capturing and displaying performance data. T4 is discussed here:
http://www.openvms.compaq.com/openvms/products/t4/index.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2010 06:08 AM
тАО06-03-2010 06:08 AM
Re: Running MONITOR IO in a batched command file
try something like:
$ monitor io/end="+0-0:5:00"/summ/nodispl
This will create a MONITOR.SUM file for the 5-minute interval.
There are also some examples on how to use MONITOR in batch in SYS$EXAMPLES:MON*.COM.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2010 06:10 AM
тАО06-03-2010 06:10 AM
Re: Running MONITOR IO in a batched command file
A little tweaking may be needed to suit your needs.
$ ty
_File: sys$examples:submon.com
$ ! Copyright (c) 1987 Digital Equipment Corporation. All rights reserved.
$ !
$ ! SUBMON.COM (Submit MONITOR.COM file)
$ !
$ ! This command file is to be placed in a cluster-accessible
$ ! directory called SYS$MONITOR. At system startup time, for
$ ! each node, it is executed by SYSTARTUP.COM, following logical
$ ! name definitions for the cluster-accessible directories,
$ ! SYS$MONITOR and MON$ARCHIVE.
$ !
$ !
$ ! Submit detached MONITOR process to do continuous recording.
$ !
$ !
$ RUN SYS$SYSTEM:LOGINOUT.EXE -
/UIC=[1,4] -
/INPUT=SYS$MONITOR:MONITOR.COM -
/OUTPUT=SYS$MONITOR:MONITOR.LOG -
/ERROR=SYS$MONITOR:MONITOR.LOG -
/PROCESS_NAME="Monitor" -
/WORKING_SET=100 -
/MAXIMUM_WORKING_SET=100 -
/EXTENT=512 -
/NOSWAPPING
$ !
$ !
$ ! End of SUBMON.COM
$ !
$ dir sys$examples:monsum
Directory SYS$COMMON:[SYSHLP.EXAMPLES]
MONSUM.COM;1
Total of 1 file.
$ ty sys$examples:submon.com
$ ! Copyright (c) 1987 Digital Equipment Corporation. All rights reserved.
$ !
$ ! SUBMON.COM (Submit MONITOR.COM file)
$ !
$ ! This command file is to be placed in a cluster-accessible
$ ! directory called SYS$MONITOR. At system startup time, for
$ ! each node, it is executed by SYSTARTUP.COM, following logical
$ ! name definitions for the cluster-accessible directories,
$ ! SYS$MONITOR and MON$ARCHIVE.
$ !
$ !
$ ! Submit detached MONITOR process to do continuous recording.
$ !
$ !
$ RUN SYS$SYSTEM:LOGINOUT.EXE -
/UIC=[1,4] -
/INPUT=SYS$MONITOR:MONITOR.COM -
/OUTPUT=SYS$MONITOR:MONITOR.LOG -
/ERROR=SYS$MONITOR:MONITOR.LOG -
/PROCESS_NAME="Monitor" -
/WORKING_SET=100 -
/MAXIMUM_WORKING_SET=100 -
/EXTENT=512 -
/NOSWAPPING
$ !
$ !
$ ! End of SUBMON.COM
$ !
$ ty sys$examples:monsum.com
$ ! Copyright (c) 1987 Digital Equipment Corporation. All rights reserved.
$ !
$ ! MONSUM.COM (Generate cluster multi-file summaries)
$ !
$ ! This command file is to be placed in a cluster-accessible directory
$ ! called SYS$MONITOR and executed at the convenience of the cluster
$ ! manager. The file generates both 24-hour and "prime time" cluster
$ ! multi-file summaries and resubmits itself to run each day at midnight.
$ !
$ SET DEF SYS$MONITOR
$ SET NOON
$ !
$ ! Compute file specification for MONSUM.COM and resubmit the file.
$ !
$ FILE = F$ENVIRONMENT("PROCEDURE")
$ FILE = F$PARSE(FILE,,,"DEVICE")+F$PARSE(FILE,,,"DIRECTORY")+F$PARSE(FILE,,,"NAME")
$ SUBMIT 'FILE' /AFTER=TOMORROW /NOPRINT
$ !
$ ! Generate 24-hour cluster summary.
$ !
$ !
$ MONITOR/INPUT=(SYS$MONITOR:*MON*.DAT;*,MON$ARCHIVE:*MON*.DAT;*) -
/NODISPLAY/SUMMARY=MONSUM.SUM -
ALL_CLASSES,DISK/ITEM=ALL,SCS/ITEM=ALL -
/BEGIN="YESTERDAY+0:0:0.00" /END="TODAY+0:0:0.00" /BY_NODE
$ !
$ !
$ ! Mail 24-hour summary file to cluster manager and delete the file from
$ ! SYS$MONITOR.
$ !
$ !
$ !
$ MAIL/SUBJECT="Daily Monitor Cluster-wide Summary" MONSUM.SUM cluster_manager
$ DELETE MONSUM.SUM;*
$ !
$ ! Generate prime-time cluster summary.
$ !
$ !
$ MONITOR/INPUT=(SYS$MONITOR:*MON*.DAT;*,MON$ARCHIVE:*MON*.DAT;*) -
/NODISPLAY/SUMMARY=MONSUM.SUM -
ALL_CLASSES,DISK/ITEM=ALL,SCS/ITEM=ALL -
/BEGIN="YESTERDAY+9:0:0.00" /END="YESTERDAY+18:0:0.00" /BY_NODE
$ !
$ !
$ ! Mail prime-time summary file to cluster manager and delete the file
$ ! from SYS$MONITOR.
$ !
$ !
$ MAIL/SUBJECT="Prime-Time Monitor Cluster-wide Summary" MONSUM.SUM cluster_manager
$ DELETE MONSUM.SUM;*
$ !
$ ! End of MONSUM.COM
$ !
$
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2010 06:14 AM
тАО06-03-2010 06:14 AM
Re: Running MONITOR IO in a batched command file
>> How do I handle the (CTRL Z) in the .COM file?
You can tell Monitor to collect data only for some period of time.
You can specify the ending time using the /ENDING qualifier.
If you dont specify the /ENDING then MONITOR will continue its work
until you terminate it using Crtl/C or Crtl/Z.
Check the following link -
http://h71000.www7.hp.com/doc/83final/6048/6048pro_046.html
-> Refer help for /ENDING
You need to make use of the /ENDING in your command procedure.
In the Command procedure, if you want monitor to run for 5 mins only then
* Take Current Time
* End time = Current time + 5 mins
* MONITOR *** /ENDING=End time
Hope that helps.
Regards,
Murali
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2010 06:14 AM
тАО06-03-2010 06:14 AM
Re: Running MONITOR IO in a batched command file
http://en.wikipedia.org/wiki/Launchd
I've previously groused about the lack of capable job scheduling being a problem, of course.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2010 08:48 AM
тАО06-03-2010 08:48 AM
Re: Running MONITOR IO in a batched command file
$ monitor/input=
Use the /view option to speed display rate.
And yes, you can read this file while monitor is writing, use /begin and /end to narrow your window.
I used to run monitor in batch, with daily summaries of "prime time" emailed to me before T4 became available. You have the option of creating 1 large file over your 24 hour period and extracting reports. Anything you do manually will only duplicate the functionality of T4 and TLViz.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2010 12:37 PM
тАО06-03-2010 12:37 PM
Re: Running MONITOR IO in a batched command file
Generally, I would recommend gathering the full spectrum of performance data (as is done by T4 using MONITOR/RECORD as a foundation.
Playing the data back later, one can do choose to look at as broad or as limited set of data as one pleases. More importantly, if one is trying to understand peaks of IO activity, being able to drill down into other issues is often clarifying (particularly when using tools such as the companion to T4, which allow plotting of data over time).
My general rule: Gather broad data, then do narrow or broad analysis as appropriate. With today's storage capacities, the difference in volume is not great. I also note that attention should be paid to ensure adequate RMS extend and buffering factors for the MONITOR output file. To be able to remove the activity generated by MONITOR itself, it also helps to have a separate disk volume (or an otherwise low activity volume) to store the data.
As Hoff noted, the underlying parameters are /BEGIN and /END, together with /RECORD.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-15-2011 03:54 AM
тАО02-15-2011 03:54 AM
Re: Running MONITOR IO in a batched command file
http://h71000.www7.hp.com/openvms/products/t4/