1 INFO-VAX	Tue, 16 Aug 2005	Volume 2005 : Issue 455       Contents: Curious problem with the VAX  Re: Curious problem with the VAX  Re: Curious problem with the VAX  Re: Curious problem with the VAX  Re: Curious problem with the VAX+ Finding virtual disks (Was:  SAMBA for VMS) / Re: Finding virtual disks (Was:  SAMBA for VMS) % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set % Re: Help Needed: Tape Backup Save Set  Re: Image restore fails 3 LDDRIVER original developer (was Re: SAMBA for VMS) , Print Queue in "starting" state  --  cause??0 Re: Print Queue in "starting" state  --  cause??0 Re: Print Queue in "starting" state  --  cause??0 Re: Print Queue in "starting" state  --  cause??. Re: Print Queue in "starting" state -- cause??D Re: Problems with updating firmware on SDLT1 drives using LTT on VMSK Re: Problems with updating firmware on SDLT1 drives using LTT on VMS VMSVMS  Re: SAMBA for VMS  Re: SAMBA for VMS  Re: SAMBA for VMS  Re: SAMBA for VMS 7 Re: TCPIP Services: SMTP bug/wrong logic with 450 codes  The Educational License Program   F ----------------------------------------------------------------------   Date: 15 Aug 2005 18:46:57 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)% Subject: Curious problem with the VAX , Message-ID: <3mc690F1633n5U1@individual.net>  C Well, I was actually able to get the VAX going again.  The CD seems A to come and go pretty much as it pleases but it stays around long   enough get things running again.  A But I have run into an interesting anomaly.  I will cut and paste B from my console and maybe someone can tell me what is going on and how to fix it.  E I have this at the end of my SYSTARTUP_VMS.COM (just before the EXIT)      $ WRITE SYS$OUTPUT "" / $ WRITE SYS$OUTPUT "Mount the USERS Filesystem"  $ WRITE SYS$OUTPUT ""  $ mount $1$DUA2: users users:     ; After starting up the following is displayed on my console:        Mount the USERS Filesystem  5 %MOUNT-I-MOUNTED, USERS mounted on _$1$DUA2: (HSJ002)      But when I do a SHOW DEV I get:   P Device                  Device           Error    Volume         Free  Trans MntP  Name                   Status           Count     Label        Blocks Count Cnt. $1$DKA40:     (HSJ002)  Online               0P $1$DUA1:      (HSJ002)  Mounted              0  OVMSVAXSYS    87083342   173   1. $1$DUA2:      (HSJ002)  Online               0. $1$DUA3:      (HSJ002)  Online               0  . Device                  Device           Error.  Name                   Status           Count. FTA0:                   Offline              0. OPA0:                   Online               0. TNA0:                   Offline              0  . Device                  Device           Error.  Name                   Status           Count. EXA0:                   Online               0. EXA3:                   Online               0. EXA4:                   Online               0. EXA5:                   Online               0. EXB0:                   Online               0. MPA0:                   Offline              0. PAA0:                   Online               0    , You will note that $1$DUA2: is not mounted!!  / However, if I then type the same command I get:      $ mount $1$DUA2: users users: 5 %MOUNT-I-MOUNTED, USERS mounted on _$1$DUA2: (HSJ002)  $ sh dev  P Device                  Device           Error    Volume         Free  Trans MntP  Name                   Status           Count     Label        Blocks Count Cnt. $1$DKA40:     (HSJ002)  Online               0P $1$DUA1:      (HSJ002)  Mounted              0  OVMSVAXSYS    87083256   173   1P $1$DUA2:      (HSJ002)  Mounted alloc        0  USERS        106613755     1   1. $1$DUA3:      (HSJ002)  Online               0  . Device                  Device           Error.  Name                   Status           Count. FTA0:                   Offline              0. OPA0:                   Online               0. TNA0:                   Offline              0  . Device                  Device           Error.  Name                   Status           Count. EXA0:                   Online               0. EXA3:                   Online               0. EXA4:                   Online               0. EXA5:                   Online               0. EXB0:                   Online               0. MPA0:                   Offline              0. PAA0:                   Online               0 $     E And now it is mounted!!  Why does this command not work while booting B (although the message says it does) and yet works fine afterwards?   bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------   Date: 15 Aug 2005 19:04:01 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)) Subject: Re: Curious problem with the VAX , Message-ID: <3mc791F15t0akU1@individual.net>  C In article <1124132447.530962.114750@z14g2000cwz.googlegroups.com>, ! 	shoppa@trailing-edge.com writes:  >> $ WRITE SYS$OUTPUT ""2 >> $ WRITE SYS$OUTPUT "Mount the USERS Filesystem" >> $ WRITE SYS$OUTPUT ""  >> $ mount $1$DUA2: users users: > ' >> Why does this command not work while   >> booting (although the message >> says it does) > F > It did work.  But when the startup process exited it got dismounted. >  > Make it $mount/system. >    Thank you!!    bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------    Date: 15 Aug 2005 12:00:47 -0700 From: shoppa@trailing-edge.com) Subject: Re: Curious problem with the VAX C Message-ID: <1124132447.530962.114750@z14g2000cwz.googlegroups.com>    > $ WRITE SYS$OUTPUT "" 1 > $ WRITE SYS$OUTPUT "Mount the USERS Filesystem"  > $ WRITE SYS$OUTPUT ""  > $ mount $1$DUA2: users users:   & > Why does this command not work while > booting (although the message  > says it does)   D It did work.  But when the startup process exited it got dismounted.   Make it $mount/system.   Tim.   ------------------------------  % Date: Mon, 15 Aug 2005 15:16:40 -0400  From: norm.raphael@metso.com) Subject: Re: Curious problem with the VAX Q Message-ID: <OF24992867.CAE653D6-ON8525705E.0069B8FE-8525705E.0069E5C5@metso.com>   : bill@triangle.cs.uofs.edu wrote on 08/15/2005 02:46:57 PM:  E > Well, I was actually able to get the VAX going again.  The CD seems C > to come and go pretty much as it pleases but it stays around long " > enough get things running again. > C > But I have run into an interesting anomaly.  I will cut and paste D > from my console and maybe someone can tell me what is going on and > how to fix it. > G > I have this at the end of my SYSTARTUP_VMS.COM (just before the EXIT)  >  >  > $ WRITE SYS$OUTPUT "" 1 > $ WRITE SYS$OUTPUT "Mount the USERS Filesystem"  > $ WRITE SYS$OUTPUT ""  > $ mount $1$DUA2: users users:  > > Well, you mounted it process-private by omitting the "/SYSTEM": qualifier.  It dismounted when your startup process ended. > = > After starting up the following is displayed on my console:  >  >  >  > Mount the USERS Filesystem > 7 > %MOUNT-I-MOUNTED, USERS mounted on _$1$DUA2: (HSJ002)  >  > ! > But when I do a SHOW DEV I get:  > : > Device                  Device           Error    Volume > Free  Trans Mnt : >  Name                   Status           Count     Label > Blocks Count Cnt0 > $1$DKA40:     (HSJ002)  Online               0< > $1$DUA1:      (HSJ002)  Mounted              0  OVMSVAXSYS > 87083342   173   10 > $1$DUA2:      (HSJ002)  Online               00 > $1$DUA3:      (HSJ002)  Online               0 > 0 > Device                  Device           Error0 >  Name                   Status           Count0 > FTA0:                   Offline              00 > OPA0:                   Online               00 > TNA0:                   Offline              0 > 0 > Device                  Device           Error0 >  Name                   Status           Count0 > EXA0:                   Online               00 > EXA3:                   Online               00 > EXA4:                   Online               00 > EXA5:                   Online               00 > EXB0:                   Online               00 > MPA0:                   Offline              00 > PAA0:                   Online               0 >  > . > You will note that $1$DUA2: is not mounted!! > 1 > However, if I then type the same command I get:  >  >  > $ mount $1$DUA2: users users: 7 > %MOUNT-I-MOUNTED, USERS mounted on _$1$DUA2: (HSJ002) 
 > $ sh dev > : > Device                  Device           Error    Volume > Free  Trans Mnt : >  Name                   Status           Count     Label > Blocks Count Cnt0 > $1$DKA40:     (HSJ002)  Online               0< > $1$DUA1:      (HSJ002)  Mounted              0  OVMSVAXSYS > 87083256   173   17 > $1$DUA2:      (HSJ002)  Mounted alloc        0  USERS  > 106613755     1   1 0 > $1$DUA3:      (HSJ002)  Online               0 > 0 > Device                  Device           Error0 >  Name                   Status           Count0 > FTA0:                   Offline              00 > OPA0:                   Online               00 > TNA0:                   Offline              0 > 0 > Device                  Device           Error0 >  Name                   Status           Count0 > EXA0:                   Online               00 > EXA3:                   Online               00 > EXA4:                   Online               00 > EXA5:                   Online               00 > EXB0:                   Online               00 > MPA0:                   Offline              00 > PAA0:                   Online               0 > $  >  > G > And now it is mounted!!  Why does this command not work while booting D > (although the message says it does) and yet works fine afterwards? >   C You have again mounted it process-private.  If you logout and login  it will again be not mounted.    > bill >  > --E > Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three  wolvesF > bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. > University of Scranton   |@ > Scranton, Pennsylvania   |         #include <std.disclaimer.h>   ------------------------------  % Date: Mon, 15 Aug 2005 15:24:24 -0400 - From: William Webb <william.w.webb@gmail.com> ) Subject: Re: Curious problem with the VAX 7 Message-ID: <8660a3a105081512246630779a@mail.gmail.com>   F On 15 Aug 2005 18:46:57 GMT, Bill Gunshannon <bill@cs.uofs.edu> wrote:E > Well, I was actually able to get the VAX going again.  The CD seems C > to come and go pretty much as it pleases but it stays around long " > enough get things running again. >=20C > But I have run into an interesting anomaly.  I will cut and paste D > from my console and maybe someone can tell me what is going on and > how to fix it. >=20G > I have this at the end of my SYSTARTUP_VMS.COM (just before the EXIT)  >=20 >=20 > $ WRITE SYS$OUTPUT "" 1 > $ WRITE SYS$OUTPUT "Mount the USERS Filesystem"  > $ WRITE SYS$OUTPUT ""  > $ mount $1$DUA2: users users:  >=20 >=20= > After starting up the following is displayed on my console:  >=20 >=20 >=20 > Mount the USERS Filesystem >=207 > %MOUNT-I-MOUNTED, USERS mounted on _$1$DUA2: (HSJ002)  >=20 >=20! > But when I do a SHOW DEV I get:  >=20L > Device                  Device           Error    Volume         Free  Tr= ans Mnt L >  Name                   Status           Count     Label        Blocks Co= unt Cnt 0 > $1$DKA40:     (HSJ002)  Online               0L > $1$DUA1:      (HSJ002)  Mounted              0  OVMSVAXSYS    87083342   = 173   1 0 > $1$DUA2:      (HSJ002)  Online               00 > $1$DUA3:      (HSJ002)  Online               0 >=200 > Device                  Device           Error0 >  Name                   Status           Count0 > FTA0:                   Offline              00 > OPA0:                   Online               00 > TNA0:                   Offline              0 >=200 > Device                  Device           Error0 >  Name                   Status           Count0 > EXA0:                   Online               00 > EXA3:                   Online               00 > EXA4:                   Online               00 > EXA5:                   Online               00 > EXB0:                   Online               00 > MPA0:                   Offline              00 > PAA0:                   Online               0 >=20 >=20. > You will note that $1$DUA2: is not mounted!! >=201 > However, if I then type the same command I get:  >=20 >=20 > $ mount $1$DUA2: users users: 7 > %MOUNT-I-MOUNTED, USERS mounted on _$1$DUA2: (HSJ002) 
 > $ sh dev >=20L > Device                  Device           Error    Volume         Free  Tr= ans Mnt L >  Name                   Status           Count     Label        Blocks Co= unt Cnt 0 > $1$DKA40:     (HSJ002)  Online               0L > $1$DUA1:      (HSJ002)  Mounted              0  OVMSVAXSYS    87083256   = 173   1 L > $1$DUA2:      (HSJ002)  Mounted alloc        0  USERS        106613755   =   1   1 0 > $1$DUA3:      (HSJ002)  Online               0 >=200 > Device                  Device           Error0 >  Name                   Status           Count0 > FTA0:                   Offline              00 > OPA0:                   Online               00 > TNA0:                   Offline              0 >=200 > Device                  Device           Error0 >  Name                   Status           Count0 > EXA0:                   Online               00 > EXA3:                   Online               00 > EXA4:                   Online               00 > EXA5:                   Online               00 > EXB0:                   Online               00 > MPA0:                   Offline              00 > PAA0:                   Online               0 > $  >=20 >=20G > And now it is mounted!!  Why does this command not work while booting D > (although the message says it does) and yet works fine afterwards? >=20 > bill >=20 > --L > Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolve= s F > bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. > University of Scranton   |@ > Scranton, Pennsylvania   |         #include <std.disclaimer.h> >=20  , You're mounting it privately, for one thing.  C You probably want to MOUNT/SYSTEM if your students' directories are ! residing on that particular disk.   ; SYNTAX:  MOUNT/SYSTEM <physical device name> <volume label>   A There are more variations to mount than you can shake a stick at.    HELP /MOUNT is quite verbose.   I Good practice is to refer to physical device names as little as possible;   B Most system managers create system logicals for each physical diskA drive early in the startup process and refer to *them* thereafter B unless there's some requirement to refer to a physical device name that can't be gotten around.  B That way, if you have to restore or copy the contents of a failingD disk to a spare, you only have to change your reference in one placeF instead of searching through all your DCL to replace all the instances$ of Dxxx that are hardcoded in there.  ( Have you bought David Miller's book? =20  F You ought to give it a look, as there's a lot in there that would make your life easier.    HTH    WWWebb --=20 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: Mon, 15 Aug 2005 23:59:08 -0400 2 From: "Stanley F. Quayle" <squayle@insight.rr.com>4 Subject: Finding virtual disks (Was:  SAMBA for VMS)- Message-ID: <43012C4C.1035.B8D3071@localhost>   0 On 15 Aug 2005 at 21:06, David J Dachtera wrote:G > > Before it becomes supported, can the device type be changed so that F > > the virtual disks come up as "D" something?  To see the disks on aC > > system, I do a "SHOW DEVICE D", and this command will miss them 
 > > all...  C I have a command procedure to display disk information.  Here's an   excerpt:   	<loops through all disks> 	disk = f$device ("*", "DISK")5 	If .not. f$getdvi(disk,"mnt")  then Goto GET_NXT_DEV ; 	If f$getdvi (disk,"devclass") .ne. 1 then Goto GET_NXT_DEV   - Turns out that if I change the first line to:    	disk = f$device ("*")  F It chews through every device on the system, not just "disks".  Since D only a disk can be mounted, or have a device class of 1, it doesn't F skip the virtual disks.  I know it finds VDAx virtual disks by actual  testing.  3 So, all is well.  Except F$DEVICE is broken.  Yuck.   
 --Stan Quayle  Quayle Consulting Inc.  
 ----------- Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363 3 8572 North Spring Ct., Pickerington, OH  43147  USA 0 stan-at-stanq-dot-com       http://www.stanq.com) "OpenVMS, when downtime is not an option"    ------------------------------  % Date: Mon, 15 Aug 2005 22:13:01 -0700 ( From: Jeff Cameron <roktsci@comcast.net>8 Subject: Re: Finding virtual disks (Was:  SAMBA for VMS)0 Message-ID: <BF26C3ED.125BC%roktsci@comcast.net>  K On 8/15/05 8:59 PM, in article 43012C4C.1035.B8D3071@localhost, "Stanley F. ' Quayle" <squayle@insight.rr.com> wrote:   2 > On 15 Aug 2005 at 21:06, David J Dachtera wrote:G >>> Before it becomes supported, can the device type be changed so that F >>> the virtual disks come up as "D" something?  To see the disks on aC >>> system, I do a "SHOW DEVICE D", and this command will miss them 
 >>> all... > D > I have a command procedure to display disk information.  Here's an
 > excerpt: >  > <loops through all disks>  > disk = f$device ("*", "DISK") 6 > If .not. f$getdvi(disk,"mnt")  then Goto GET_NXT_DEV< > If f$getdvi (disk,"devclass") .ne. 1 then Goto GET_NXT_DEV > / > Turns out that if I change the first line to:  >  > disk = f$device ("*")  > G > It chews through every device on the system, not just "disks".  Since E > only a disk can be mounted, or have a device class of 1, it doesn't G > skip the virtual disks.  I know it finds VDAx virtual disks by actual 
 > testing. > 5 > So, all is well.  Except F$DEVICE is broken.  Yuck.  >  > --Stan Quayle  > Quayle Consulting Inc. >  > ----------/ > Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363 5 > 8572 North Spring Ct., Pickerington, OH  43147  USA 2 > stan-at-stanq-dot-com       http://www.stanq.com+ > "OpenVMS, when downtime is not an option"  >  > J I think it is important to understand that a Virtual disk (aka a ram disk)K is a completely different class of device from magnetic disks. Additionally ) their drivers are considerably different.   H Just because this type of device supports a file system and has the wordK "disk" in it's name does not mean it should show up as a device class of 1.   G Magnetic tapes can also support a file system, but they are a different = class of devices, hence they have a different type of driver.   H That is why the virtual disk device mnemonic starts with a V (as in VDA). instead of a D (as in DUA, DIA, DKA, DJA etc.)  H Remember the TU58 tape cartridge? It had a complete files-11 file systemH implemented on tape that even allowed you to delete files and create newL ones in the space that was released when files were deleted. From the user'sK standpoint it reacted like a very slow disk, when in fact it was a magnetic 1 tape, and it did not show up as a class 1 device.    Jeff   ------------------------------  % Date: Mon, 15 Aug 2005 13:00:46 -0500 ( From: Wayne Sewell <wayne@tachysoft.com>. Subject: Re: Help Needed: Tape Backup Save Set0 Message-ID: <00A48521.D119F515.13@tachysoft.com>  ) >From: "Chris Allen" <ca.allen@gmail.com>  >X-Newsgroups: comp.os.vms/ >Subject: Re: Help Needed: Tape Backup Save Set ! >Date: 15 Aug 2005 09:36:09 -0700  > I >Interesting...  Have they fixed this in newer versions?  I'm running 7.1  >     P Fixed what?  You need to quote enough of the message you are responding to that N we know what "this" is.  There have been dozens of messages in this thread and1 many of them have strayed off the original topic.    Wayne O =============================================================================== N Wayne Sewell, Tachyon Software Consulting  (281)812-0738   wayne@tachysoft.com; http://www.tachysoft.com/www/tachyon.html and wayne.html    O =============================================================================== P Jake Blues:"You traded the Caddy for a microphone? ...... Okay, I can buy that."   ------------------------------    Date: 15 Aug 2005 11:00:28 -0700( From: "Chris Allen" <ca.allen@gmail.com>. Subject: Re: Help Needed: Tape Backup Save SetC Message-ID: <1124128828.745269.114240@o13g2000cwo.googlegroups.com>   2 Thanks for the articles, I'll take a look at them.   ------------------------------  % Date: Mon, 15 Aug 2005 13:05:46 -0500 ( From: Wayne Sewell <wayne@tachysoft.com>. Subject: Re: Help Needed: Tape Backup Save Set0 Message-ID: <00A48522.83F126D6.15@tachysoft.com>  % >From: "AEF" <spamsink2001@yahoo.com>  >X-Newsgroups: comp.os.vms/ >Subject: Re: Help Needed: Tape Backup Save Set ! >Date: 15 Aug 2005 08:59:37 -0700  >  >  >Chris Allen wrote: F >> Not being stubborn, just being cautious.  As I know next to nothingG >> about DECNet I fear making a mistake that could result in a security G >> hole.  The VMS servers here run on a hardened network, and it is top + >> priority that they are properly secured.  >  >  >Nitpick alert!!!  >  >It's spelled DECnet.   :-|  >   N Us lazy sumbitches refuse to expend effort worrying about stuff like that.  OrM bothering with the shift key.  I just say decnet.  I think people know what I  mean. O =============================================================================== N Wayne Sewell, Tachyon Software Consulting  (281)812-0738   wayne@tachysoft.com; http://www.tachysoft.com/www/tachyon.html and wayne.html    O =============================================================================== P Jake Blues:"You traded the Caddy for a microphone? ...... Okay, I can buy that."   ------------------------------    Date: 15 Aug 2005 11:14:46 -0700( From: "Chris Allen" <ca.allen@gmail.com>. Subject: Re: Help Needed: Tape Backup Save SetC Message-ID: <1124129686.739259.311900@g43g2000cwa.googlegroups.com>   T >    Fixed what?  You need to quote enough of the message you are responding to thatS >    we know what "this" is.  There have been dozens of messages in this thread and 6 >    many of them have strayed off the original topic.  G I thought it was obvious because of the nesting, but I'll quote it too. ?  Also some of my messages aren't being nested properlly anyway.   	 AEF said:   I >    Well, yes, I think that in this case it is the SYS$SYSROOT-DIRECTORY K >    anti-synergism. Yeah, I don't like it either. I thought of this before L >    posting, but didn't clearly recall exactly what circumstances it occursB >    in. I didn't think this was one of them, but you are correct.  E >    Anyway, if he had tries my suggestion of adding /FILE to his DIR D >    command, he should then find the same file id for "both" files.  H >   Adding [] or [000000] may fix this problem in this case. I can't tryK >   that right now with an actual tape device, but adding [000000] fixes it 7 >  in a case I just checked where the device is a disk.   G So when I said "Interesting...  Have they fixed this in newer versions? E I'm running 7.1"  I was referring to the problem of two files showing F up in my DIR listing even though there was really only one file on the0 tape.  I'll make sure to quote next time around.   ------------------------------    Date: 15 Aug 2005 13:26:44 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen) . Subject: Re: Help Needed: Tape Backup Save Set3 Message-ID: <GPWkOLuklLUu@eisner.encompasserve.org>   n In article <1124129686.739259.311900@g43g2000cwa.googlegroups.com>, "Chris Allen" <ca.allen@gmail.com> writes:U >>    Fixed what?  You need to quote enough of the message you are responding to that T >>    we know what "this" is.  There have been dozens of messages in this thread and7 >>    many of them have strayed off the original topic.  > I > I thought it was obvious because of the nesting, but I'll quote it too. A >  Also some of my messages aren't being nested properlly anyway.   % Not every newsreader shows "nesting".    ------------------------------  % Date: Mon, 15 Aug 2005 15:20:55 -0400  From: norm.raphael@metso.com. Subject: Re: Help Needed: Tape Backup Save SetQ Message-ID: <OF46199A29.85E0E01B-ON8525705E.006A273C-8525705E.006A4970@metso.com>   H Kilgallen@SpamCop.net (Larry Kilgallen) wrote on 08/15/2005 02:26:44 PM:  E > In article <1124129686.739259.311900@g43g2000cwa.googlegroups.com>, , > "Chris Allen" <ca.allen@gmail.com> writes:D > >>    Fixed what?  You need to quote enough of the message you are > responding to thatF > >>    we know what "this" is.  There have been dozens of messages in > this thread and 9 > >>    many of them have strayed off the original topic.  > > K > > I thought it was obvious because of the nesting, but I'll quote it too. B > >  Also some of my messages aren't being nested properly anyway. > ' > Not every newsreader shows "nesting".   E ..and some read this via e-mail listserver, where no nesting obtains. ' Nothing is as obvious as it looks  ;) .    ------------------------------    Date: 15 Aug 2005 16:48:51 -0700( From: "Chris Allen" <ca.allen@gmail.com>. Subject: Re: Help Needed: Tape Backup Save SetC Message-ID: <1124149731.373735.138880@g47g2000cwa.googlegroups.com>   D One other thing... I'm getting this error everytime I backup.  "DoesC not support specified density - default used"  I'm not specifying a C density in my backup .com file.  HELP/BACKUP says that if it is not F specified then the current density will be used.  However even after ID write a backup with my script I get the error repeatedly even thoughC the default density was used the last time (since it told me it was D using the default density).  My drive is a TZ89, the help suggests IE put in /DENSITY=TK89, which is fine but it also mentions that it must F be paired with the /REWIND qualifier.  What if I want to append to the tape?    ------------------------------  % Date: Mon, 15 Aug 2005 21:20:29 -0400 6 From: Brad Hamilton <brMadAhamPiltSon@coMmcaAstP.neSt>. Subject: Re: Help Needed: Tape Backup Save Set0 Message-ID: <5oqdncHYWZnAopzeRVn-1A@comcast.com>   Chris Allen wrote:F > One other thing... I'm getting this error everytime I backup.  "DoesE > not support specified density - default used"  I'm not specifying a E > density in my backup .com file.  HELP/BACKUP says that if it is not H > specified then the current density will be used.  However even after IF > write a backup with my script I get the error repeatedly even thoughE > the default density was used the last time (since it told me it was F > using the default density).  My drive is a TZ89, the help suggests IG > put in /DENSITY=TK89, which is fine but it also mentions that it must H > be paired with the /REWIND qualifier.  What if I want to append to the > tape?  >   I I looked at the snippet of code that you posted earlier - is it possible  H that "BACK" has been defined (symbol?) as "BACKUP/DENSITY=<mumble>"?  I # realize this is a long shot, but...    --   Bradford J. Hamilton "All opinions are my own" * "Lose the MAPS, and replace '-at-' with @"   ------------------------------    Date: 15 Aug 2005 18:54:26 -0700$ From: "AEF" <spamsink2001@yahoo.com>. Subject: Re: Help Needed: Tape Backup Save SetC Message-ID: <1124157266.399655.212770@g43g2000cwa.googlegroups.com>    Wayne Sewell wrote: ' > >From: "AEF" <spamsink2001@yahoo.com>  > >X-Newsgroups: comp.os.vms1 > >Subject: Re: Help Needed: Tape Backup Save Set # > >Date: 15 Aug 2005 08:59:37 -0700  > >  > >  > >Chris Allen wrote: H > >> Not being stubborn, just being cautious.  As I know next to nothingI > >> about DECNet I fear making a mistake that could result in a security I > >> hole.  The VMS servers here run on a hardened network, and it is top - > >> priority that they are properly secured.  > >  > >  > >Nitpick alert!!!  > >  > >It's spelled DECnet.   :-|  > >  > P > Us lazy sumbitches refuse to expend effort worrying about stuff like that.  Or   THAT'S WE! :-)  O > bothering with the shift key.  I just say decnet.  I think people know what I  > mean.    NITPICK ALERT:   LOOKS ALMOST LIKE DECENT TO ME!   A HEY, I AM SOMETIMES PRETTY LAZY MYSELF AND CAN'T BE BOTHERED WITH F MAKING SURE THE CAPS LOCK PARITY IS CORRECT. i THINK PEOPLE STILL KNOW% WHAT I MEAN. yA KNOW WHAT i MEAN? :-)   D MAKE SURE YOU DON'T MISTYPE NOT FOR NOW OR NOW FOR NOT! i ONCE GOT A, MESSAGE LIKE THAT AND IT WAS VERY CONFUSING!  F THERE'S ALSO THE EXAMPLE WHERE CAESAR SAID "EXECUTE NOT, LIBERATE" BUT9 IT WAS MISTAKENLY TRANSCRIBED AS "EXECUTE, NOT LIBERATE".    END NITPICK ALERT:  F Thanks for your efforts to make everything clear and correct. I shouldF have said that backup/norewind/media=compact will compact every volumeF except the first of a save set (assuming the tape was not mounted withF /med=compact or init-ed similarly) and that backup/rewind will compact all volumes of the save set.  F I would think that for all the effort you went thru to demonstrate theG other point that backup/norewind ALWAYS goes to the logical end-of-tape E marker before writing and that backup/rewind ALWAYS starts writing at D BOT, and your efforts to demonstarte how backup/med=compact works, aC little extra effort to write DECnet instead of decnet would somehow ! fade into oblivion by comparison.   ! OK, THANKS FOR YOUR EFFORTS!  &-)    ------------------------------  % Date: Mon, 15 Aug 2005 20:40:54 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net>. Subject: Re: Help Needed: Tape Backup Save Set+ Message-ID: <43014426.D0CC7F15@comcast.net>    Chris Allen wrote: > J > Interesting...  Have they fixed this in newer versions?  I'm running 7.1  E ...which could (partially) explain your density issue. V7.1 pre-dates  TZ89 by fair stretch of time.    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Mon, 15 Aug 2005 20:53:49 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net>. Subject: Re: Help Needed: Tape Backup Save Set+ Message-ID: <4301472D.152B2F18@comcast.net>    Wayne Sewell wrote:  > 5 > >NNTP-Posting-Date: Sat, 13 Aug 2005 22:51:21 -0500 . > >Message-ID: <42FEBFDA.1A8C10D9@comcast.net>( > >Date: Sat, 13 Aug 2005 22:51:55 -05005 > >From: David J Dachtera <djesys.nospam@comcast.net> ( > >Reply-To: djesysno@spam.earthlink.net > >Organization: DJE Systems > >X-Newsgroups: comp.os.vms1 > >Subject: Re: Help Needed: Tape Backup Save Set 
 > > [snip]< > >When WRITING, BACKUP will start at BOT when first MOUNTed > % > not true without /rewind, see below   ? Under what circumstances would a tape not be at BOT "when first 	 MOUNTed"?    > >or if you use8 > >/REWIND, at the current tape position without /REWIND > 6 > In the above, "current tape position" is ambiguous.   F Well, in the above statment, it is incorrect, as you pointed out. WhenC WRITING without /REWIND, BACKUP will position to logical EOT before  attempting to start writing.  A When READing, "current tape position" means exactly what it says: D "current tape position". If BACKUP does not find tape labels records* where they are expected, it will complain.  C Note that when READing BACKUP expects the tape to be positioned one H record (regardless of whether that's a tape mark or a VOL1 label record) before the HDR labels.   > [snip]K > And in fact, even that is not true.  The help is wrong about the behavior L > during writes.  You always have to use /rewind if you want to write at the? > beginning of the tape, even if you are already sitting there.   A ...unless MOUNT/FOREIGN and BACKUP are preceded immediately by an & INITIALIZE, as is frequently the case.   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Mon, 15 Aug 2005 21:17:59 -0500 ( From: Wayne Sewell <wayne@tachysoft.com>. Subject: Re: Help Needed: Tape Backup Save Set/ Message-ID: <00A48567.46C6B5F1.3@tachysoft.com>   ) >From: "Chris Allen" <ca.allen@gmail.com>  >X-Newsgroups: comp.os.vms/ >Subject: Re: Help Needed: Tape Backup Save Set ! >Date: 15 Aug 2005 11:14:46 -0700 ' >Organization: http://groups.google.com    > U >>    Fixed what?  You need to quote enough of the message you are responding to that T >>    we know what "this" is.  There have been dozens of messages in this thread and7 >>    many of them have strayed off the original topic.  > H >I thought it was obvious because of the nesting, but I'll quote it too.@ > Also some of my messages aren't being nested properlly anyway. >   M I'm not sure what you mean by "nesting".  Not all of us read the newsgroup in M the same way.  In fact, some of us can't use usenet at all and are getting in M via the info-vax mailing list.  So "nesting" information is lost and messages N do not arrive in any particular order.  Every post needs to be self contained.   Wayne O =============================================================================== N Wayne Sewell, Tachyon Software Consulting  (281)812-0738   wayne@tachysoft.com; http://www.tachysoft.com/www/tachyon.html and wayne.html    O =============================================================================== P Jake Blues:"You traded the Caddy for a microphone? ...... Okay, I can buy that."   ------------------------------  % Date: Mon, 15 Aug 2005 23:57:23 -0500 ( From: Wayne Sewell <wayne@tachysoft.com>. Subject: Re: Help Needed: Tape Backup Save Set/ Message-ID: <00A4857D.8B55DDD0.1@tachysoft.com>   & >Date: Mon, 15 Aug 2005 20:53:49 -05003 >From: David J Dachtera <djesys.nospam@comcast.net>  >Organization: DJE Systems/ >Subject: Re: Help Needed: Tape Backup Save Set    >Wayne Sewell wrote: >>  6 >> >From: David J Dachtera <djesys.nospam@comcast.net> >> > [snip] = >> >When WRITING, BACKUP will start at BOT when first MOUNTed  >>  & >> not true without /rewind, see below > @ >Under what circumstances would a tape not be at BOT "when first
 >MOUNTed"?  M You didn't say "tape would be at" the first time, you said "backup will start J at".  Since we were talking about writing, I took it as "backup will startN writing at".  If "will be positioned at" is what you meant, then I retract the
 statement.    M Yes, the tape will be physically positioned at BOT when execution starts, but L *writing* will start at EOT without rewind.  On an initialized tape, EOT and BOT are the same.     	 >> [snip] L >> And in fact, even that is not true.  The help is wrong about the behaviorM >> during writes.  You always have to use /rewind if you want to write at the @ >> beginning of the tape, even if you are already sitting there. > B >...unless MOUNT/FOREIGN and BACKUP are preceded immediately by an' >INITIALIZE, as is frequently the case.    Okay.     6 I still think the help is wrong, though, when it says:  I "If you want to start processing at BOT, and the magnetic tape is already O positioned beyond BOT, specify /REWIND. Otherwise, the magnetic tape begins (or ? resumes) processing from the logical end-of-tape (EOT) marker."   M This indicates that you don't have to specify /rewind if you want to write to M the beginning of the tape and you are already sitting at the beginning of the L tape, as you would be after a fresh mount.  But this would be true *only* ifN the tape has been initialized.  Unfortunately, the above text does not mentionK initialized tapes, implying that it would also happen with populated tapes.   M So based on the above, if I mounted a tape with 50 savesets on it and did not O specify /rewind, I would expect to start writing my saveset at BOT, overwriting O the first of the 50 savesets with a new one and making the others inaccessible.     M I would simply remove the phrase "and the magnetic tape is already positioned % beyond BOT".  This would leave it as:   H "If you want to start processing at BOT, specify /REWIND. Otherwise, theO magnetic tape begins (or resumes) processing from the logical end-of-tape (EOT)  marker."  L This would cover all cases, no matter what the current position of the tape,/ including BOT or EOT and everything in between.   O It would also cover initialized tapes, where EOT and BOT are the same position. K You can use *either* /rewind or /norewind with an initialized tape, and the D only difference is whether backup initializes the tape again or not.O =============================================================================== N Wayne Sewell, Tachyon Software Consulting  (281)812-0738   wayne@tachysoft.com; http://www.tachysoft.com/www/tachyon.html and wayne.html    O =============================================================================== P Jake Blues:"You traded the Caddy for a microphone? ...... Okay, I can buy that."   ------------------------------    Date: 15 Aug 2005 21:58:30 -0700( From: "Chris Allen" <ca.allen@gmail.com>. Subject: Re: Help Needed: Tape Backup Save SetC Message-ID: <1124168310.003562.243330@g44g2000cwa.googlegroups.com>   R >    I'm not sure what you mean by "nesting".  Not all of us read the newsgroup inR >    the same way.  In fact, some of us can't use usenet at all and are getting inR >    via the info-vax mailing list.  So "nesting" information is lost and messagesS >    do not arrive in any particular order.  Every post needs to be self contained.      Fair enough.   ------------------------------    Date: 15 Aug 2005 22:15:24 -0700( From: "Chris Allen" <ca.allen@gmail.com>. Subject: Re: Help Needed: Tape Backup Save SetC Message-ID: <1124169324.585658.110150@g43g2000cwa.googlegroups.com>    Chris Allen wrote:K >> Interesting...  Have they fixed this in newer versions?  I'm running 7.1    David J Dachtera wrote: F >...which could (partially) explain your density issue. V7.1 pre-dates > TZ89 by fair stretch of time.   ; Maybe that's my problem.  When I checked the online help on E BACKUP/DENSITY it suggested using /DENSITY=TK89 however I was looking F at the help on v7.2.  My work is too freakin' cheap to buy another VAX? computer and v7.1 license for testing (currently all of our VAX E machines are in full time use) so I had to get a hobbyist license and B installed it in SIMH on FreeBSD so I could learn.  However it is aG different version and I don't have any "real" hardware connected to it.    ------------------------------    Date: 15 Aug 2005 22:21:59 -0700( From: "Chris Allen" <ca.allen@gmail.com>. Subject: Re: Help Needed: Tape Backup Save SetC Message-ID: <1124169719.136563.304980@o13g2000cwo.googlegroups.com>    Brad Hamilton wrote: > J > I looked at the snippet of code that you posted earlier - is it possibleI > that "BACK" has been defined (symbol?) as "BACKUP/DENSITY=<mumble>"?  I % > realize this is a long shot, but...     F I doubt it but I'll check tomorrow and let you know.  Good suggestion. You never know right?    ------------------------------  % Date: Mon, 15 Aug 2005 20:56:42 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net>  Subject: Re: Image restore fails+ Message-ID: <430147D9.84E0C44C@comcast.net>    Peter Sjoberg wrote: > = > On Fri, 12 Aug 2005 22:25:14 -0500, David J Dachtera wrote:  >  > > Peter Sjoberg wrote: > >> [snip] O > >> The system I'm trying to restore is VMS 6.x while the lab system I'm doing I > >> it on is 7.3-1. I dn't have a VMS 6 cd anywhere here but on the real - > >> system it was used with the same result.  > >  > > AH! That explains a lot! > > L > > There is a significant change in BACKUP between V6.2 and V7.x that gives > > rise to this issue.  > > J > > If you have a V6.2 CD, boot it up and try the restore again. Should do > > better.  > I seen that,D > http://www3.sympatico.ca/n.rieck/docs/openvms_72_backup_bug.htm is5 > basically what I see but in my case it's all Alpha. K > The hw that has the problem is an AlphaServer 1000A which require 6.2-1H3 K > or later. We could not find a cd with that version and booted up on a 7.2 E > cd (Tried a 6.2 but it failed) and done some of the tests from 7.2.   6 E-mail me privately and I can probably help you out...  - How to demung the reply-to should be obvious.    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  + Date: Mon, 15 Aug 2005 20:48:17 +0000 (UTC) % From: Dan Foster <usenet@evilphb.org> < Subject: LDDRIVER original developer (was Re: SAMBA for VMS)5 Message-ID: <slrndg1vtj.pfq.usenet@zappy.catbert.org>   ; In article <1ZednZqwgfTbNp3eRVn-rA@rcn.net>, Glenn Everhart  <Everhart@gce.com> wrote: A > Thanks for the comment, but LDdriver was not one of mine. I did F > VDdriver and some others, but LDdriver was done internally at DEC byA > Ton D. (sorry, I forget the spelling of his last name). The old F > RSX11M/M+ VDdriver was Ralph Stamerjohn's thing, though I and others > did various tweaks.   G My sincerest apologies to the original developer -- intent was *NOT* to  mis-credit the developer.   K And a thank-you to Mr. Everhart for setting the record straight. Mea culpa.   H I should note that from a previous HP OpenVMS Technical Journal article,F it states the original developer was reported to have been Adrie SweepA from the Netherlands, and originally written for VAX/VMS in 1985.   P http://h71000.www7.hp.com/openvms/journal/v6/disk_partitioning_with_lddriver.pdf  G I am not sure how to reconcile this with Mr. Everhart's recollection of 8 Ton D. having done this version internally at DEC.. hmm.   -Dan   ------------------------------    Date: 15 Aug 2005 12:49:17 -0700" From: dave.baxter@bannerhealth.com5 Subject: Print Queue in "starting" state  --  cause?? C Message-ID: <1124135357.887396.182670@o13g2000cwo.googlegroups.com>   F      Although I have seen this every now and then, I have never really: understood the cause.     I have a print queue (TELNETSYM)C directed to <NODE>::<p_server>:9100 which has just been created and # which is having a problem starting.   <      Looking at the queue from a different node, it shows as "starting".   C      The queue is being created by a process on a different cluster C using the TCPIP$REXEC process.    The process has been successfully A used through several VMS and TCPIP upgrades for more than 3 years D without this problem.    Right now, the parent process is hanging up7 because the queue on the remote cluster will not start.   G      The only thing which has changed is that I recently enabled all of C the print queues on this cluster for "autostart".   However the new C queues are not init'd "/autostart" (because I haven't got around to  modifying the script yet.   B Q.   What is the actual cause of the "starting" status.    Will it eventually time-out???   Dave.    ------------------------------  # Date: Mon, 15 Aug 2005 21:53:02 GMT   From: John Santos <john@egh.com>9 Subject: Re: Print Queue in "starting" state  --  cause?? * Message-ID: <298Me.4253$%K4.1070@trnddc09>  # dave.baxter@bannerhealth.com wrote: H >      Although I have seen this every now and then, I have never really< > understood the cause.     I have a print queue (TELNETSYM)E > directed to <NODE>::<p_server>:9100 which has just been created and % > which is having a problem starting.  > > >      Looking at the queue from a different node, it shows as
 > "starting".  > E >      The queue is being created by a process on a different cluster E > using the TCPIP$REXEC process.    The process has been successfully C > used through several VMS and TCPIP upgrades for more than 3 years F > without this problem.    Right now, the parent process is hanging up9 > because the queue on the remote cluster will not start.  > I >      The only thing which has changed is that I recently enabled all of E > the print queues on this cluster for "autostart".   However the new E > queues are not init'd "/autostart" (because I haven't got around to  > modifying the script yet.  >   C This is purely a guess, but since no one else has responded yet :-)   C Are you sure the queues aren't trying to start befoe TCPIP is fully ; up?  I.E. is your "$ start/queue/manager" too early in your  systartup_vms.com?  7 Added info, on checking my own systems:  It appears the 8 "$ start/queue/manager" command has disappeared from the< template file, so presumably is no longer required. However,= it seems to start up TCPIP ($ @SYS$STARTUP:TCPIP$STARTUP.COM) 9 after all the queue starting stuff, so maybe autostart on " network printer queues is a no-no?  D > Q.   What is the actual cause of the "starting" status.    Will it > eventually time-out??? >  > Dave.  >      --   John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  % Date: Mon, 15 Aug 2005 17:56:31 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 9 Subject: Re: Print Queue in "starting" state  --  cause?? , Message-ID: <43010F89.2D43B855@teksavvy.com>  # dave.baxter@bannerhealth.com wrote: I >      The only thing which has changed is that I recently enabled all of E > the print queues on this cluster for "autostart".   However the new E > queues are not init'd "/autostart" (because I haven't got around to  > modifying the script yet.   E If the queues are started prior to the TCPIP stack being sufficiently @ up, the symbiont may lock up because it can't initialise itself.   ------------------------------  % Date: Mon, 15 Aug 2005 21:13:38 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net>9 Subject: Re: Print Queue in "starting" state  --  cause?? + Message-ID: <43014BD2.B4DAAAC2@comcast.net>    John Santos wrote: > % > dave.baxter@bannerhealth.com wrote: J > >      Although I have seen this every now and then, I have never really> > > understood the cause.     I have a print queue (TELNETSYM)G > > directed to <NODE>::<p_server>:9100 which has just been created and ' > > which is having a problem starting.  > > @ > >      Looking at the queue from a different node, it shows as > > "starting".  > > G > >      The queue is being created by a process on a different cluster G > > using the TCPIP$REXEC process.    The process has been successfully E > > used through several VMS and TCPIP upgrades for more than 3 years H > > without this problem.    Right now, the parent process is hanging up; > > because the queue on the remote cluster will not start.  > > K > >      The only thing which has changed is that I recently enabled all of G > > the print queues on this cluster for "autostart".   However the new G > > queues are not init'd "/autostart" (because I haven't got around to  > > modifying the script yet.  > >  > E > This is purely a guess, but since no one else has responded yet :-)  > E > Are you sure the queues aren't trying to start befoe TCPIP is fully = > up?  I.E. is your "$ start/queue/manager" too early in your  > systartup_vms.com? > 9 > Added info, on checking my own systems:  It appears the : > "$ start/queue/manager" command has disappeared from the> > template file, so presumably is no longer required. However,? > it seems to start up TCPIP ($ @SYS$STARTUP:TCPIP$STARTUP.COM) ; > after all the queue starting stuff, so maybe autostart on $ > network printer queues is a no-no?  F At some point, not sure when, this was added into the startup sequence outside of SYSTARTUP_VMS.   G I was kinda hoping someone inside HP/OVMS/TCPIP Engr. would pipe up and @ explain how to deal with this (queue manager starting before the environment is ready for that).   A Then again, you couldn't do what LPD$STARTUP needs to do if queue " manager (at least) wasn't running.   Hhmm... A puzzlement...    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------    Date: 15 Aug 2005 20:09:21 -0700$ From: "AEF" <spamsink2001@yahoo.com>7 Subject: Re: Print Queue in "starting" state -- cause?? C Message-ID: <1124161761.150003.114620@g44g2000cwa.googlegroups.com>    David J Dachtera wrote:  > John Santos wrote: > > ' > > dave.baxter@bannerhealth.com wrote: L > > >      Although I have seen this every now and then, I have never really@ > > > understood the cause.     I have a print queue (TELNETSYM)I > > > directed to <NODE>::<p_server>:9100 which has just been created and ) > > > which is having a problem starting.  > > > B > > >      Looking at the queue from a different node, it shows as > > > "starting".  > > > I > > >      The queue is being created by a process on a different cluster I > > > using the TCPIP$REXEC process.    The process has been successfully G > > > used through several VMS and TCPIP upgrades for more than 3 years J > > > without this problem.    Right now, the parent process is hanging up= > > > because the queue on the remote cluster will not start.  > > > M > > >      The only thing which has changed is that I recently enabled all of I > > > the print queues on this cluster for "autostart".   However the new I > > > queues are not init'd "/autostart" (because I haven't got around to  > > > modifying the script yet.  > > >  > > G > > This is purely a guess, but since no one else has responded yet :-)  > > G > > Are you sure the queues aren't trying to start befoe TCPIP is fully ? > > up?  I.E. is your "$ start/queue/manager" too early in your  > > systartup_vms.com? > > ; > > Added info, on checking my own systems:  It appears the < > > "$ start/queue/manager" command has disappeared from the@ > > template file, so presumably is no longer required. However,A > > it seems to start up TCPIP ($ @SYS$STARTUP:TCPIP$STARTUP.COM) = > > after all the queue starting stuff, so maybe autostart on & > > network printer queues is a no-no? > H > At some point, not sure when, this was added into the startup sequence > outside of SYSTARTUP_VMS.  > I > I was kinda hoping someone inside HP/OVMS/TCPIP Engr. would pipe up and B > explain how to deal with this (queue manager starting before the! > environment is ready for that).     C Ah, yes, but the queue manager starting is not the same as starting C your queues. But I do not know if that makes a difference for this.   E The queue manager as of approx. VMS 6.0, 6.1, or so is started by the > JOB_CONTROL process, which happens before SYSTARTUP_VMS.COM is9 executed. I think it does this after STARTUP.COM executes G SYLOGICALS.COM because that is where you put your queue manager logical  names.  D Maybe if the OP just finishes his autostart assignments, the problemA will go away. Maybe he starts his printer queues before he starts D TCP/IP and that's the problem. But then shouldn't starting change to, ready (or idle, whatever) once TCP/IP is up?  8 This from the system management manual might be of help:  G The job controller automatically starts the queue manager during reboot G unless you enter a STOP/QUEUE/MANAGER/CLUSTER command. For this reason, B including START/QUEUE/MANAGER in your startup command procedure is unnecessary.  E You could stop the queman in syshutdwn.com, and start it after TCP/IP 5 in systartup_vms.com, but what it the system crashes!   ) 'Sorry I can't be of more help than this.     C > Then again, you couldn't do what LPD$STARTUP needs to do if queue $ > manager (at least) wasn't running. >  > Hhmm... A puzzlement...      Which calls for a solutionment.    ------------------------------  # Date: Tue, 16 Aug 2005 02:12:07 GMT L From: winston@SSRL.SLAC.STANFORD.EDU (Alan Winston - SSRL Central Computing)M Subject: Re: Problems with updating firmware on SDLT1 drives using LTT on VMS 6 Message-ID: <00A48555.B161E988@SSRL.SLAC.STANFORD.EDU>  p In article <1124092891.022908.126710@f14g2000cwb.googlegroups.com>, "MDPlatts" <martin.platts@cdl.co.uk> writes:  G >I just download the firmware file (*.FRM) from the following URL, pick G >your tape drive and then any of the individual vartieties and then any D >really of the operating systems (windows usually is more up to dateE >than OpenVMS) from the pages after that - then put the FRM file into 5 >the FIRMWARE directory created when you install LTT.  >   l >http://h20000.www2.hp.com/bizsupport/TechSupport/Product.jsp?prodTypeId=12169&prodCatId=304613&locale=en_US  L Thank you!  This worked.  (Somehow I previously couldn't see the independentH firmware downloads, and thought it was supposed to be bundled with LTT.)   -- Alan    ------------------------------  % Date: Mon, 15 Aug 2005 11:17:58 -0700 , From: Ken Fairfield <my.full.name@intel.com>T Subject: Re: Problems with updating firmware on SDLT1 drives using LTT on VMS VMSVMS+ Message-ID: <ddqm8m$bic$1@news01.intel.com>   , Alan Winston - SSRL Central Computing wrote: > VMSers --  > K > I've got an MSL5026 tape library attached by SCSI to my DS20E, which runs P > VMS 7.3-2 at present.  I inherited the library and don't have docs, managementQ > CD, etc.  I was able, finally, to find the current library firmware and reflash 0 > the library.  Ths library has two tape drives: > 4 > 1 COMPAQ MSL5000 Series (Address: 1.3.0[1-GKA300])A >    2   Drive 1:COMPAQ SuperDLT1 (Address: 1.1.0[1-SSRL$MKA100]) A >    3   Drive 2:COMPAQ SuperDLT1 (Address: 1.2.0[1-SSRL$MKA200]) E >                                                                      > N > One of the drives is at firmware v82, the other at firmware V45.  That's theK > one that occasionally refuses to let go of a tape when the robot tries to P > collect it.  (This is usually Friday night, so that the Saturday image backups > don't really work.)  > 2 > I'd like to upgrade the firmware on the Drive 1. > Q > Cruising the HP site for firmware, I find that all linkns lead to a new version O > of LTT, which I've installed.  (I note that they still have a .PCSI download, J > rather than a compressed file, and the the record format on the PCSI are8 > screwed up so you have to fix it before installation.) > N > However, LTT claims it doesn't have any firmware images for this tape.  ("No( > matching file" is the actual message.)  4     Been there, done that, called Field Service. :-(  F     Our local FE pointed me to the download for LTT.  I spent a lot ofE cycles getting it to work on an ES-40 with an attached ELS-9000 class  library (DLT8000 drives).   F     The problem of "no matching file" was solved by struggling throughE HP's web site until I found a kit (some kits?) with up to date FW for B these drives, downloading the .ZIP file, unZIP'ing it, and copyingF the resulting files into SYS$SYSDEVICE:[VMS$COMMON.OPT.LTT.FIRMWARE] .< (I think they're the .FRM files, but don't know for sure...)  A     After doing all this, and running the LTT utility (VERY UGLY  < INTERFACE(!); wants a VT100 and feels like it's written with? curses. :-(), and while I could _query_ the tape drives' to see 4 their FW level, the update failed.  <spit! disgust!>  C     Our FE updated the firmware in these drives from his laptop via C the serial connection to the library.  His comment was that LTT was A designed for Windows and he wasn't really sure how well it worked  on other OS's.  M > Is this (another) packaging error in VMS LTT or is something else going on?  > Q > Where can I get firmware for this tape?  What should the file be called so that O > LTT will recognize it?  Will current firmware fix my intermittent drive fetch ! > problem?  And what about Naomi?   D     If you're determined to pursue this yourself, contact me offlineB and I'll try to dig out the URL for the FW files. My advice: don't waste any more of your time...  
 	Regards, Ken  --  6 I don't speak for Intel, Intel doesn't speak for me...  
 Ken Fairfield ! D1C Automation VMS System Support " who:   kenneth dot h dot fairfield where: intel dot com   ------------------------------  % Date: Mon, 15 Aug 2005 21:02:54 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net> Subject: Re: SAMBA for VMS+ Message-ID: <4301494D.76D8EFC2@comcast.net>    Larry Kilgallen wrote: > [snip]G > People should understand that not everybody is allow to use Freeware.   F So you're telling me that there is a business opportunity out there toE sell "sensitive sites" the same things they can get at no cost to the $ taxpayer through the usual channels?  $ Sounds about right for gov't work...   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Mon, 15 Aug 2005 21:04:16 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net> Subject: Re: SAMBA for VMS+ Message-ID: <430149A0.64F1775E@comcast.net>     Peter 'EPLAN' LANGSTOEGER wrote: > e > In article <S$w4BegPtECc@eisner.encompasserve.org>, Kilgallen@SpamCop.net (Larry Kilgallen) writes: P > >> Look for VMS freeware LD V8 to get the .ZIP file with the .HLB and the .CLD > > J > >So even given the freeware, it is not sufficient to install the command' > >file, you also need to install ZIP ?  > + > No, my fault. LD V8 is already a PCSI kit   B I believe there should also be a .PCSI$COMPRESSED kit (transfer as( binary, no need to SET FILE/ATTRIBUTES).   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Mon, 15 Aug 2005 21:06:58 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net> Subject: Re: SAMBA for VMS+ Message-ID: <43014A42.49B29DD5@comcast.net>    "Stanley F. Quayle" wrote: > 2 > On 13 Aug 2005 at 23:17, David J Dachtera wrote:G > > Having been unsupported freeware for some years now, LD is about to  > > become supported!  > E > Before it becomes supported, can the device type be changed so that D > the virtual disks come up as "D" something?  To see the disks on aA > system, I do a "SHOW DEVICE D", and this command will miss them  > all...  ? You may want it to miss them. LD CONNECT/LBN requires that the  H underlying physical disk not be MOUNTed. So, this sequence would pick up what you want to see:   
 $ SH DEV D/MO  $ SH DEV LD    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Mon, 15 Aug 2005 21:09:05 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net> Subject: Re: SAMBA for VMS+ Message-ID: <43014AC1.AEB4C844@comcast.net>    "Michael D. Ober" wrote: > - > http://www.pi-net.dyndns.org/anonymous/jyc/  > M > Based on the Samba 2.2.8 source.  Versions for Alpha and VAX.  It's best if F > you compile it from the source, a-la Unix.  VMS 7.3 has the required; > compilers and linkers as part of the system distribution.   A The C compiler now ships bundled with VMS??!! ...since V7.3???!!!   " How on earth did I miss that???!!!   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Mon, 15 Aug 2005 15:33:38 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> @ Subject: Re: TCPIP Services: SMTP bug/wrong logic with 450 codes* Message-ID: <4300EE0A.E84E00@teksavvy.com>   Mike Rechtman wrote:% > Sorry, missed the "VAX" in the O.P. I > If you have support (or if you know of someone who has, and who has the I > same problem) perhaps you should get a request for back-porting the fix  > into the system.    E Thing is that this shows that the SMTP software that comes with TCPIP F services is a poor implementation. The standards have long stated thatE 400 codes were temporary glitches. The software itself writes part of C the log stating it will requeue the message but in the end, it hard A bounces it sending it back to the user with the wrong error code.   D I realise that HP doesn'.t even have the trademark "VAX" anymore and they don't care.    G Thing is that more and more, VMS falls behind and platforms such as the F MAC are becoming more attractive simply because they are more complete1 and have better quality TCPIP applications on it.   A If the VMS management were to release the documentation on direct A interfaces to the SMTP symbiont, It would then become possible to F gradually replace the standard flawed software with stuff list postfixF (for instance, implementing the receiver portion first, and then doingD the sender). Short of that doc, one has to fully re-invent the wheelE completely (unless you are willing to live with performance issues of F having to write a email to dick 3 times (receiving it, then formattingF it for the SFF routines which then take that content and format it for the symbiont).   ------------------------------   Date: 15 Aug 2005 18:10:59 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)( Subject: The Educational License Program, Message-ID: <3mc45jF16c3d9U1@individual.net>   Sue,A   Now that you seem to have taken over the EDU Program I hope you # don't mind if I ask you a question.   B   The EDU Licenses all expire on 31 Aug.  Will the new licenses be@ available before the old ones expire?  That is about 8 days into? the new semester and a real bad time to have the students loose  access to the machine.   bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------   End of INFO-VAX 2005.455 ************************                                                                                                                                                                                                                                                                                                                              f7͖A I;8]EF%@IUND⧢3M&tJ
\1%.+Ą "|=hPD
fbA[pn[KHzĀLgVkE<+ĀUW	+)bb?KǨX7r`$k
JN\AoʻXK77pzC7e,_|e|sdj2
f+5w=Q9뮩f kz5DO)]H~ƺI
Z,ZY=W<d:gEMDuH	vfs"wLڥtK;jyW`tH}_
a%meXg"nbđ9V8h"8olVQ:SB}ugUt^xNa~7Rk&SXY·R뗅sNg[MTJv"ZwyFC3֍3WB50z_{*k¹l