INFO-VAX Sun, 11 Nov 2007 Volume 2007 : Issue 617 Contents: Re: "Latch" style Batch Queue Re: "Latch" style Batch Queue Re: Hardcopy documentation Re: Hardcopy documentation Re: Informationweek mentions VMS 30 year anniversary Re: Mylex 960 question Re: Mylex 960 question Re: Mylex 960 question Re: UCX Ping on a DECWindows Re: Unknown BACKUP qualifier in VMS 8.2 VAX, VMS and QBUS Devices Re: VAX, VMS and QBUS Devices Re: VAX, VMS and QBUS Devices Re: VAX, VMS and QBUS Devices ---------------------------------------------------------------------- Date: Sat, 10 Nov 2007 21:23:19 -0600 From: David J Dachtera Subject: Re: "Latch" style Batch Queue Message-ID: <473675A7.80DF2D1E@spam.comcast.net> "Michael D. Ober" wrote: > > Is there a way in VMS 8.3 to create a queue that when it is started, will > only process the jobs in the queue at the time it's started, but then hold > any additional jobs that are submitted until it starts again. Basically, I > need to create a queue that will accumulate jobs during the day and then > start after the system completes database cleanups at night and then > immediately stop. I'd tend to agree with those who suggest having a Generic Batch queue with no /GENERIC_TARGETS and no execution queues which accept jobs from generic queues (no /ENABLE_GENERIC on any execution queues). SUBMIT your jobs to that queue during the processing day. During your nightly procedures, ASSIGN/QUEUE/MERGE that queue to another Generic queue which has at least one execution queue as a /GENERIC_TARGET. You can use a WAIT loop and the PENDING_JOB_COUNT item of F$GETQUI() to wait until the first queue has "drained" into the second, then DEASSIGN/QUEUE the "holding" queue so it will accept new jobs and hold them until you again run the job to drain it into the other queue. I know - clear as mud, eh? -- David J Dachtera dba DJE Systems http://www.djesys.com/ Unofficial OpenVMS Marketing Home Page http://www.djesys.com/vms/market/ Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/ Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/ Unofficial OpenVMS Hobbyist Support Page: http://www.djesys.com/vms/support/ ------------------------------ Date: Sat, 10 Nov 2007 22:06:04 -0600 From: David J Dachtera Subject: Re: "Latch" style Batch Queue Message-ID: <47367FAC.9F9670D4@spam.comcast.net> David J Dachtera wrote: > > "Michael D. Ober" wrote: > > > > Is there a way in VMS 8.3 to create a queue that when it is started, will > > only process the jobs in the queue at the time it's started, but then hold > > any additional jobs that are submitted until it starts again. Basically, I > > need to create a queue that will accumulate jobs during the day and then > > start after the system completes database cleanups at night and then > > immediately stop. > > I'd tend to agree with those who suggest having a Generic Batch queue with no > /GENERIC_TARGETS and no execution queues which accept jobs from generic queues > (no /ENABLE_GENERIC on any execution queues). > > SUBMIT your jobs to that queue during the processing day. > > During your nightly procedures, ASSIGN/QUEUE/MERGE that queue to another Generic > queue which has at least one execution queue as a /GENERIC_TARGET. You can use a > WAIT loop and the PENDING_JOB_COUNT item of F$GETQUI() to wait until the first > queue has "drained" into the second, then DEASSIGN/QUEUE the "holding" queue so > it will accept new jobs and hold them until you again run the job to drain it > into the other queue. > > I know - clear as mud, eh? Actually, having tried it here on my little Alpha, all you would really need might look like this: $ INIT/QUE/BATCH/START OVERNIGHT_EXECUTOR1 $ INIT/QUE/BATCH/START OVERNIGHT_EXECUTOR2 $ INIT/QUE/BATCH/START OVERNIGHT_EXECUTOR- /GENERIC=(OVERNIGHT_EXECUTOR1,OVERNIGHT_EXECUTOR2) $ INIT/QUE/BATCH OVERNIGHT_TASKS/GENERIC That sets it up. Set up the jobs that run during the course of the day (on other queues) to SUBMIT overnight processing to the OVERNIGHT_TASKS queue. Then, at the time of your choosing, have a scheduled job run a command like this: $ ASSIGN/MERGE OVERNIGHT_EXECUTOR OVERNIGHT_TASKS That will move all of the jobs queued up on the OVERNIGHT_TASKS queue to the OVERNIGHT_EXECUTOR queue, which will then distribute jobs to the OVERNIGHT_EXECUTOR1 and OVERNIGHT_EXECUTOR2 queues. On a two-node cluster, one queue on each node would help distribute the load. The OVERNIGHT_TASKS queue should always remain STOPped if you have any batch execution queues which are INITIALIZEd using /ENABLE_GENERIC (which is the default). -- David J Dachtera dba DJE Systems http://www.djesys.com/ Unofficial OpenVMS Marketing Home Page http://www.djesys.com/vms/market/ Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/ Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/ Unofficial OpenVMS Hobbyist Support Page: http://www.djesys.com/vms/support/ ------------------------------ Date: Sat, 10 Nov 2007 20:00:31 GMT From: "Robert Jarratt" Subject: Re: Hardcopy documentation Message-ID: I would be interested but it depends on where you are and how much it would cost to ship them (to the UK). I am especially interested in Orange manuals as these are the ones I particularly remember. Regards Rob "IrishPub" wrote in message news:1194700744.926865.301030@d55g2000hsg.googlegroups.com... > Greetings, > > I have boxes of VMS documentation that I am looking for a new home > for. I was wondering if there is any interest in this. I have VMS > 4.x documentation (the Orange covered manuals), VMS 5.x (the Gray > covered manuals) and OpenVMS documentation (White covers). If there > is interest I can provide more specifics about which manuals I have > (all should be near complete sets, but they have been sitting for > awhile so I would want to check to be sure). > > I also have various books on VMS, including Internals that I would be > willing to part with as well. > > If this is not the right forum, I apologize as I tried to find a group > that would be appropriate for this. > > Thanks for taking a look, > -Ron Patrick > ------------------------------ Date: Sun, 11 Nov 2007 01:51:16 -0000 From: IrishPub Subject: Re: Hardcopy documentation Message-ID: <1194745876.265898.48990@v3g2000hsg.googlegroups.com> On Nov 10, 2:00 pm, "Robert Jarratt" wrote: > I would be interested but it depends on where you are and how much it would > cost to ship them (to the UK). I am especially interested in Orange manuals > as these are the ones I particularly remember. > > Regards > > Rob > > "IrishPub" wrote in message > > news:1194700744.926865.301030@d55g2000hsg.googlegroups.com... > > > Greetings, > > > I have boxes of VMS documentation that I am looking for a new home > > for. I was wondering if there is any interest in this. I have VMS > > 4.x documentation (the Orange covered manuals), VMS 5.x (the Gray > > covered manuals) and OpenVMS documentation (White covers). If there > > is interest I can provide more specifics about which manuals I have > > (all should be near complete sets, but they have been sitting for > > awhile so I would want to check to be sure). > > > I also have various books on VMS, including Internals that I would be > > willing to part with as well. > > > If this is not the right forum, I apologize as I tried to find a group > > that would be appropriate for this. > > > Thanks for taking a look, > > -Ron Patrick I am located near St Louis, Missouri. The White set is dated May 1993 for Open VMS VAX 6.0 (Open VMS AXP 1.5) ------------------------------ Date: Sat, 10 Nov 2007 15:42:57 -0500 From: JF Mezei Subject: Re: Informationweek mentions VMS 30 year anniversary Message-ID: Main, Kerry wrote: > Well, knowing how reporters are, they likely heard "OpenVMS V8.3-1H1", but their > notes recorded OpenVMS V8.3" without understanding the differences. had a professional PR firm been involved (since HP's own marketing dept who have such expertise refuses to handle VMS related stuff), they would have told you to not mention that VMS is getting a new release when refering to V8.3-1H1. Whowever spoke to the press should have just mentioned that VMS is adding support for such and such hardware with a few new utilities to better manage such and such hardware. Since reporters have no clue on what was available before (since VMS is not openly marketed), they have no point of reference on what an 8.3-1H1 really means and don't know that 8.3 has been out for over a year already. ------------------------------ Date: Sat, 10 Nov 2007 11:51:54 -0800 From: H Vlems Subject: Re: Mylex 960 question Message-ID: <1194724314.681568.99130@k79g2000hse.googlegroups.com> On 10 nov, 19:35, s...@obanion.us wrote: > Have you tried a hard resert or power cycle? I have a 960 in my AS > 2100A configured like yours, and I think I did this once just to see > what happened. > > When the 960 initializes, it should probe the exisitng drives, build > it's device table, and respond to SRM and VMS with a DRAx for each > disk. > > Unless the drive did actuly die when you pulled it out, whcih happens > on occasion. > > Sean > > On Nov 10, 3:25 am, H Vlems wrote: > > > First of all let me start with admitting that my brain was not yet > > switched on this morning while my hands were already busy fumbling > > with an Alpha. > > The Alpha in question is an AlphaServer 1200. The internal drives are > > all connected to a Mylex 960 raid controller. All disks are connected > > as JBOD, so no actual RAID is performed by the Mylex. > > The Alpha was on the >>> prompt and I pulled the top disk (DRA0:) > > which happens to be the system disk BTW. > > At that point my brain engaged and its first thought was "s%%t". I > > pushed the disk back in and an orange led came on. > > As I feared, >>> SHOW DEV listed DRA0: as JBOD FAILED. > > > Is there a way to get the disk back on line or do I need to > > reconfigure the entire JBOD set and reinstall VMS again? > > Actually the latter is not much of a problem, but it took the Alpha > > more than a day to configure the JBOD disk set when I first configured > > the system early this year. > > > Hans Vlems The first thing I tried is power cycling the system. The amber led stays on unfortunately. ------------------------------ Date: Sat, 10 Nov 2007 11:58:16 -0800 From: H Vlems Subject: Re: Mylex 960 question Message-ID: <1194724696.953923.324140@19g2000hsx.googlegroups.com> On 10 nov, 16:11, Jur van der Burg <"lddriver at digiater dot nl"> wrote: > Or boot from a VMS installation cd and excute the swxcr software > from VMS. I may have a copy somewhere. > > Jur. > > R.A.Omond wrote: > > H Vlems wrote: > >> First of all let me start with admitting that my brain was not yet > >> switched on this morning while my hands were already busy fumbling > >> with an Alpha. > >> The Alpha in question is an AlphaServer 1200. The internal drives are > >> all connected to a Mylex 960 raid controller. All disks are connected > >> as JBOD, so no actual RAID is performed by the Mylex. > >> The Alpha was on the >>> prompt and I pulled the top disk (DRA0:) > >> which happens to be the system disk BTW. > >> At that point my brain engaged and its first thought was "s%%t". I > >> pushed the disk back in and an orange led came on. > >> As I feared, >>> SHOW DEV listed DRA0: as JBOD FAILED. > > >> Is there a way to get the disk back on line or do I need to > >> reconfigure the entire JBOD set and reinstall VMS again? > >> Actually the latter is not much of a problem, but it took the Alpha > >> more than a day to configure the JBOD disk set when I first configured > >> the system early this year. > > > Hans, this is from very distant memory, so don't be too harsh on me > > if it's of fthe mark. > > > You should have a floppy with the SWXCR utility on it somewhere (since > > you had to configure the JBOD earlier this year as you mention above). > > There should be an option to "set optimal dra0:" (or something like > > that). It should not be necessary to reconfigure the entire JBOD set > > and reinstall VMS. Hello Jur, the AS1200 runs V8.3 but the most recent VMS version I've got on cd is V7.3-1. That is probably not a problem since swxcr has no clue about VMS versions, right? What command do I use when VMS is booted from cd? Bedankt alvast, Hans ------------------------------ Date: Sat, 10 Nov 2007 13:16:38 -0800 From: IanMiller Subject: Re: Mylex 960 question Message-ID: <1194729398.540789.311560@o38g2000hse.googlegroups.com> You need the raid config utility (RCU) and set the disk to 'optimal' See http://h18006.www1.hp.com/alphaserver/products/storage/retired/ra230/index.html download the RCU and put it on a floppy and run it from the console. The docs are on that site. ------------------------------ Date: Sat, 10 Nov 2007 21:11:04 -0600 From: David J Dachtera Subject: Re: UCX Ping on a DECWindows Message-ID: <473672C8.A5845CEB@spam.comcast.net> Coach Teri wrote: > > We recently migrated from a traditional DEC Vax box to a DecWindows. > We have lost our capability to use the UCX ping from within the > system. > > I am an application support person and am having trouble effectively > conveying this point to the vendor support group. > Can you offer any help. I found information on the > http://www.uni-giessen.de/faq/archiv/vms-ucx-faq.part1/msg00000.html > site for UCX FAQ's it states > "This document contains "Frequently Asked Questions" (or FAQ for > short) about DEC TCP/IP Services for OpenVMS, also known as UCX, from > an earlier version." > It goes on to have a section about about installing a patch kit for > the DECWindows. We have been told that installing the patch is not > something we want to do. Is this correct? How do I recover the UCX > Ping capabilities > thanks > Teri As others have pointed out, the reference "a DecWindows" is confusing since, to my knowledge, there never was such a thing. DECwindows is/was Digital's X11 implementation on VMS and others, including VMS on VAX and Alpha and, I beleive, also on I64. If you could, perhaps, describe more fully exactly what you mean by "a DecWindows", perhaps we'd be better able to interpret your situation and what you are asking. Try describing exactly what steps you took: - Did you install new software? ...new PAKs? - Did you move the software from VAX to Alpha? ...from VAX to I64? ...from one VAX to another? What exactly, in great detail, did you do? -- David J Dachtera dba DJE Systems http://www.djesys.com/ Unofficial OpenVMS Marketing Home Page http://www.djesys.com/vms/market/ Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/ Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/ Unofficial OpenVMS Hobbyist Support Page: http://www.djesys.com/vms/support/ ------------------------------ Date: Sat, 10 Nov 2007 20:57:54 -0600 From: David J Dachtera Subject: Re: Unknown BACKUP qualifier in VMS 8.2 Message-ID: <47366FB2.9C0A0795@spam.comcast.net> Ron Johnson wrote: > > On 11/07/07 08:06, Bob Koehler wrote: > > In article , Ron Johnson writes: > >> Command: BACK/STOR=V2SLS/RELEASE_TAPE/LIST=_MBA25078:/FULL > >> > > > > From my 6.2 system, I get a pretty good hint: > > > > $ backup/store=v2sls nl: nl: > > %BACKUP-F-NOSLS, qualifier /STORAGE_MANAGEMENT is invalid when SLS is not instal > > led > > That's a start! > > But where can I look to determine what it actually does, and whether > I can take advantage of it beyond STORA START SYSTEM_BACKUP? About the only place to look is in SLS$SYSTEM:SYSBAK.COM. It's rather a major piece of work, and not without its foibles, but it does yield some clues when you study it and the SLS$SYSBAK_LOGS: files. Whether you can exploit any of that outside of either SLS or ABS is rather a good question, I should think. I know of other folks who've written their own wrappers around VMS BACKUP, MTI's TapeControl not being the least of them, and entirely DCL-based suites have been known to be done (not sure how recommendable that might be, though). -- David J Dachtera dba DJE Systems http://www.djesys.com/ Unofficial OpenVMS Marketing Home Page http://www.djesys.com/vms/market/ Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/ Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/ Unofficial OpenVMS Hobbyist Support Page: http://www.djesys.com/vms/support/ ------------------------------ Date: 10 Nov 2007 18:52:23 GMT From: billg999@cs.uofs.edu (Bill Gunshannon) Subject: VAX, VMS and QBUS Devices Message-ID: <5pmcv7Fs09frU1@mid.individual.net> OK, here's a quastion that may seem rather strange, but I am serious. If I put a QBUS extender on a VAX 4000-100 can I put an RXV11 on it? Will VMS recognize it and allow access to RX01/RX02 disks? And, lastly, if this will actually work, can VMS recognize and read any PDP-11 formats? bill -- Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves bill@cs.scranton.edu | and a sheep voting on what's for dinner. University of Scranton | Scranton, Pennsylvania | #include ------------------------------ Date: Sat, 10 Nov 2007 17:37:19 -0500 From: "Richard B. Gilbert" Subject: Re: VAX, VMS and QBUS Devices Message-ID: <4736329F.4000705@comcast.net> Bill Gunshannon wrote: > OK, here's a quastion that may seem rather strange, but I am serious. > If I put a QBUS extender on a VAX 4000-100 can I put an RXV11 on it? > Will VMS recognize it and allow access to RX01/RX02 disks? And, lastly, > if this will actually work, can VMS recognize and read any PDP-11 formats? > > bill > VMS SHOULD be able to read PDP-11 formats; especially ODS-1. OTOH, you'll be damned lucky if the RX01/RX02 disks are still readable, and if the drives still work, etc. ------------------------------ Date: 11 Nov 2007 00:17:42 GMT From: billg999@cs.uofs.edu (Bill Gunshannon) Subject: Re: VAX, VMS and QBUS Devices Message-ID: <5pn016FrsatiU1@mid.individual.net> In article <4736329F.4000705@comcast.net>, "Richard B. Gilbert" writes: > Bill Gunshannon wrote: >> OK, here's a quastion that may seem rather strange, but I am serious. >> If I put a QBUS extender on a VAX 4000-100 can I put an RXV11 on it? >> Will VMS recognize it and allow access to RX01/RX02 disks? And, lastly, >> if this will actually work, can VMS recognize and read any PDP-11 formats? >> >> bill >> > > VMS SHOULD be able to read PDP-11 formats; especially ODS-1. OTOH, > you'll be damned lucky if the RX01/RX02 disks are still readable, and if > the drives still work, etc. The drives work just fine. They are on a PDP-11 at the moment. As for the readability of RX01/RX02. I have dozens and dozens of them dating back to the days of the MINC and they all still read without a problem. I was more concerned about wether or not the controller being 18 bit was going to cause a problem. bill -- Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves bill@cs.scranton.edu | and a sheep voting on what's for dinner. University of Scranton | Scranton, Pennsylvania | #include ------------------------------ Date: Sat, 10 Nov 2007 21:38:41 -0700 From: Jeff Campbell Subject: Re: VAX, VMS and QBUS Devices Message-ID: <1194755489_7157@sp12lax.superfeed.net> Bill Gunshannon wrote: > In article <4736329F.4000705@comcast.net>, > "Richard B. Gilbert" writes: >> Bill Gunshannon wrote: >>> OK, here's a quastion that may seem rather strange, but I am serious. >>> If I put a QBUS extender on a VAX 4000-100 can I put an RXV11 on it? >>> Will VMS recognize it and allow access to RX01/RX02 disks? And, lastly, >>> if this will actually work, can VMS recognize and read any PDP-11 formats? >>> >>> bill >>> >> VMS SHOULD be able to read PDP-11 formats; especially ODS-1. OTOH, >> you'll be damned lucky if the RX01/RX02 disks are still readable, and if >> the drives still work, etc. > > The drives work just fine. They are on a PDP-11 at the moment. As > for the readability of RX01/RX02. I have dozens and dozens of them > dating back to the days of the MINC and they all still read without > a problem. > > I was more concerned about wether or not the controller being 18 bit > was going to cause a problem. > > bill > Not having tested it, 8-) it should work fine. The RXV11 does not do DMA so the 18 bit issue isn't an issue. 8-) $ HELP EXCHANGE Jeff ----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet News==---- http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups ----= East and West-Coast Server Farms - Total Privacy via Encryption =---- ------------------------------ End of INFO-VAX 2007.617 ************************