INFO-VAX Fri, 09 Nov 2007 Volume 2007 : Issue 614 Contents: Re: "Latch" style Batch Queue Re: "Latch" style Batch Queue Re: "Latch" style Batch Queue Re: "Latch" style Batch Queue Re: "Latch" style Batch Queue Re: "Latch" style Batch Queue Re: "Latch" style Batch Queue Selling: Alphaserver DS15 for less than 5k Re: UCX Ping on a DECWindows Re: UCX Ping on a DECWindows Re: UCX Ping on a DECWindows ---------------------------------------------------------------------- Date: Fri, 09 Nov 2007 10:55:06 +0100 From: Evert van Dijken Subject: Re: "Latch" style Batch Queue Message-ID: <%7WYi.9128$Hv4.3385@amstwist00> Michael D. Ober schreef: > 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. > > Thanks, > Mike Ober. > > submit/after=tomorrow will do the job ------------------------------ Date: 9 Nov 2007 06:15:54 -0600 From: Kilgallen@SpamCop.net (Larry Kilgallen) Subject: Re: "Latch" style Batch Queue Message-ID: In article <%7WYi.9128$Hv4.3385@amstwist00>, Evert van Dijken writes: > Michael D. Ober schreef: >> 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. >> >> Thanks, >> Mike Ober. >> >> > submit/after=tomorrow will do the job Another approach, perhaps closer to what you specify (but not necessarily closer to what you want) would be two queues 1. a "submission" queue that is always stopped 2. an "action" queue that is always running To "start" the operation, release a self-resubmitting (/HOLD) job in the "action" queue (or some third queue) that does a SET ENTRY/REQUEUE on each job in the "submission" queue to the "action" queue". It might be possible to set protections on the "action" queue to keep unprivileged users who are not the owner from submitting directly to it, but perhaps that is not required in your security situation. ------------------------------ Date: Fri, 09 Nov 2007 08:05:52 -0500 From: "Richard B. Gilbert" Subject: Re: "Latch" style Batch Queue Message-ID: <47345B30.1080101@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. > > Thanks, > Mike Ober. > > Why don't you create a second batch queue that runs jobs to start and stop the first? Or, if there is some reason not to create a second queue ISTR that the RUN command can be used to run things at some later time. Sorry, I'm to lazy to look it up for you unless you offer payment! ------------------------------ Date: 9 Nov 2007 07:28:51 -0600 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: "Latch" style Batch Queue Message-ID: In article <13j7bep5prb6bd6@corp.supernews.com>, "Michael D. Ober" writes: > 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 would put a self-resubmitting job in the queue that stops the queue at the appropriate time. Perhaps the DCL SYNCHRONIZE command is the key to knowing when. ------------------------------ Date: Fri, 09 Nov 2007 06:49:48 -0800 From: cycle4fun@excite.com Subject: Re: "Latch" style Batch Queue Message-ID: <1194619788.376760.34760@e9g2000prf.googlegroups.com> On Nov 8, 6:46 pm, "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. > > Thanks, > Mike Ober. I would create a generic queue, which points to a started batch queue with a job_limit=1. This generic queue is stopped, so you can submit jobs to it throughout the day. Then at the end of the database cleanups, start the generic queue and submit a job to the generic queue to stop the generic queue. All of the jobs queued up will run and the last job will stop the generic queue, so you are all set for the next day of jobs. ------------------------------ Date: 9 Nov 2007 08:59:21 -0600 From: briggs@encompasserve.org Subject: Re: "Latch" style Batch Queue Message-ID: In article , koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: > In article <13j7bep5prb6bd6@corp.supernews.com>, "Michael D. Ober" writes: >> 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 would put a self-resubmitting job in the queue that stops the > queue at the appropriate time. Perhaps the DCL SYNCHRONIZE command > is the key to knowing when. If the queue has a /JOB_LIMIT=1 and /SCHEDULE=NOSIZE then submitting a job to do the $ STOP /QUEUE /NEXT would eliminate the need to hang around and do a $SYNCHRONIZE. Personally, I think a two-queue solution is the way to go. Larry's suggestion of a batch job that does a requeue is nice. $ ASSIGN /MERGE makes such a job a one liner. ------------------------------ Date: 9 Nov 2007 12:44:22 -0600 From: Kilgallen@SpamCop.net (Larry Kilgallen) Subject: Re: "Latch" style Batch Queue Message-ID: In article , briggs@encompasserve.org writes: > Personally, I think a two-queue solution is the way to go. > > Larry's suggestion of a batch job that does a requeue is nice. > $ ASSIGN /MERGE makes such a job a one liner. But doing SET ENTRY one job at a time creates a clear log of what was encountered at trigger time. That is not so much for the sake of analyzing this transfer activity as for keeping records of what went on with the set of batch jobs in general. I realize that not everybody loves log files so much as I do :-) ------------------------------ Date: Fri, 9 Nov 2007 08:22:39 -0500 From: "David Turner, Island Computers" Subject: Selling: Alphaserver DS15 for less than 5k Message-ID: <13j8novcm6hhe0@news.supernews.com> IN STOCK Alphaserver DS15 1GB Memory (4 x 256MB) DVD-RW/CDRW On Board U3 SCSI On Board Dual 10/100 36GB 10KRPM Disk Hot Pluggable (our own hot plug bay under CD) No License Only $4995 + shipping We only have 8 so it is purely a case of first come first serve. These would normally sell for over $8000 !!! -- David B Turner Island Computers US Corp 2700 Gregory St, Suite 180 Savannah GA 31404 T: 877-6364332 x201 Intl: 001 912 447 6622 E: dturner@islandco.com F: 912 201 0402 W: http://www.islandco.com The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. ------------------------------ Date: Fri, 09 Nov 2007 08:00:02 -0500 From: "Richard B. Gilbert" Subject: Re: UCX Ping on a DECWindows Message-ID: <473459D2.3080600@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 > Teri, I hate to be the one to break the news to you but DecWindows is SOFTWARE! It has little or nothing to do with the box you run it on. AFAIK DECWindows still works on VAX and Alpha with any VMS release since V5.5-2 at least! Earlier versions may also work. There are some hardware requirements; e.g. memory, a graphics adapter for the system running the display (the "server" in DECWindows terminology), etc. You will have to describe your problem a little more clearly. Exactly what hardware are you talking about? Neither DEC, Compaq, or now HP as ever offered anything called "a DecWindows". DEC did offer hardware that acted as a DECwindows server. As I recall, the first one was based on a stripped VAXstation 3100 (it would not run VMS but had DECwindows built into the firmware). There were later models that were designed from the ground up as DECwindows servers. I used one for a few months in 1994. Like all DEC products they were priced too high to become popular and just faded away when Compaq bought DEC. If you have lost your ability to use "ping" it is not the fault of DECwindows. ------------------------------ Date: Fri, 09 Nov 2007 13:11:14 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: UCX Ping on a DECWindows Message-ID: In article <473459D2.3080600@comcast.net>, "Richard B. Gilbert" writes: > > >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 >> > >Teri, > >I hate to be the one to break the news to you but DecWindows is >SOFTWARE! It has little or nothing to do with the box you run it on. >AFAIK DECWindows still works on VAX and Alpha with any VMS release since >V5.5-2 at least! Earlier versions may also work. There are some >hardware requirements; e.g. memory, a graphics adapter for the system >running the display (the "server" in DECWindows terminology), etc. > >You will have to describe your problem a little more clearly. Exactly >what hardware are you talking about? Neither DEC, Compaq, or now HP as >ever offered anything called "a DecWindows". DEC did offer hardware >that acted as a DECwindows server. As I recall, the first one was based >on a stripped VAXstation 3100 (it would not run VMS but had DECwindows >built into the firmware). There were later models that were designed >from the ground up as DECwindows servers. I used one for a few months >in 1994. Like all DEC products they were priced too high to become >popular and just faded away when Compaq bought DEC. > >If you have lost your ability to use "ping" it is not the fault of >DECwindows. > I'd wager she's got TCPIP Services now. They probably have an old symbol definition for the UCX$PING or none at all. Try executing $ @SYS$MANAGER:TCPIP$DEFINE_COMMANDS.COM -- 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: Fri, 09 Nov 2007 05:22:27 -0800 From: Bob Gezelter Subject: Re: UCX Ping on a DECWindows Message-ID: <1194614547.535758.256390@e9g2000prf.googlegroups.com> On Nov 8, 7:15 pm, 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 thehttp://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 Teri, In general, I concur with the comments made previously about the possibility that the old system was running an older version of the Digital TCP/IP stack, before the name change from UCX to TCPIP. Some questions: - What version of OpenVMS and the IP stack was on the older system? - What version of OpenVMS and the IP stack are on the new system? I agree with Brian (VAXMAN) that it is quite likely a symbol definition is missing or incorrect. How do you attempt to use PING and what is the resulting output? - Bob Gezelter, http://www.rlgsc.com ------------------------------ End of INFO-VAX 2007.614 ************************