INFO-VAX Wed, 26 Sep 2007 Volume 2007 : Issue 526 Contents: Re: Article of Interest. Re: ba356 box Re: ba356 box Soymail not working with WASD Re: System Service to perform F$PARSE functions Re: System Service to perform F$PARSE functions Re: System Service to perform F$PARSE functions Re: System Service to perform F$PARSE functions Web-based VMS Que Monitor for Deathrow Re: Web-based VMS Que Monitor for Deathrow Re: Web-based VMS Que Monitor for Deathrow Re: Web-based VMS Que Monitor for Deathrow Re: Web-based VMS Que Monitor for Deathrow Re: Web-based VMS Que Monitor for Deathrow Re: Web-based VMS Que Monitor for Deathrow Re: Web-based VMS Que Monitor for Deathrow Re: Web-based VMS Que Monitor for Deathrow Re: Web-based VMS Que Monitor for Deathrow wierd backup behavior Re: wierd backup behavior ---------------------------------------------------------------------- Date: Wed, 26 Sep 2007 01:02:21 -0700 From: IanMiller Subject: Re: Article of Interest. Message-ID: <1190793741.844624.318690@57g2000hsv.googlegroups.com> On Sep 26, 4:02 am, "Main, Kerry" wrote: > Perhaps. Its also possible they did not install all the well publicised security patches > for the platforms in question and the bad guys simply attacked known holes. > That would also count as operational incompetence. ------------------------------ Date: Wed, 26 Sep 2007 09:31:08 -0600 From: Keith Parris Subject: Re: ba356 box Message-ID: rexdale1050@yahoo.ca wrote: > I am running OpenVMS 7.3 on an Alphaserver DS10 using a DS-BA356-CC > RAID tower. Can I add an extra DS-BA356 to take over if the original > DS-BA356 fails? > What hardware / software is needed? One method would be to add storage of some type (another DS-BA356 should be fine, or anything where the disks are at least as large in size as the ones you already have), and use host-based Volume Shadowing software to do host-based mirroring (RAID-1) with the existing disks in combination with the new storage. You may need another SCSI interface card in the DS10 to connect another SCSI bus, so you have separate busses to protect against a SCSI bus failure. ------------------------------ Date: Wed, 26 Sep 2007 13:31:02 -0400 From: "Carl Friedberg" Subject: Re: ba356 box Message-ID: <890539d90709261031t5843faa9k3b9283cce35963fb@mail.gmail.com> It's been awhile, but IIRC, the BA356 is capable of operating in a split bus mode, so that there are two independent SCSI buses. Assuming two power supplies, that allows you to connect to two channels on a SWXCR. This only protects you against disk failure (assuming you use the RAID 1 or RAID 5 capability of the SWXCR. Warning: this is VERY old technology, and doing many RAID tasks requires that you shut down the AlphaServer, boot it in graphics console mode, run the firmware SWXCR utility, and wait, wait, wait while something rebuilds. Largest supported disk size is effectively 18GB. I believe the BA356 dates back to the early 1990's. I'm pretty sure I had a SWXCR in an AlphaServer 2100. On 9/26/07, Keith Parris wrote: > rexdale1050@yahoo.ca wrote: > > I am running OpenVMS 7.3 on an Alphaserver DS10 using a DS-BA356-CC > > RAID tower. Can I add an extra DS-BA356 to take over if the original > > DS-BA356 fails? > > What hardware / software is needed? > > One method would be to add storage of some type (another DS-BA356 should > be fine, or anything where the disks are at least as large in size as > the ones you already have), and use host-based Volume Shadowing software > to do host-based mirroring (RAID-1) with the existing disks in > combination with the new storage. > > You may need another SCSI interface card in the DS10 to connect another > SCSI bus, so you have separate busses to protect against a SCSI bus failure. > ------------------------------ Date: Wed, 26 Sep 2007 10:40:20 -0700 From: ultradwc@gmail.com Subject: Soymail not working with WASD Message-ID: <1190828420.562306.230040@y42g2000hsy.googlegroups.com> followed Alans book ... SSL webserver is running and serving static pages, but the moment the /soymail switch is added to the URL, only the soymail page under construction comes up ... clicking on /ht_root/src/soymail/ works but /cgi-bin/soymail/~ does not, gets err 404 HTTPD$AUTH.CONF contains ["Default"=REALM] /cgi-bin/soymail/~* r+w HTTPD$MAP.CONF contains pass /soymail/-/* /ht_root/src/soymail/* set /cgi-bin/soymail/~* map=once the WASD server startup command is $ DEF/SYS HTTPD$SERVER "SYSUAF=SSL" $ @DSA0:[HT_ROOT.LOCAL]STARTUP WASD_SSL=1 soymail.conf contains [private-access] username/*/USERNAME can the owner of soymail or anyone else familiar with WASD give some insight as to why following the book and docs failed and why a site under work page shows instead of authentication box then mail? PS I can redirect purveyor to run the WASD built soymail .exe and it works, so the compile is fine ... ------------------------------ Date: Wed, 26 Sep 2007 02:38:53 -0400 From: JF Mezei Subject: Re: System Service to perform F$PARSE functions Message-ID: davidpryce123@yahoo.com.au wrote: > Is there a system service that I can call to perform operations such > as the lexical f$parse. The RMS manual is your best friend here. Essentially, you need: (not sure if buffers are large enough for ODS5). in the code below "libname" contains the filename to parse. #include (and a bunch of other includes) struct FAB myfab ; struct NAM mynam ; char myesa[256]; char mybuffer[256]; char *ptr1 ; int status, x ; myfab = cc$rms_fab ; /* populate with default values */ mynam = cc$rms_nam ; myfab.fab$l_fna = libname ; myfab.fab$b_fns = strlen(libname); myfab.fab$l_nam = &mynam; mynam.nam$b_nop = mynam.nam$b_nop | NAM$V_SYNCHK ; mynam.nam$l_esa = myesa ; mynam.nam$b_ess = 255; status = SYS$PARSE(&myfab,0,0); sprintf(uid_file_name,"%.*s%.*s%.*s% %.*s", mynam.nam$b_dev, mynam.nam$l_dev, mynam.nam$b_dir, mynam.nam$l_dir, mynam.nam$b_name, mynam.nam$l_name, mynam.nam$b_type, mynam.nam$l_type, mynam.nam$b_ver, mynam.nam$l_ver); the "$b" is a byte containing the length of the string, the "$l" is a pointer to the location of first character of the string. Essentially, SYS$PARSE will expand the file specification into a single large buffer ("myesa") and then populate the $l_dev etc with pointers to charcaters in that string. > char *nam$l_node; /* Nodespec address */ > char *nam$l_dev; /* Device address */ > char *nam$l_dir; /* Directory address */ > char *nam$l_name; /* Filename address */ > char *nam$l_type; /* Filetype address */ > char *nam$l_ver; /* Version number address */ (and there are the equivalent lengths with the $b_ versions) (NoteL: you need to CC/UNSIGNED to ensure that all "strings" are handled so that they can contained the full ISO character set. For a very silly reason, ANSI dicatted that signed chars see their 8th bit snipped off so you may see ('é' = 'i') being true. With ODS5, you may enter accented characters. ------------------------------ Date: Wed, 26 Sep 2007 07:29:45 -0500 From: "Craig A. Berry" Subject: Re: System Service to perform F$PARSE functions Message-ID: In article , "Martin Vorlaender" wrote: > wrote: > > Is there a system service that I can call to perform operations such > > as the lexical f$parse. > > > > I have VMS file names and I want to extract different components such > > as nodename, device, directory, file name, file type and version. I > > would like to do it properly instead or indexing into strings etc > > > > Does anyone have an example in C or Pascal to perform this? > > The basis is probably RMS' $PARSE service[1], but a solution that is > easier to handle is $FILESCAN [2]. Jim Duff has an example using $FILESCAN: http://www.eight-cubed.com/examples/framework.php?file=sys_filescan.c There is also one in the guts of Perl. Look for a routine called vms_split_path here: http://public.activestate.com/cgi-bin/perlbrowse/f/vms/vms.c -- Posted via a free Usenet account from http://www.teranews.com ------------------------------ Date: 26 Sep 2007 07:35:28 -0500 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: System Service to perform F$PARSE functions Message-ID: In article <1190781227.357351.190810@n39g2000hsh.googlegroups.com>, davidpryce123@yahoo.com.au writes: > Hi Group, > > Is there a system service that I can call to perform operations such > as the lexical f$parse. > Lot of folks will point you to the RMS service sys$parse. Before you decide to do that look at the system service sys$filescan. I find the latter much more readily useable most of the time. Here's an example of parsing off just the name. #include #include #include #include #include #include #include #define OK(x) $VMS_STATUS_SUCCESS(x) char *nameonly(char *file) { struct item_list_2 { unsigned short length; unsigned short code; char *address; }; struct dsc$descriptor file_desc = {0, 0, 0, 0}; int status, size; static char *np = NULL; struct { struct item_list_2 item; int mbz; } list; if (np != NULL) free(np); file_desc.dsc$a_pointer = file; file_desc.dsc$w_length = strlen(file); list.item.code = FSCN$_NAME; list.mbz = 0; status = sys$filescan(&file_desc,&list,0); if (!OK(status)) exit(status); size = list.item.length; np = (char *) malloc(size + 1); strncpy(np,list.item.address,size); np[size] = 0; return np; } ------------------------------ Date: 26 Sep 2007 07:38:09 -0500 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: System Service to perform F$PARSE functions Message-ID: <+gLE0qOZyN7k@eisner.encompasserve.org> In article , JF Mezei writes: > davidpryce123@yahoo.com.au wrote: >> Is there a system service that I can call to perform operations such >> as the lexical f$parse. > > The RMS manual is your best friend here. > > Essentially, you need: (not sure if buffers are large enough for ODS5). For ODS-5 you need NAML instead of NAM. For ODS-2 you should use NAM$C_MAXRSS and for ODS-5 NAML$C_MAXRSS to size the local buffers. And of course, add one to store C's null terminator. ------------------------------ Date: Wed, 26 Sep 2007 18:23:24 +0800 From: "Richard Maher" Subject: Web-based VMS Que Monitor for Deathrow Message-ID: Hi, If any of you Inmates out there would like to monitor the state of your batch jobs on the Deathrow cluster via a Web Browser interface, then please click on the following web page: - http://manson.vistech.net/t3$examples/demo_client_web.html In order to be able to use this Queue Manager example successfully you will need:- 1) Javascript enabled 2) Java Applets enabled 3) Can't be behind a Firewall that forbids all unknown outgoing connections (otherwise open-up 5255) 4) Must be running SUN's JRE 1.4.2_13 or later (1.6 is advised) http://java.sun.com/javase/downloads/index.jsp 5) Must be running Internet Explorer (6 or later) or Firefox (Haven't tested other browsers) If need be, turn on the Java Console (Settings/Controle pannel/Java Plug-in/Console on) and, if using Firefox, the Error Console. (You just gotta love FireBug!!!) All things being equal you should then be prompted (via Java modal dialogue box) for:- Username: TIER3_DEMO Password: QUEUE If things are still going well, enter an asterix "*" for the Queue Name and you will see the List-of-values appear with all the available queues on the Deathrow cluster. Now click on the "Get Job Info" button and we're away! If not the Java Console should give you a message. If you're slightly curious as to exactly how easily this full-function, high-quality, high-performance GUI has gained access to the VMS servers that we all know and love, then all the source code is available at http://manson.vistech.net/t3$examples/ (Can also help to track down any problems) If you'd like to use this application on an ongoing basis from your normal Inmate Username/Password then please contact me and I will see if it's possible. Cheers Richard Maher Here's some of the functionality-catwalk highlights from the example: - 1) Full, one-time, context-specific, VMS User Authentication. No Cookies, Session IDs, Password Caching or generic Work-Station or Browser credentials! When you load the demo_client_web.html page into your browser, a Java Applet is automatically activated that prompts the user for their VMS Username and Password via a modal dialogue box. If authorization fails, the "Access Denied" page will be displayed and VMS Intrusion Detection (in accordance with the policy set out by your System Manager) will be enforced, and Login-Failures is incremented in SYSUAF. Alternatively, if authorization is successful (and you left the "Display Logon Confirmation" box ticked) then a Welcome dialog box will be displayed detailing last login times and the number of unsuccessful login attempts (if any). Login-Failures is now set to zero and last non-interactive login time is set to the current time. If you refresh this page, or move to a different page, then the server connection is broken and you must be re-authorised before continuing to access the Demo Queue Manager application. 2) A Hot-Abort button! After you have pressed the "Get Job Info" button you'll notice that the "Abort Request" button becomes active and turns red. (Actually you probably won't notice 'cos this query completes too quickly :-) You can edit the DEMO_UARS.COB code and change the value of the DEBUG_DELAY field if you want to see your 3GL Interrupt routine in action.) In this case the cancel-flag I've set in the AST routine is picked up in the mainline code, resulting in the graceful termination of the loop that controls "next queue" (or "next row") retrieval. Also, if you look at the getResponse() function in query_lookup.html, you will see how the chan.setTimeout() method has been deployed to provide an erstwhile "blocking" socket Read with the ability to surrender the event-thread for things like processing the Abort button and ticking over the clock. (all of this, and much more, "infrastructure-code" is already there and doesn't have to be re-invented) 3) Predictive text on the Queue Name field so that all matching VMS queues are retrieved on-demand as the user types. As is now common-place with many websites, a drop down select list of matching options is automatically retrieved from the server and made available for the user to select from. 4) Result-set drill-down. Many database queries return a result-set of rows for the user to scan through and possibly drill-down into for more detail. I've provided a reasonably generic example of this, where all matching Job Entries have been populated into a dynamic HTML select list. Once again the user was able to see the select-list grow, the scroll-bar diminish, and "Jobs Found" field tick over in real-time, whilst continually being empowered (by the Abort button) to curtail the results at any time! If you click on an entry in the Select List then the changes and the entry_details.html page appears. See the parent.entry_details.getReady() call in queue_lookup.html to see how the handover to the new frame takes place. (Also see goBack() in entry_details.html to see how simply that operation is reversed.) The user is now free to move forward, back, first, last, refresh, and delete queue entries, or return to the previous frame. (Thanks to the deployment of the VMS Persona functionality, the user is only permitted to see those queue entries that the Username they signed in under is permitted to see. They can also *only* delete those entries that this username is allowed to delete.) 5) Floating
s. You'll see that any queue names are highlighted in bold and italics; if you mouseover any of these fields when they are not blank then the current status information for that queue will be retrieved from the server and displayed in a quasi-popup DIV. 6) Local Result-Set Sort. If you click on the "header" or "first" row in the Select List of queues, you will get a popup prompting you for a sort key. If you select one, the contents of the Select List are sorted in the chosen order. (Try enter "*" for the Queue Name and then clicking "Get Job Info" to get some data worth sorting) ------------------------------ Date: Wed, 26 Sep 2007 11:14:11 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: Web-based VMS Que Monitor for Deathrow Message-ID: <7arKi.10$fT2.4@newsfe12.lga> In article , "Richard Maher" writes: > > >Hi, > >If any of you Inmates out there would like to monitor the state of your >batch jobs on the Deathrow cluster via a Web Browser interface, then please >click on the following web page: - > >http://manson.vistech.net/t3$examples/demo_client_web.html > >In order to be able to use this Queue Manager example successfully you will >need:- > >1) Javascript enabled >2) Java Applets enabled >3) Can't be behind a Firewall that forbids all unknown outgoing connections >(otherwise open-up 5255) >4) Must be running SUN's JRE 1.4.2_13 or later (1.6 is advised) >http://java.sun.com/javase/downloads/index.jsp >5) Must be running Internet Explorer (6 or later) or Firefox (Haven't tested >other browsers) > >If need be, turn on the Java Console (Settings/Controle pannel/Java >Plug-in/Console on) and, if using Firefox, the Error Console. (You just >gotta love FireBug!!!) > >All things being equal you should then be prompted (via Java modal dialogue >box) for:- > >Username: TIER3_DEMO >Password: QUEUE > >If things are still going well, enter an asterix "*" for the Queue Name and >you will see the List-of-values appear with all the available queues on the >Deathrow cluster. Now click on the "Get Job Info" button and we're away! FYI RIchard, Safari aborts after entering the Username and Password. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM "Well my son, life is like a beanstalk, isn't it?" http://tmesis.com/drat.html ------------------------------ Date: Wed, 26 Sep 2007 07:42:21 -0400 From: Robert Deininger Subject: Re: Web-based VMS Que Monitor for Deathrow Message-ID: In article , "Richard Maher" wrote: > Hi, > > If any of you Inmates out there would like to monitor the state of your > batch jobs on the Deathrow cluster via a Web Browser interface, then please > click on the following web page: - > > http://manson.vistech.net/t3$examples/demo_client_web.html > > In order to be able to use this Queue Manager example successfully you will > need:- > > 1) Javascript enabled > 2) Java Applets enabled > 3) Can't be behind a Firewall that forbids all unknown outgoing connections > (otherwise open-up 5255) > 4) Must be running SUN's JRE 1.4.2_13 or later (1.6 is advised) > http://java.sun.com/javase/downloads/index.jsp > 5) Must be running Internet Explorer (6 or later) or Firefox (Haven't tested > other browsers) Wow! That's the most annoying web page I've seen in many months. It doesn't work at all in the Safari browser. The logon dialog never appears. Even with pop-ups enabled. In the Omniweb browser, it (sort of) works. The first thing it does is resize the browser window to full screen. That's REALLY annoying. It's MY screen, dammit, and I'll thank you to use no more of it than I specify. Then it pops up the login window (at a normal size, thank you). The normal window controls are disabled. (2 of them are grayed out; the close button looks normal but doesn't work.) The two buttons in the window (OK and Cancel) don't have normal keyboard controls. I suppose that's just the way Java works. The logon confirmation box is ok, but again I can't activate the OK button from the keyboard. Even though it is the only control in the box, and it appears to have focus because it's highlighted, neither the Return nor the Enter key will click it. (Ah, I discovered on my 7th trip through the logon sequence that I must use the space bar to activate your controls.) Alas, I couldn't test the rest of the demo. It crashes the browser every time. Usually just after the logon confirmation; once it drew the main page and then crashed. Nice concept (really). But icky implementation. -- Robert ------------------------------ Date: Wed, 26 Sep 2007 07:55:06 -0400 From: Robert Deininger Subject: Re: Web-based VMS Que Monitor for Deathrow Message-ID: In article <7arKi.10$fT2.4@newsfe12.lga>, VAXman- @SendSpamHere.ORG wrote: > In article , "Richard Maher" > writes: > > > > > >Hi, > > > >If any of you Inmates out there would like to monitor the state of your > >batch jobs on the Deathrow cluster via a Web Browser interface, then please > >click on the following web page: - > > > >http://manson.vistech.net/t3$examples/demo_client_web.html > > > >In order to be able to use this Queue Manager example successfully you will > >need:- > > > >1) Javascript enabled > >2) Java Applets enabled > >3) Can't be behind a Firewall that forbids all unknown outgoing connections > >(otherwise open-up 5255) > >4) Must be running SUN's JRE 1.4.2_13 or later (1.6 is advised) > >http://java.sun.com/javase/downloads/index.jsp > >5) Must be running Internet Explorer (6 or later) or Firefox (Haven't tested > >other browsers) > > > >If need be, turn on the Java Console (Settings/Controle pannel/Java > >Plug-in/Console on) and, if using Firefox, the Error Console. (You just > >gotta love FireBug!!!) > > > >All things being equal you should then be prompted (via Java modal dialogue > >box) for:- > > > >Username: TIER3_DEMO > >Password: QUEUE > > > >If things are still going well, enter an asterix "*" for the Queue Name and > >you will see the List-of-values appear with all the available queues on the > >Deathrow cluster. Now click on the "Get Job Info" button and we're away! > > FYI RIchard, > > Safari aborts after entering the Username and Password. Congrats! What incantation did you use? I couldn't even get the login box using Safari. Am I brave enough to download yet another browser (Firefox) and try this again? $ SHOW QUEUE works pretty well for me. I guess I'll leave the Mickey-Clicky stuff to the kids. ------------------------------ Date: 26 Sep 2007 07:47:16 -0500 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: Web-based VMS Que Monitor for Deathrow Message-ID: In article , "Richard Maher" writes: > Hi, > > If any of you Inmates out there would like to monitor the state of your > batch jobs on the Deathrow cluster via a Web Browser interface, then please > click on the following web page: - > > http://manson.vistech.net/t3$examples/demo_client_web.html > Interesting. Seems the demo account has visisbility into everybody's job, but the product promises visibility into "authorized" jobs. Is the demo account granted WORLD or is the web server providing the necessary privilege? ------------------------------ Date: 26 Sep 2007 07:48:42 -0500 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: Web-based VMS Que Monitor for Deathrow Message-ID: In article , Robert Deininger writes: > > Am I brave enough to download yet another browser (Firefox) and try this > again? I only tested it with Firefox. No crashes, but I noticed the resizing, too. ------------------------------ Date: Wed, 26 Sep 2007 14:13:12 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: Web-based VMS Que Monitor for Deathrow Message-ID: In article , Robert Deininger writes: > > >In article <7arKi.10$fT2.4@newsfe12.lga>, VAXman- @SendSpamHere.ORG >wrote: > >> In article , "Richard Maher" >> writes: >> > >> > >> >Hi, >> > >> >If any of you Inmates out there would like to monitor the state of your >> >batch jobs on the Deathrow cluster via a Web Browser interface, then please >> >click on the following web page: - >> > >> >http://manson.vistech.net/t3$examples/demo_client_web.html >> > >> >In order to be able to use this Queue Manager example successfully you will >> >need:- >> > >> >1) Javascript enabled >> >2) Java Applets enabled >> >3) Can't be behind a Firewall that forbids all unknown outgoing connections >> >(otherwise open-up 5255) >> >4) Must be running SUN's JRE 1.4.2_13 or later (1.6 is advised) >> >http://java.sun.com/javase/downloads/index.jsp >> >5) Must be running Internet Explorer (6 or later) or Firefox (Haven't tested >> >other browsers) >> > >> >If need be, turn on the Java Console (Settings/Controle pannel/Java >> >Plug-in/Console on) and, if using Firefox, the Error Console. (You just >> >gotta love FireBug!!!) >> > >> >All things being equal you should then be prompted (via Java modal dialogue >> >box) for:- >> > >> >Username: TIER3_DEMO >> >Password: QUEUE >> > >> >If things are still going well, enter an asterix "*" for the Queue Name and >> >you will see the List-of-values appear with all the available queues on the >> >Deathrow cluster. Now click on the "Get Job Info" button and we're away! >> >> FYI RIchard, >> >> Safari aborts after entering the Username and Password. > >Congrats! What incantation did you use? I couldn't even get the login >box using Safari. > >Am I brave enough to download yet another browser (Firefox) and try this >again? > >$ SHOW QUEUE works pretty well for me. I guess I'll leave the >Mickey-Clicky stuff to the kids. Here's the best way... # ssh {your-username}@manson.vistech.net Passowrd: {your-password} $ SHOW QUEUE /sundry-qualifiers-of-your-own-choosing -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM "Well my son, life is like a beanstalk, isn't it?" http://tmesis.com/drat.html ------------------------------ Date: 26 Sep 2007 10:15:50 -0500 From: burley.not-this@encompasserve-or-this.org (Graham Burley) Subject: Re: Web-based VMS Que Monitor for Deathrow Message-ID: In article <7arKi.10$fT2.4@newsfe12.lga>, VAXman- @SendSpamHere.ORG writes: > Safari aborts after entering the Username and Password. FWIW it works fine for me with Safari. ------------------------------ Date: 26 Sep 2007 10:37:52 -0500 From: burley.not-this@encompasserve-or-this.org (Graham Burley) Subject: Re: Web-based VMS Que Monitor for Deathrow Message-ID: In article , koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: > Interesting. Seems the demo account has visisbility into everybody's > job, but the product promises visibility into "authorized" jobs. Is > the demo account granted WORLD or is the web server providing the > necessary privilege? That's because most/all the queues have at least W:R, the demo account has no privileges. ------------------------------ Date: Wed, 26 Sep 2007 17:48:25 +0200 From: "P. Sture" Subject: Re: Web-based VMS Que Monitor for Deathrow Message-ID: In article , Robert Deininger wrote: > Congrats! What incantation did you use? I couldn't even get the login > box using Safari. > > Am I brave enough to download yet another browser (Firefox) and try this > again? > > $ SHOW QUEUE works pretty well for me. I guess I'll leave the > Mickey-Clicky stuff to the kids. Using my own username and password with FireFox (on OS X), I got access denied. Tried again in uppercase, and got the same thing. On logging on via ssh, I saw 2 login failures, confirming that those are treated properly, which is good news. Using the TIER3_DEMO username, I could see the batch job I had submitted, so the question of what TIER3_DEMO can see is still open. I also don't like any website resizing my browser windows, so I'll add a "me too" vote. -- Paul Sture Sue's OpenVMS bookmarks: http://eisner.encompasserve.org/~sture/ovms-bookmarks.html ------------------------------ Date: Wed, 26 Sep 2007 08:54:40 -0700 From: jhjr4381 Subject: wierd backup behavior Message-ID: <1190822080.542181.314400@o80g2000hse.googlegroups.com> I have a problem with my backups that I can't quite nail down. We have a two server cluster with one Alpha running VMS 6.2-1h3 and a VAX running VMS 6.2. I have a full backup com file executing on the Alpha system which does an image backup of all the disks (5 drive on the Alpha, 3 on the Vax). There are very few changes /updates made on these systems as they pretty much just store code. These are done on a DLT drive, and it usually only takes one tape for the whole backup. However, the log files show very inconsistent backup activity (number of files stored - varies by 5-10k), only on the Vax disks, even if done by itself. At the end of the log file for each Alpha disk I get the following: Total of 2640 files, 3378686 blocks End of save set At the end of the log file for each Vax disk I get: [file name of last file stored] [EOB] (no number of files / blocks, no 'end of save set') So it seems to just stop. Here is the com file, only one disk is included, as the rest are all the same DCL: $ SET VERIFY $ SHOW TIME $ SET NOON $ SET PROC/PRIV=(BYPASS,READALL) $ mount/for RDAXP$MKB500 $ dism/nounl RDAXP$MKB500 $ INIT RDAXP$MKB500: VOLN01 $ MOUNT/FOR RDAXP$MKB500: $! $ BACKUP/NOREWIND/LIST=DKA100:[BACKUP]DUA510FUL.LOG/IMAGE - /NOALIAS - /RECORD/IGNORE=(INTERLOCK,LABEL,NOBACKUP)/NOASSIST $1$DUA510: - RDAXP$MKB500:DUA510.BCK next disk.... . . $ DISMOUNT RDAXP$MKB500: The first disk backup up is on the Vax, and it 'fails' and the last two are on the Vax which also 'fail'. The Alpha drives are in the middle, and are fine. Here's a 'dir' of the Alpha log files as an example: DKC0FUL.LOG;189 428 21-SEP-2007 21:39:34.79 DKC0FUL.LOG;188 428 14-SEP-2007 22:28:04.22 DKC0FUL.LOG;187 427 31-AUG-2007 20:52:21.01 DKC100FUL.LOG;191 2021 21-SEP-2007 21:54:05.61 DKC100FUL.LOG;190 2021 14-SEP-2007 22:42:18.27 DKC100FUL.LOG;189 2021 31-AUG-2007 21:07:06.77 Here's a 'dir' of the Vax log files: DUA430FUL.LOG;192 10944 21-SEP-2007 22:13:22.05 DUA430FUL.LOG;191 4384 14-SEP-2007 23:01:28.62 DUA430FUL.LOG;190 928 31-AUG-2007 21:26:39.08 DUA510FUL.LOG;199 4224 25-SEP-2007 19:43:36.24 DUA510FUL.LOG;198 2848 21-SEP-2007 20:00:50.25 DUA510FUL.LOG;197 5664 14-SEP-2007 20:00:43.30 DUA510FUL.LOG;196 128 31-AUG-2007 20:01:24.72 DUA510ful.log;199 was from last night which ran by itself as a test (failed). The tape drive itself does not unload, and looks like it's still writing to the tape, so it looks like it doesn't hit the dismount despite the 'set noon'. I'm just looking for a clue to help explain/fix this behavior. It appears that I'm either hitting a limit on the number of (stored) files, or hitting a (temp?) file condition (size?), or I have a aproblem with the tape drive (TZ89 - only with the Vax?). I'm not getting any errors that I can see in the .log files, they just seem to end. Any help would be appreciated, just point, I'll follow! Thanks! Dan - VMS newbie ------------------------------ Date: Wed, 26 Sep 2007 17:11:25 +0100 From: "Richard Brodie" Subject: Re: wierd backup behavior Message-ID: "jhjr4381" wrote in message news:1190822080.542181.314400@o80g2000hse.googlegroups.com... > However, the log files show very inconsistent backup activity (number > of files stored - varies by 5-10k), only on the Vax disks, even if > done by itself. One small point, that might help. I wouldn't call the files you create with /LIST log files. They are save set listing files; useful as a record of the contents of the tape. The logging information will be in the standard output of where the backup job ran from. That would be the place to start looking for errors. If it's run as a batch job specifying /NOLOG, fix that first. ------------------------------ End of INFO-VAX 2007.526 ************************