1 INFO-VAX	Sat, 18 Mar 2006	Volume 2006 : Issue 154       Contents: boot problem - device full Re: boot problem - device full Re: boot problem - device full Re: boot problem - device full+ Re: Does OpenVMS MIME work with your stack? ) Re: Mail Utility - Logical Names It Needs % Re: [F$GETQUI] Please explain RAD ;-)   F ----------------------------------------------------------------------  % Date: Sat, 18 Mar 2006 13:57:26 +0100 ! From: Emil <emilg2SP@AMgazeta.pl> # Subject: boot problem - device full + Message-ID: <dvh044$3i5$1@achot.icm.edu.pl>    Hi all, H I have a big (for me :) I'm a newbe in OpenVMS) problem and hope it can  be solved with your help. I I have Digital Alphastation 255 233MHz with OpenVMS 6.2. Problem is that  / it won't boot. Here is what I get when booting:   9 RMS-F-FUL device full (insufficient space for allocation)    Message form user QUEUE_MANAGEJ QMAN-E-NODISKSPACE, disk space not available for queue manager to continue  0 QMAN-I-FREEDISK, free up 204 blocks on disk DKA0  6 Could someone please tell me how to free these blocks?   regards  Wojtek   ------------------------------  % Date: Sat, 18 Mar 2006 08:21:51 -0500 / From: "William Webb" <william.w.webb@gmail.com> ' Subject: Re: boot problem - device full H Message-ID: <8660a3a10603180521x3bbf5cdbr82ebf9e49b1511d@mail.gmail.com>  . On 3/18/06, Emil <emilg2SP@amgazeta.pl> wrote:	 > Hi all, I > I have a big (for me :) I'm a newbe in OpenVMS) problem and hope it can  > be solved with your help. J > I have Digital Alphastation 255 233MHz with OpenVMS 6.2. Problem is that1 > it won't boot. Here is what I get when booting:  > ; > RMS-F-FUL device full (insufficient space for allocation)  >   > Message form user QUEUE_MANAGEL > QMAN-E-NODISKSPACE, disk space not available for queue manager to continu= e  > 2 > QMAN-I-FREEDISK, free up 204 blocks on disk DKA0 > 8 > Could someone please tell me how to free these blocks? > 	 > regards  > Wojtek >   ) Your default boot device (DKA0:) is full.   # 1.  Boot from an OpenVMS binary CD, 0 2.  Take the menu option to execute DCL commands 3.  Mount DKA0: A 4.  On DKA0:,  free up space by doing such things as purging file A versions, creating new versions of log files and deleting the old 2 ones-- whatever is appropriate for your situation.   HTH,   WWWebb --C NOTE: This email address is only used for noncommerical VMS-related  correspondence. C All unsolicited commercial email will be deemed to be a request for 8 services pursuant to the terms and conditions located at# http://bellsouthpwp.net/w/e/webbww/    ------------------------------  % Date: Sat, 18 Mar 2006 10:30:18 -0500 3 From: "Richard B. Gilbert" <rgilbert88@comcast.net> ' Subject: Re: boot problem - device full 0 Message-ID: <4v2dnTMMWP4WuoHZRVn-ug@comcast.com>   Emil wrote: 	 > Hi all, J > I have a big (for me :) I'm a newbe in OpenVMS) problem and hope it can  > be solved with your help. K > I have Digital Alphastation 255 233MHz with OpenVMS 6.2. Problem is that  1 > it won't boot. Here is what I get when booting:  > ; > RMS-F-FUL device full (insufficient space for allocation)  >   > Message form user QUEUE_MANAGEL > QMAN-E-NODISKSPACE, disk space not available for queue manager to continue > 2 > QMAN-I-FREEDISK, free up 204 blocks on disk DKA0 > 8 > Could someone please tell me how to free these blocks? > 	 > regards  > Wojtek   You can do a "minimum boot".    >>> boot -1  , The boot should stop at the SYSBOOT> prompt. SYSBOOT> set startup_p1 "MIN"  SYSBOOT> continue   F The system will boot without starting the queue manager, or executing  SYSTARTUP_VMS.COM   D Log in at the console and clean up your disk.  If you don't have at E least ten percent free space, you are living on the edge of disaster.   D If you can't get ten percent free, consider buying a bigger disk or  adding a disk.   Finally do:  $ MCR SYSGEN SYSGEN> use current 5 SYSGEN> set startup_p1 ""  ! That's the "null string"  SYSGEN> write current  SYSGEN> EXIT $ F and reboot.  The system should do a normal startup.  I hope I haven't I forgotten any steps, it's been a couple of years since I needed to think     about this sort of thing.   I It's a very good idea to keep an eye on your disk space.  Do it manually  H or write a script to notify you when free space drops below ten percent.  D There are reasons why a System Manager is sometimes called a system   janitor and this is one of them.   ------------------------------  # Date: Sat, 18 Mar 2006 15:30:59 GMT # From: Beach Runner <bob@nospam.com> ' Subject: Re: boot problem - device full ; Message-ID: <TIVSf.81556$Fw6.33277@tornado.tampabay.rr.com>    William Webb wrote:   0 > On 3/18/06, Emil <emilg2SP@amgazeta.pl> wrote: > 	 >>Hi all, I >>I have a big (for me :) I'm a newbe in OpenVMS) problem and hope it can  >>be solved with your help. J >>I have Digital Alphastation 255 233MHz with OpenVMS 6.2. Problem is that1 >>it won't boot. Here is what I get when booting:  >>; >>RMS-F-FUL device full (insufficient space for allocation)  >>  >>Message form user QUEUE_MANAGEL >>QMAN-E-NODISKSPACE, disk space not available for queue manager to continue >>2 >>QMAN-I-FREEDISK, free up 204 blocks on disk DKA0 >>8 >>Could someone please tell me how to free these blocks? >>	 >>regards  >>Wojtek >> >  > + > Your default boot device (DKA0:) is full.  > % > 1.  Boot from an OpenVMS binary CD, 2 > 2.  Take the menu option to execute DCL commands > 3.  Mount DKA0: C > 4.  On DKA0:,  free up space by doing such things as purging file C > versions, creating new versions of log files and deleting the old 4 > ones-- whatever is appropriate for your situation. >  > HTH, >  > WWWebb > --) Or, if you don't have a CD, boot minimum.   	 b -fl 0,1  at sysboot type  sysboot>set startup_p1 "MIN" sysboot>cont     afterword at sysboot type  sysboot>set startup_p1 ""      bbww/    ------------------------------  % Date: Sat, 18 Mar 2006 08:56:02 -0500 ) From: "Neil Rieck" <n.rieck@sympatico.ca> 4 Subject: Re: Does OpenVMS MIME work with your stack?9 Message-ID: <LjUSf.7656$fy1.336666@news20.bellglobal.com>   5 "Neil Rieck" <n.rieck@sympatico.ca> wrote in message  3 news:UqrRf.1216$fy1.126253@news20.bellglobal.com...  >  [...snip...] > K > The good folks at PSC have passed on this interim work-around for my MIME E > problem. I tried it out and it works but I haven't (yet) found any  
 > official9 > OpenVMS documentation describing "/foreign" or "/type".  > 4 >    $MAIL/subj=whatever/foreign/type=2 mime-doc.txt >  > Note that: >  >    send/foreign/type=2 > ! > also works from within VMSMAIL.  >   M Oops. I just discovered that the "send/foreign" suggestion doesn't work when  0 sending a zipped attachment. (I've notified PSC)  H So for the current time I'll still need to use the DCL hack provided by . David Mathog which you can download from here:? http://www3.sympatico.ca/n.rieck/demo_vms/dcl-mmail-scripts.zip J These scripts are not part of a finished product but they do work and are  easy to modify.   
 Neil Rieck Kitchener/Waterloo/Cambridge,  Ontario, Canada.9 http://www3.sympatico.ca/n.rieck/links/cool_openvms.html     ------------------------------  % Date: Sat, 18 Mar 2006 15:04:39 +0100 ( From: Paul Sture <paul.sture@bluewin.ch>2 Subject: Re: Mail Utility - Logical Names It Needs+ Message-ID: <482ibnFi6e67U1@individual.net>    JF Mezei wrote:  > Chris Sharman wrote: > : >>My money would be on a spurious logical MAIL or MAILSHR. >  > 7 > If it is the destination username which is a logical   >  > eg:  > < > $DEFINE CHOCOLATE "This is a sinfully delicious substance" > $MAIL  > MAIL> SEND > TO: CHOCOLATE  > C > Then it would issue a "no such user" message for each word in the G > logical name translation. (Didn't know you could use logicals to have 9 > distribution lists with each name separated by a space)   J The workaround in this case is to precede the username with an underscore:   $MAIL 
 MAIL> SEND TO: _CHOCOLATE   ------------------------------    Date: 18 Mar 2006 19:36:40 +01006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER). Subject: Re: [F$GETQUI] Please explain RAD ;-), Message-ID: <441c6148$1@news.langstoeger.at>  ` In article <441B8600.A38CF594@comcast.net>, David J Dachtera <djesys.nospam@comcast.net> writes:F >AH! Now we have more data. This makes it look like a potential bug inF >the newer code. Since the old queue records in the database might notA >contain a valid RAD field, the system software may try to assume E >something so the F$GETQUI() call will not result in a process dump / D >logout. That assumption might not be valid, as we have seen via the >results you've reported.   E More new data. SHOW QUEUE is obviously not using $GETQUI (as F$GETQUI ' and LIB$GETQUI do) which is shown here:    $ CREATE GETQUI_RAD.FOR          OPTIONS /EXTEND_SOURCE         INCLUDE '($QUIDEF)'            INTEGER*2       que_len          CHARACTER*1023  que_str   3         istat = LIB$GET_FOREIGN (que_str,, que_len) *         IF (.NOT. istat) CALL EXIT (istat)  0 C       QUI$_RAD is still not defined in $QUIDEFf         istat = LIB$GETQUI (QUI$_DISPLAY_QUEUE, QUI$_RESERVED_OUTPUT_85,, que_str(1:que_len),, irad,,)*         IF (.NOT. istat) CALL EXIT (istat)6         TYPE *, que_str(1:que_len), ' QUI$_RAD=', irad           END  ^Z $ FORTRAN GETQUI_RAD $ LINK/NOTRACE GETQUI_RAD  $ EXEC = "$SYS$DISK:[]'"   $ SHOW QUEUE/FULL LUNA$BATCH' Batch queue LUNA$BATCH, idle, on LUNA:: F   /AUTOSTART_ON=(LUNA::) /BASE_PRIORITY=3 /JOB_LIMIT=3 /OWNER=[SYSTEM]   /PROTECTION=(S:M,O:D,G:R,W:S)  $ exec GETQUI_RAD LUNA$BATCH  LUNA$BATCH QUI$_RAD=           0   $ SHOW QUEUE EPLAN" Batch queue EPLAN, idle, on LUNA::F   /AUTOSTART_ON=(LUNA::) /BASE_PRIORITY=3 /JOB_LIMIT=3 /OWNER=[SYSTEM]   /PROTECTION=(S:M,O:D,G:R,W:S)  $ exec GETQUI_RAD EPLAN  EPLAN QUI$_RAD=          -1   E The only difference is, LUNA$BATCH is there for some years now, while # EPLAN is there since a few minutes.   3 >> So, Guy/Hoff, please, your word is required. TIA  > , >Yes, please. Much speculation, little fact. > : >How 'bout someone with the source CDs? Might you have the9 >time/inclination to look this up in the source listings?   K Not me, I'm afraid (and a source CD wouldn't fix the problem, too, right ?)   J In the meantime I can "fix" my queue(s) by doing a SET QUEUE/NORAD for allH queues which show a "0" instead of a "-1" (just to make my JBC inventory procedure happy ;-)    --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------   End of INFO-VAX 2006.154 ************************