[Sponsored by PointSecure - The leading provider of security and auditing solutions for OpenVMS]
Part 2 of a 4 series: Marty interviews Nina Buik about Endeavour, the code name used for the consolidation of the primary HP user groups into a single larger and stronger organization. Combined user groups, more customers...more influence with HP? Download and listen to part 1 of this 4 part series.
labadie, Wednesday April 02 2008 @ 04:37AM EST views: 165
This procedure sorts the bg devices based on the Bytes sent, Bytes received, I/O sent, I/O received.
I have already submitted it, but realised that there was a typo due to a bad copy and paste.
Keith Cayemberg, Sunday November 25 2007 @ 11:46PM EST views: 615
This "DCL Program" (1867 lines) provides powerful process scanning capabilities giving detailed JPI process context variable information about any processes on the same node or cluster. The processes to be displayed can be specified using multiple selection criteria. A VT220 compatible terminal is assumed. The procedure adapts the number of columns displayed automatically when the screen is in 80 column or 132 column mode. Single pass and continuous display modes are supported. The continuous display mode can be exited only using Control-C. The continuous mode will also change the page length of the screen automatically when needed, if your terminal emulation supports the VT function correctly. DECwindow's DECterm supports this functionality the best. For a more complete HELP description and many more capabilities, start the procedure with a question mark "?" as the first command line parameter.
Some of the useful things you can do with this procedure:
find all processes running a specific image, or any image within a specific directory tree.
find all processes with a specific quota exhausted to a specified percentage.
count the number of times processes with a specific set of attributes exist during a period of time.
call this procedure from your own, and use the global variables created that give the identifying attributes of the first or last process that PROCESS_SCAN found.
watch the processes of another cluster node and their changing attributes as that node boots, BEFORE the System Manager can log-on to the booting node, and BEFORE TCP/IP or DECnet has been loaded on that node.
Happy 30th OpenVMS Anniversary to the OpenVMS Community!
Aaron, Tuesday October 02 2007 @ 11:19AM EDT views: 752
This is a short routine that I use to keep file versions in check for those files that like to rapidly increment version numbers, preventing sudden application death from version ;32767. This will take any sequence of file version numbers and reset them to start from ;1 while maintaining the order and original creation dates of the files. The use of Rename to reset the versions allows the file to be open for write by another program without interfering with this reset (or for this reset to interfere with an app that has a file open for write).
This routine should be customized for the user's site by adding a separate CALL command for each file that is to be reset, following the example given in the procedure. Add as many CALL ResetFiles as you need. You can use an automated scheduling program (e.g., I use Kronos), submit the job repetitively, or run it by hand any time you need.
Jess Goodman, Friday September 21 2007 @ 02:53PM EDT views: 993
This retrieves all specifications for a set of batch job(s) using F$GETQUI and formats the data into SUBMIT command(s). Use $ @DISPLAY_JOBS ? for full documentation.
Catalin Dandes, Friday September 14 2007 @ 08:50AM EDT views: 639
Checking over quotas on all disks; if quota not enabled, disk is skipped. Requires SYSPRV to run sysman.
Eric Onspaugh, Friday September 07 2007 @ 02:04PM EDT views: 674
Search a device or directory structure and find ACE entries by name and optionally delete them. This can be particularly useful for getting ridof those orphaned identifiers that show up as %x*******
Jose Baars, Tuesday July 31 2007 @ 02:36PM EDT views: 826
On the freeware cd's there was a utility called fixque ( I think by Keith Parris) that dumped the queue database, and parsed out the output of show queue/full etc. Problem was that it couldn't handle the large entrynumbers either :-). So I wrote a dumpqdb.com based on f$getqui
that produced an output file with all the commands necessary to create a new queue database.
Couple of things missing : characteristics, we don't use it. ACL's on queue, ditto. /new switch to the start/que/manager command. Probably more, there are a lot of things that we don't use, but are possible.
To use it, create the output file by @dumqdb/out=w.w, then carefully compare w.w to your queues and entries, edit in omissions or additions, add the /new switch to the start/que/manager command.
Then stop the queumanager, backup, and then rename or delete all queue database files, as they probably have grown beyond any reasonable size and run w.w. You should (almost, right in three tries is my sad motto) be back to normal.
This was all written as an emergency procedure, and it did work 99% in our situation, but this might be different in yours.