1 INFO-VAX	Mon, 31 Jul 2006	Volume 2006 : Issue 423       Contents: 8400/140 cpu wierdness Re: 8400/140 cpu wierdness Re: 8400/140 cpu wierdness Re: An opportunity for VMS( Re: Announcing Availability Manager V2.6( Re: Announcing Availability Manager V2.6( Re: Announcing Availability Manager V2.6 BACKUP weirdness Re: BACKUP weirdness Re: BACKUP weirdness Re: BACKUP weirdness Re: BACKUP weirdness Re: BACKUP weirdness Re: BACKUP weirdness Re: BACKUP weirdness Re: BACKUP weirdness8 Is there a Unix /tmp directory. How dissimilar are they.< Re: Is there a Unix /tmp directory. How dissimilar are they.< Re: Is there a Unix /tmp directory. How dissimilar are they.< Re: Is there a Unix /tmp directory. How dissimilar are they./ Re: page_setup and a signature 'font' on a dimm  ra3000/hsz22 unix search list logicals ??  Re: unix search list logicals ??  Re: unix search list logicals ??  Re: unix search list logicals ?? Re: V8.2 is out  Re: V8.2 is out  [LD] V8.2 is out  F ----------------------------------------------------------------------    Date: 31 Jul 2006 08:13:00 -0700 From: anicker_j@yahoo.com  Subject: 8400/140 cpu wierdness B Message-ID: <1154358780.149012.16680@b28g2000cwb.googlegroups.com>  D I'm trying to move 2 alpha 8400's from one location to another.  The@ idea is to not physically move the machines but to have chassis'; already at the new location and just move cpu's and memory.   G I tested moving a couple cpu's this weekend and found a strange result. G  One of the cpu's would not post in the front (slots 0-3) of one of the C 8400's.  It would, however, post if it was in one of the rear slots E (4-7).  It would not post even when by itself  in slot 0.  The second ; cpu board I used had no issues.  The output of the boot was B unintelligable garbage characters so I don't have a specific errorF message to work with.  The hardware rev on the label of the two boards0 was c06 and the firware is the same level, 1.96.  F The cpu board is a 6/525 (which I think technically makes it a gs140).= Does anyone have any ideas why this board might be a problem?   C I wasn't thinking that moving cpu's from one server to another like ? server would be a problem and so testing every single board for F compatibility wasn't on my to do list.  However, at this point I think it might be necessary.     Thanks,  Jeff   ------------------------------  # Date: Mon, 31 Jul 2006 16:05:29 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com># Subject: Re: 8400/140 cpu wierdness 1 Message-ID: <dTpzg.1308$5L6.615@news.cpqcorp.net>    anicker_j@yahoo.com wrote:F > I'm trying to move 2 alpha 8400's from one location to another.  TheB > idea is to not physically move the machines but to have chassis'= > already at the new location and just move cpu's and memory.   I    I can understand why you don't want to haul around all that cabinetry.   H    I'll assume that the target series platform has rather less than the I 6/525 you are seeking to transplant into the target box; that this is as  @ much a CPU upgrade as a migration.  Implicit in this transplant I operation is that the target box has hardware and firmware revisions for  / some unspecified and probably slower processor.   H > The cpu board is a 6/525 (which I think technically makes it a gs140).? > Does anyone have any ideas why this board might be a problem?   I    The 6/525 was an available option on the AlphaServer 8400 series, and    on the AlphaServer GS140 series.  I    There are various module revision requirements throughout the system;  E swapping processors around (in isolation) isn't necessarily going to  C work.  I don't have the full list of these module revisions handy,  I that's something that the services folks generally track.  You also need  G to ensure the bus clock is matched to the processor -- if those aren't  H matched up, all manner of weirdness ensues, and you also need to ensure D you have the terminators in the right slots.  (The AlphaServer 8400 B series service manual goes into some detail on this configuration G effort, it's rather more involved than just swapping processor modules   around.)  1    Here are the available documents for this box:   A http://h18002.www1.hp.com/alphaserver/archive/8400/8x00_tech.html   G    The other obvious approach is to look at newer and smaller boxes --  I various of the newer (and not necessarily even "new") Alpha or Integrity  B boxes around may be better choices than would preserving an older E AlphaServer 8400 series box -- this in terms of cooling and/or power  H and/or performance.  (The platform itself dates back to 1995 or so, and E there have obviously been various improvements since.)  I might well  G expect an Integrity rx2620 box to run as well as this AlphaServer box,  I if not faster -- a much older Integrity rx2600 holds nicely even with an  F AlphaStation EV6 box, in my own experience, and disks have gotten far  smaller and far faster, too.   ------------------------------    Date: 31 Jul 2006 10:21:38 -0700 From: etmsreec@yahoo.co.uk# Subject: Re: 8400/140 cpu wierdness B Message-ID: <1154366498.594369.36220@m79g2000cwm.googlegroups.com>  F We had two 8400s that we upgraded to 5/625 processors in 1999 with the@ proceeds of selling a VAX 7850 (=A350k for the VAX was more than enough!)  F One of the 8400s had a 440MHz cpu and the other a 300MHz if I rememberF rightly.  One (the 440MHz) was able to be upgraded direct to the 5/625: but the other had to have a new clock board in it as well.  G One version of the firmware that was released in around H2CY2000 gave a F great crash when the 8400 passed control from VMS back to the console.D Only option was power it off and power back on again, but I digress.  D It seems (from the quickspecs) that it was the EV6 that decided that+ the system was a GS140 rather than an 8400.    Steve    anicker_j@yahoo.com wrote:F > I'm trying to move 2 alpha 8400's from one location to another.  TheB > idea is to not physically move the machines but to have chassis'= > already at the new location and just move cpu's and memory.  > I > I tested moving a couple cpu's this weekend and found a strange result. I >  One of the cpu's would not post in the front (slots 0-3) of one of the E > 8400's.  It would, however, post if it was in one of the rear slots G > (4-7).  It would not post even when by itself  in slot 0.  The second = > cpu board I used had no issues.  The output of the boot was D > unintelligable garbage characters so I don't have a specific errorH > message to work with.  The hardware rev on the label of the two boards2 > was c06 and the firware is the same level, 1.96. > H > The cpu board is a 6/525 (which I think technically makes it a gs140).? > Does anyone have any ideas why this board might be a problem?  > E > I wasn't thinking that moving cpu's from one server to another like A > server would be a problem and so testing every single board for H > compatibility wasn't on my to do list.  However, at this point I think > it might be necessary. =20 >=20	 > Thanks,  > Jeff   ------------------------------  + Date: Mon, 31 Jul 2006 10:33:59 +0000 (UTC)  From: david20@alpha2.mdx.ac.uk# Subject: Re: An opportunity for VMS , Message-ID: <eakman$1ni$1@south.jnrs.ja.net>  j In article <1154311242.411700.219630@i42g2000cwa.googlegroups.com>, "AEF" <spamsink2001@yahoo.com> writes: >  >Bob Koehler wrote: m >> In article <1154052852.556761.243320@b28g2000cwb.googlegroups.com>, "AEF" <spamsink2001@yahoo.com> writes:  >>? >> > Something that's worth the price of going to space to get.  >>F >>    Worth it to who?  I know folks for whom the entire return of theD >>    space effort going back to pre-NASA days isn't worth one cent. > A >Well, you snipped it out but my comment above was in response to B >obtaining resources from the Solar System. I assume that would be@ >mostly minerals and such. Well, what I meant was, is there someH >substance that would be cheaper to mine from asteroids than from Earth?/ >We're talking economics of raw materials here.  >   F Chicken and egg problem. Pretty much any resource in space is probablyH uneconomic at present because we haven't got the facilities out there to economically mine it.   K There are certainly things which are common out in space but rare on earth. L Two things that come to mind are iridium (best known as the signature of theL impact which killed the Dinosaurs) and Helium-3 (which is very rare on EarthL but is suspected to be available in sufficient quantities - deposited by the3 solar wind - on the moon for mining to be feasible. O It has been stated that one of the long term goals of the Chinese lunar program  is mining of lunar helium-3 see   . http://en.wikipedia.org/wiki/Chang%27e_program  I (Though at the moment there probably isn't a need for large quantities of C Helium-3 since it's main application would be in fusion reactions).         
 David Webb Security team leader CCSS Middlesex University         >>E >>    And I know folks who feel otherwise.  But the couple of dollars E >>    it has cost each American taxpayer each year will no longer buy  >>    them lunch at Mickey D's.  > > >NASA's budget is only a few hundred million dollars per year? >  >AEF >    ------------------------------    Date: 31 Jul 2006 05:54:13 -07001 From: "Bart.Zorn@gmail.com" <Bart.Zorn@gmail.com> 1 Subject: Re: Announcing Availability Manager V2.6 B Message-ID: <1154350453.867032.86960@p79g2000cwp.googlegroups.com>   Barry Kierstein wrote:G > The Availability Manager team is pleased to announce the Availability K > Manager Version 2.6.  This version includes updates to both Data Analyzer  > and Data Collector kits. > M > New features in the Availability Manager Version 2.6 include the following:  > < >     -  Support for OpenVMS V8.3, including 64 CPU support. > < >     -  System Overview window redone to look like DECamds. > K >     -  Additional Group Overview window and Single Group window for sites  >        with many groups. > B >     -  New Single Process views to view all information at once. > F >     -  New events added to detect high CPU usage on the primary CPU. >  > D > Problems corrected in Availability Manager Version 2.6 include the > following: > B >     -  Disk Status and Disk Volume filtering problems corrected. > J >     -  Disk free space collection corrected, occasionally reported stale	 > values.  > G >     -  Single process windows fixes - fixed hangs in data collection.  >  > L > The Availability Manager kits can be obtained from the following web site: > 8 >        www.hp.com/products/openvms/availabilitymanager >  > K > Thank you for using our products.  Let us know if you have any questions.  >  > The Availability Manager Team  > OpenVMS Engineering   E I am a bit surprised to see this announcement here in cov, but not on / the What's new page from HP's OpenVMS homepage!    What is going on?    Bart   ------------------------------    Date: 31 Jul 2006 06:32:06 -0700  From: "Ian Miller" <ijm@uk2.net>1 Subject: Re: Announcing Availability Manager V2.6 B Message-ID: <1154352726.711752.94470@s13g2000cwa.googlegroups.com>  D I think its easier to post an announcement here than to jump through hoops at hp to get the web site updated.    ------------------------------  % Date: Mon, 31 Jul 2006 19:03:45 +0400 N From: "Ruslan R. Laishev" <zzLaishev@zzDeltaTelecom.RU-remove.all-zz-to-reply>1 Subject: Re: Announcing Availability Manager V2.6 ? Message-ID: <95A3157F85405D1444D229D8127E1C25@NNTP.DeltaTel.RU>    Mark Daniel wrote:   > Ruslan R. Laishev wrote: >  >> Barry Kierstein wrote:  >>I >>> The Availability Manager team is pleased to announce the Availability E >>> Manager Version 2.6.  This version includes updates to both Data   >>> Analyzer >>> and Data Collector kits. >> >> >>& >>     System tools on Java ?! Amen... >  >  > You mean RIP?    Rest In Peae? Yes! :-)    --  F + WBR, OpenVMS [Sys|Net] HardWorker ............. Skype: SysMan-One  +9 Delta Telecom JSC, IMT-MC-450(CDMA2000) cellular operator E Russia,191119,St.Petersburg,Transportny per. 3 Cel: +7 (812) 716-3222 F +http://starlet.deltatelecom.ru ............. Frying on OpenVMS only +   ------------------------------    Date: 31 Jul 2006 05:10:06 -0700 From: sampsal@gmail.com  Subject: BACKUP weirdness C Message-ID: <1154347806.038256.238680@i42g2000cwa.googlegroups.com>   A I recently backed up my system drive using the following command:   ;       BACKUP DRA0:[000000...] DRA2:[000000]FULL.BCK/SAVESET   F (I KNOW I should've used /IMAGE, but unfortunately I was in a rush and didn't :( )   D Anyway, if I try to restore the saveset (when booted up from the VMS! install CD) using a command like:   (       BACKUP DRA2:FULL.BCK/SAVESET DRA0:  G then BACKUP just dumps all the files in the Master File Directory. If I B do a BACKUP/LIST on the FULL.BCK saveset, it show that the correct* directory structures are in fact in place.  A Can someone tell me how to restore these files into their correct 
 locations?   Sampsa   ------------------------------  % Date: Mon, 31 Jul 2006 14:32:33 +0200 + From: Martin Vorlaender <mv@pdv-systeme.de>  Subject: Re: BACKUP weirdness + Message-ID: <4j6bj0F6ftnrU1@individual.net>    sampsal@gmail.com wrote:C > I recently backed up my system drive using the following command:  > = >       BACKUP DRA0:[000000...] DRA2:[000000]FULL.BCK/SAVESET  > H > (I KNOW I should've used /IMAGE, but unfortunately I was in a rush and
 > didn't :( )  > F > Anyway, if I try to restore the saveset (when booted up from the VMS# > install CD) using a command like:  > * >       BACKUP DRA2:FULL.BCK/SAVESET DRA0: > I > then BACKUP just dumps all the files in the Master File Directory. If I D > do a BACKUP/LIST on the FULL.BCK saveset, it show that the correct, > directory structures are in fact in place. > C > Can someone tell me how to restore these files into their correct  > locations?  C BACKUP DRA2:[000000]FULL.BCK/SAVESET DRA0:[*...] /BY_OWNER=ORIGINAL    cu, 	    Martin  --  D One OS to rule them all       | Martin Vorlaender  |  OpenVMS rules!7 One OS to find them           | work: mv@pdv-systeme.de H One OS to bring them all      | http://www.pdv-systeme.de/users/martinv/> And in the Darkness bind them.| home: martin@radiogaga.harz.de   ------------------------------    Date: 31 Jul 2006 05:44:58 -07001 From: "Bart.Zorn@gmail.com" <Bart.Zorn@gmail.com>  Subject: Re: BACKUP weirdness B Message-ID: <1154349898.567542.11870@m73g2000cwd.googlegroups.com>   sampsal@gmail.com wrote:C > I recently backed up my system drive using the following command:  > = >       BACKUP DRA0:[000000...] DRA2:[000000]FULL.BCK/SAVESET  > H > (I KNOW I should've used /IMAGE, but unfortunately I was in a rush and
 > didn't :( )  > F > Anyway, if I try to restore the saveset (when booted up from the VMS# > install CD) using a command like:  > * >       BACKUP DRA2:FULL.BCK/SAVESET DRA0: > I > then BACKUP just dumps all the files in the Master File Directory. If I D > do a BACKUP/LIST on the FULL.BCK saveset, it show that the correct, > directory structures are in fact in place. > C > Can someone tell me how to restore these files into their correct  > locations? >  > Sampsa  D You give the most important part of the answer yourself already: you left out /IMAGE   F You try to restore a non-image backup as if it was an image backup and( that gives the result that you describe.  @ Assuming that the original disk was NOT the system disk, you can% restore the saveset with the command:   @     BACKUP DRA2:FULL.BCK/SAVESET  DRA0:[*...]/NEW/OWNER=ORIGINAL  , If it was a systemdisk, you are out of luck!   Regards,   Bart   ------------------------------    Date: 31 Jul 2006 05:56:46 -0700 From: sampsal@gmail.com  Subject: Re: BACKUP weirdness C Message-ID: <1154350606.257580.100800@p79g2000cwp.googlegroups.com>   F What if I just do the WRITEBOOT, and then do an "upgrade" installation1 from CD? Would that repair the VMS$COMMON issues?     Peter 'EPLAN' LANGSTOEGER wrote:_ > In article <1154347806.038256.238680@i42g2000cwa.googlegroups.com>, sampsal@gmail.com writes: D > >I recently backed up my system drive using the following command: > > > > >      BACKUP DRA0:[000000...] DRA2:[000000]FULL.BCK/SAVESET > > I > >(I KNOW I should've used /IMAGE, but unfortunately I was in a rush and  > >didn't :( ) > E > So you ended without information about your aliases in the saveset. N > This is really not good with a system disk (where aliases are heavily used). > G > >Anyway, if I try to restore the saveset (when booted up from the VMS $ > >install CD) using a command like: > > + > >      BACKUP DRA2:FULL.BCK/SAVESET DRA0:  > > J > >then BACKUP just dumps all the files in the Master File Directory. If IE > >do a BACKUP/LIST on the FULL.BCK saveset, it show that the correct - > >directory structures are in fact in place.  > > D > >Can someone tell me how to restore these files into their correct
 > >locations?  > 5 > $ BACKUP DRA2:FULL.BCK/SAVESET DRA0:[*...]/OWN=ORIG  > D > and then check the various [SYS*.SYSCOMMON...] trees which are all: > copies of [VMS$COMMON...] but should be aliases instead.> > This means you could repair them by hand with something like > 0 > $ RENAME [SYS0]SYSCOMMON.DIR SYSCOMMON_OLD.DIR= > $ SET FILE/ENTER=[SYS0]SYSCOMMON.DIR [000000]VMS$COMMON.DIR  > and so on  >  > Good luck  > -- > Peter "EPLAN" LANGSTOEGER ' > Network and OpenVMS system specialist  > E-mail  peter@langstoeger.atH > A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Mon, 31 Jul 2006 14:59:47 +0200 + From: Martin Vorlaender <mv@pdv-systeme.de>  Subject: Re: BACKUP weirdness + Message-ID: <4j6d62F6ev7fU1@individual.net>    sampsal@gmail.com schrieb:H > What if I just do the WRITEBOOT, and then do an "upgrade" installation3 > from CD? Would that repair the VMS$COMMON issues?   H I'd rather have it the other way around - first repair your system disk,
 then upgrade.    cu, 	    Martin  --  D One OS to rule them all       | Martin Vorlaender  |  OpenVMS rules!7 One OS to find them           | work: mv@pdv-systeme.de H One OS to bring them all      | http://www.pdv-systeme.de/users/martinv/> And in the Darkness bind them.| home: martin@radiogaga.harz.de   ------------------------------    Date: 31 Jul 2006 14:43:30 -02006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) Subject: Re: BACKUP weirdness * Message-ID: <44ce1712@news.langstoeger.at>  ] In article <1154347806.038256.238680@i42g2000cwa.googlegroups.com>, sampsal@gmail.com writes: B >I recently backed up my system drive using the following command: > < >      BACKUP DRA0:[000000...] DRA2:[000000]FULL.BCK/SAVESET > G >(I KNOW I should've used /IMAGE, but unfortunately I was in a rush and  >didn't :( )  C So you ended without information about your aliases in the saveset. L This is really not good with a system disk (where aliases are heavily used).  E >Anyway, if I try to restore the saveset (when booted up from the VMS " >install CD) using a command like: > ) >      BACKUP DRA2:FULL.BCK/SAVESET DRA0:  > H >then BACKUP just dumps all the files in the Master File Directory. If IC >do a BACKUP/LIST on the FULL.BCK saveset, it show that the correct + >directory structures are in fact in place.  > B >Can someone tell me how to restore these files into their correct >locations?   3 $ BACKUP DRA2:FULL.BCK/SAVESET DRA0:[*...]/OWN=ORIG   B and then check the various [SYS*.SYSCOMMON...] trees which are all8 copies of [VMS$COMMON...] but should be aliases instead.< This means you could repair them by hand with something like  . $ RENAME [SYS0]SYSCOMMON.DIR SYSCOMMON_OLD.DIR; $ SET FILE/ENTER=[SYS0]SYSCOMMON.DIR [000000]VMS$COMMON.DIR 	 and so on   	 Good luck  --   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   ------------------------------  % Date: Mon, 31 Jul 2006 14:43:55 +0200 + From: Martin Vorlaender <mv@pdv-systeme.de>  Subject: Re: BACKUP weirdness + Message-ID: <4j6c8aF6ge73U1@individual.net>    Martin Vorlaender schrieb: > sampsal@gmail.com wrote:D >> I recently backed up my system drive using the following command: >>> >>       BACKUP DRA0:[000000...] DRA2:[000000]FULL.BCK/SAVESET >>I >> (I KNOW I should've used /IMAGE, but unfortunately I was in a rush and  >> didn't :( ) >>G >> Anyway, if I try to restore the saveset (when booted up from the VMS $ >> install CD) using a command like: >>+ >>       BACKUP DRA2:FULL.BCK/SAVESET DRA0:  >>J >> then BACKUP just dumps all the files in the Master File Directory. If IE >> do a BACKUP/LIST on the FULL.BCK saveset, it show that the correct - >> directory structures are in fact in place.  >>D >> Can someone tell me how to restore these files into their correct
 >> locations?  > E > BACKUP DRA2:[000000]FULL.BCK/SAVESET DRA0:[*...] /BY_OWNER=ORIGINAL   ' I overread the "system drive" detail...   7 With the above command, you'll get the files back, BUT:  - the disk will not be bootable 8 - [SYSx.SYSCOMMON] will NOT be an alias for [VMS$COMMON]  D The first issue can be cured using SYS$SYSTEM:WRITEBOOT.EXE, for theB second you should delete the [SYSx.SYSCOMMON] tree and recreate it using SET FILE/ENTER.   7 See e.g. http://h71000.www7.hp.com/wizard/wiz_4375.html    cu, 	    Martin  --  D One OS to rule them all       | Martin Vorlaender  |  OpenVMS rules!7 One OS to find them           | work: mv@pdv-systeme.de H One OS to bring them all      | http://www.pdv-systeme.de/users/martinv/> And in the Darkness bind them.| home: martin@radiogaga.harz.de   ------------------------------    Date: 31 Jul 2006 07:43:37 -0700 From: sampsal@gmail.com  Subject: Re: BACKUP weirdness C Message-ID: <1154357017.075616.176650@b28g2000cwb.googlegroups.com>   F Phew, it worked. I did the restore, ran WRITEBOOT and then renamed theF SYSCOMMON.DIR to SYSCOMMON_OLD.DIR and finally ran the SET FILE/ENTER.  E System booted up fine and seems to be running normally. I assume that - it's safe to delete the SYSCOMMON_OLD.DIR no?    Sampsa      Peter 'EPLAN' LANGSTOEGER wrote:_ > In article <1154347806.038256.238680@i42g2000cwa.googlegroups.com>, sampsal@gmail.com writes: D > >I recently backed up my system drive using the following command: > > > > >      BACKUP DRA0:[000000...] DRA2:[000000]FULL.BCK/SAVESET > > I > >(I KNOW I should've used /IMAGE, but unfortunately I was in a rush and  > >didn't :( ) > E > So you ended without information about your aliases in the saveset. N > This is really not good with a system disk (where aliases are heavily used). > G > >Anyway, if I try to restore the saveset (when booted up from the VMS $ > >install CD) using a command like: > > + > >      BACKUP DRA2:FULL.BCK/SAVESET DRA0:  > > J > >then BACKUP just dumps all the files in the Master File Directory. If IE > >do a BACKUP/LIST on the FULL.BCK saveset, it show that the correct - > >directory structures are in fact in place.  > > D > >Can someone tell me how to restore these files into their correct
 > >locations?  > 5 > $ BACKUP DRA2:FULL.BCK/SAVESET DRA0:[*...]/OWN=ORIG  > D > and then check the various [SYS*.SYSCOMMON...] trees which are all: > copies of [VMS$COMMON...] but should be aliases instead.> > This means you could repair them by hand with something like > 0 > $ RENAME [SYS0]SYSCOMMON.DIR SYSCOMMON_OLD.DIR= > $ SET FILE/ENTER=[SYS0]SYSCOMMON.DIR [000000]VMS$COMMON.DIR  > and so on  >  > Good luck  > -- > Peter "EPLAN" LANGSTOEGER ' > Network and OpenVMS system specialist  > E-mail  peter@langstoeger.atH > A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Mon, 31 Jul 2006 13:18:47 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>  Subject: Re: BACKUP weirdness , Message-ID: <44CE3B75.1AF12EC1@teksavvy.com>   sampsal@gmail.com wrote: > H > What if I just do the WRITEBOOT, and then do an "upgrade" installation3 > from CD? Would that repair the VMS$COMMON issues?     3 No. Right now, you have two copies of system files.     J disk:[VMS$COMMON.SYSEXE]MAIL.EXE  and disk:[SYS0.SYSCOMMON.SYSEXE]MAIL.EXE   for intance.  F If you upgrade, there are good chances that the logicals will point toE the SYS0.SYSCOMMON.SYSEXE directory, but some portions of the upgrade  may touch the VMS$COMMON one.   H And worse, should this become part of a cluster boot node, the next nodeH you configure, will create SYS1 structure, and within SYS1, SYSCOMMON...F will be an alias of VMS$COMMON and thus may not contain the same files  as what SYS0.SYSCOMMON contains.  = $DELETE/LOG disk:[SYS0.SYSCOMMON...]*.*;*   (repeat until all " subdirectories have been emptied).$ $DELETE/LOG disk:[SYS0]SYSCOMMON.DIRD $SET FILE/ENTER=disk:[SYS0]SYSCOMMON.DIR disk:[000000]VMS$COMMON.DIR   Then, if you do a dir/full of : > DIR/FULL disk:[SYS0]SYSCOMMON.DIR, disk:[000000]VMS$COMMON.DIR  - Then both files should have the same file ID.    ------------------------------    Date: 31 Jul 2006 06:08:56 -0700* From: "Chris Lusardi" <clusardi2k@aol.com>A Subject: Is there a Unix /tmp directory. How dissimilar are they. C Message-ID: <1154351336.632481.151220@m73g2000cwd.googlegroups.com>    Hello,  B     What are the differences between Unix's /tmp directory and theG closest thing on a Vax? How much memory is involved? What can I use the   D corresponding Vax mechanism for? How often is the Vax /tmp directoryF used? Who uses it in general? Does the contents of this repository getB deleted after a certain time limit has been reached? Are there any" caveats that I should know about?      Thank you,   Christopher Lusardi    ------------------------------  + Date: Mon, 31 Jul 2006 13:47:49 +0000 (UTC)  From: david20@alpha2.mdx.ac.ukE Subject: Re: Is there a Unix /tmp directory. How dissimilar are they. , Message-ID: <eal1m5$530$1@south.jnrs.ja.net>  p In article <1154351336.632481.151220@m73g2000cwd.googlegroups.com>, "Chris Lusardi" <clusardi2k@aol.com> writes: >Hello,  > C >    What are the differences between Unix's /tmp directory and the H >closest thing on a Vax? How much memory is involved? What can I use the > E >corresponding Vax mechanism for? How often is the Vax /tmp directory G >used? Who uses it in general? Does the contents of this repository get C >deleted after a certain time limit has been reached? Are there any # >caveats that I should know about?   > L VAX is a hardware platform not an Operating System. Various flavours of Unix# have run on that hardware platform. > What you probably meant is what is the VMS equivalent of /tmp.' The answer being that there isn't one.    F There is a logical sys$scratch which is often used to specify where anL application should write scratch files but the default for this is to create" them in the user's home directory.    
 David Webb Security team leader CCSS Middlesex University          >  >Thank you,  >Christopher Lusardi >    ------------------------------  # Date: Mon, 31 Jul 2006 14:13:17 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>E Subject: Re: Is there a Unix /tmp directory. How dissimilar are they. 1 Message-ID: <1eozg.1294$6G6.553@news.cpqcorp.net>    Chris Lusardi wrote:  D >     What are the differences between Unix's /tmp directory and the > closest thing on a Vax?       What's the real question?  G    fwiw: VAX is hardware, and can run Unix, Ultrix, OpenVMS or various  B other operating systems.  OpenVMS VAX is software.  Since this is F comp.os.vms, I'll assume this is an OpenVMS question, but given there E have been increasing numbers of Windows and Unix questions appearing  H here in comp.os.vms, and while that's arguably still a safe assumption, G it's not a certainty.  Pedantic, I know -- but the more details I have  G here, the more certain I can be of providing an answer to the intended  I question.  (Some folks I've met use "VAX" to refer to OpenVMS Alpha, for  
 instance.)   > How much memory is involved?    G    As much as is permitted by disk size or (if enabled) by disk quotas.   6 > What can I use the corresponding Vax mechanism for?       Temporary storage.   , > How often is the Vax /tmp directory used?       Whenever it is requested.   > Who uses it in general?       Whomever requests it.  H > Does the contents of this repository get deleted after a certain time  > limit has been reached?   E    Not unless the local site has explicitly coded for this to occur,  C using tools not part of OpenVMS itself, assuming the user does not   delete the contents.  2 > Are there any caveats that I should know about?       There are many, I am sure.   H    Open-ended questions are very difficult to answer.  Best to indicate C what the requirements are and/or to provide some background on the  0 problem, and we can more easily work from there.  G    OpenVMS implements /tmp for C programmers, as part of its automatic  E parsing of Unix specifications.  Within the C RTL, /tmp is converted    into references to SYS$SCRATCH:.  B    The usual equivalent for non-C applications is the sys$scratch G logical name translation.  The other temporary storage used by various  G applications is to locate the temporary files ex-directory, or to mark  G temporary files as delete-on-close.  (Delete-on-close can also be used  H to clean up automatically, and -- even if the system crashes before the E application and the system can clean up -- the files that are either  E ex-directory or delete-on-close will eventually get deleted, and the  F storage released.  Typically after the next ANALYZE/DISK/REPAIR pass.)  I    For ease of clean-up, I redefine SYS$SCRATCH within my LOGIN.COM.  My  F local translation points to a subdirectory of my login directory, and @ this obviously allows far easier cleanup of the temporary files.  E    Various sites define SYS$SCRATCH to reference a scratch disk, and  I then use a combination of resource identifiers and an automatic deletion  H command procedure; usually a DELETE/BEFORE=[some-delta-time] command or F equivalent.  Possibly with the addition of disk quotas enabled on the ( volume, to capture run-away storage use.  B    Now, what is it that you need/what to do here, and what is the D particular environment?  From that, I or others may well be able to 6 better target an answer for your particular situation.   ------------------------------  % Date: Mon, 31 Jul 2006 10:26:42 -0400 3 From: "Richard B. Gilbert" <rgilbert88@comcast.net> E Subject: Re: Is there a Unix /tmp directory. How dissimilar are they. : Message-ID: <XLadnX2ejZC-jlPZnZ2dnUVZ_vOdnZ2d@comcast.com>   Chris Lusardi wrote:   > Hello, > D >     What are the differences between Unix's /tmp directory and theI > closest thing on a Vax? How much memory is involved? What can I use the  > F > corresponding Vax mechanism for? How often is the Vax /tmp directoryH > used? Who uses it in general? Does the contents of this repository getD > deleted after a certain time limit has been reached? Are there any$ > caveats that I should know about?  >  > 
 > Thank you,   > Christopher Lusardi  >   B The nearest thing to /tmp on VMS is the logical name SYS$SCRATCH. G SYS$SCRATCH is defined in the JOB table, probably by LOGINOUT.EXE.  In  H VMS SYS$SCRATCH points to a disk:[directory] path which, by default, is + your  home directory but could be anywhere.   F The biggest difference is that the contents don't disappear when your B reboot VMS.  In Unix (Solaris anyway) /tmp is mounted on the swap G partition and so can be stored on disk, in RAM or some of each and the  ) contents of /tmp do not survive a reboot.   C There was a book, now out of print, called "VMS for Unix Users, by  > Phillip Bourne, Digital Press 1990.  It's available, used, at  amazon.com.  See  F http://home.comcast.net/~rgilbert88/VMS_Bibliography.html for details  and/or other fine books.   ------------------------------    Date: 31 Jul 2006 07:59:20 -0700( From: "Rich Jordan" <jordan@ccs4vms.com>8 Subject: Re: page_setup and a signature 'font' on a dimmC Message-ID: <1154357960.025782.160810@m73g2000cwd.googlegroups.com>    wilmesr@hotmail.com wrote: > hi,  > 8 > We've purchased a dimm from HP with a signature on it. > G > This is the current working escape sequence to print the signature on 2 > the Laserjet 4000 that the dimm is installed in. > 0 > <ESC>*p1500x2000Y<ESC>(1Q<ESC>(s1p36.0v0s0b0TS > H > I can get the signature to print if I embed the escape sequence withinH > the file being sent to the printer.  This will *probably* work to suit? > our needs however I'd like to avoid mucking around within the 9 > application that will ultimately be doing the printing.  > H > The best solution would be to have the print queue print the signatureF > at the given location on every page that it recieves (i can dedicate- > the queue for these particular print jobs).  > E > I created a control library and inserted the module with the escape F > sequence then created a form that uses the module as the page_setup.G > Doing this I can get the signature on every page but because I didn't G > reset the font none of the text printed.  I updated the module with a G > 'reset to default' directly after the font selection escape sequence.  > 6 > <ESC>*p1500x2000Y<ESC>(1Q<ESC>(s1p36.0v0s0b0TS<ESC>E > I > The thought was that the page_setup would load the signature then reset H > to the default font and the printer would accept and print the rest of! > the incoming data on that page.  > 
 >  No joy. > ! > Any thoughts anyone ?  Bueller?  >  > Thanks in advance! > RW  G As mentioned in another post the <ESC>-E command will print all current E data and reset to defaults; the signature won't overlay the page as a  result.   C You could try creating a PCL macro that sets the signature font and E prints it, then have your page setup module call that macro; one mode F (I forget if its 'execute' or 'call') will preserve the printer state,D execute the macro, then restore it.  The macro could be loaded everyD time the printer is restarted (like loading a soft font) or could be: included in a job setup module for the form you are using.  B Alternatively if your printer is always at a certain default font,D regardless of the type of document being printed to it that uses theE signature, you could add the code to reset to that font (and probably G reset the cursor position to top of page since your signature code does D move it) to the end of your page setup module.  Make sure there's noE formfeed or unwanted carriage control characters in the setup module.   E Depending on the communications method in use between your VMS system D and printer you _may_ also need to put the ANSI DCS character at theD beginning, and the ST character at the end of the page setup module;@ this "hides" the non-ANSI escape sequences from the VMS terminalG driver.  You may also have to use the 7-bit equivalents for those 8-bit @ (high bit set) characters if your data path is 7 bits (telnet?).   ------------------------------  % Date: Mon, 31 Jul 2006 11:36:04 +0100 0 From: Chris Sharman <chris.sharman@sorry.nospam> Subject: ra3000/hsz22 4 Message-ID: <eakmc2$4bh$1$8302bc10@news.demon.co.uk>  H For some mysterious reason, h22agent on our vms box has stopped working.6 It starts ok, but keels over more or less immediately.E I'm just back from a week's holiday - don't think anything's changed.  All this on Alpha VMS 7.3-1.B Any suggestions as to what's broke/how to fix it much appreciated.G The client still works serially, so I'm off on the trek to the machine   room ...   Thanks Chris    The output log is:> Jul 31 10:28:40 2006 HSZ22 Agent started. Version: 2.0 (BL 27)) HSZ22 Agent started. Version: 2.0 (BL 27)   G Jul 31 10:28:40 2006  WARNING:  - A subsytem change has been detected:  - EQUUS dkb0 OVRL=1 (SP_MONITOR: MonitorSubsys)   K Jul 31 10:28:40 2006  WARNING:  - EQUUS dkb0 10000000002 HSZ22 luns(D000:1)    (SP_MONITOR: MonitorSubsys)    The error log shows:B %SYSTEM-F-STKOVF, stack overflow, PC=FFFFFFFF800E9844, PS=0000001B/ %TRACE-F-TRACEBACK, symbolic stack dump follows K    image    module    routine             line      rel PC           abs PC @                                              0 0000000000000000  FFFFFFFF800E9844@   TCPIP$IPC_SHR                              0 0000000000006D44  00000000000FAD44@   DECC$SHR_EV56                              0 0000000000043D10  FFFFFFFF809CFD10@   DECC$SHR_EV56                                               ? 	         ? @   UCX$IPC_SHR                                0 000000000001EA64  0000000000236A64@   UCX$IPC_SHR                                0 0000000000017614  000000000022F614@   UCX$IPC_SHR                                0 0000000000017DB4  000000000022FDB4@   UCX$IPC_SHR                                0 00000000000179CC  000000000022F9CC@   UCX$IPC_SHR                                0 0000000000009558  0000000000221558@   TCPIP$ACCESS_SHR                           0 0000000000061FA8  00000000001D7FA8@   TCPIP$ACCESS_SHR                           0 000000000005DA74  00000000001D3A74@   TCPIP$ACCESS_SHR                           0 0000000000030A28  00000000001A6A28@   TCPIP$ACCESS_SHR                           0 0000000000043664  00000000001B9664@   TCPIP$ACCESS_SHR                           0 0000000000041E18  00000000001B7E18@   TCPIP$ACCESS_SHR                           0 000000000003C528  00000000001B2528@   TCPIP$IPC_SHR                              0 0000000000001268  00000000000F5268@   DECC$SHR_EV56                              0 00000000000421A0  FFFFFFFF809CE1A0@   DECC$SHR_EV56                                               ? 	         ? @   H22AGENT  SP_SNMP  NotifyClientSnmp    13097 0000000000001324  000000000003CA44(   H22AGENT  SP_MONITOR  SendTrapMessages@                                          13590 0000000000001DDC  00000000000352AC@   H22AGENT  SP_MONITOR  MonitorSubsys    12642 000000000000065C  0000000000033B2C@   PTHREAD$RTL                                0 0000000000023914  000000007BBFB914@   PTHREAD$RTL                                                 ? 	         ? @   PTHREAD$RTL                                0 0000000000011400  000000007BBE9400@   PTHREAD$RTL                                0 FFFFFFFF84428000  0000000000000000@                                              0 FFFFFFFF8028B63C  FFFFFFFF8028B63C   ------------------------------  % Date: Mon, 31 Jul 2006 11:54:46 +0100 0 From: Chris Sharman <chris.sharman@sorry.nospam>% Subject: unix search list logicals ?? 4 Message-ID: <eaknf1$g39$1$830fa17d@news.demon.co.uk>  ? A bit off-topic, this - but I'm asking here because you'll all   understand the question!  < Is there an equivalent to vms search list logicals on unix ?  / We have php 'templates', under different roots. D Most of these templates are standard, and could easily be kept in a F common root - there's just one or two that would be specific to their 	 own root.   ; In VMS, this is easily achieved with a search list logical. E In Unix (fc4 linux), we can't see any easy way to do it that doesn't  H involve duplicating large numbers of files (or links to files) across a  tree, making maintenance hard.  H Suggestions welcome - not even knowing the right terminology to ask the : question on linux makes it difficult to find the solution.   fc4, apache, mysql, php.   Thanks Chris    ------------------------------  % Date: Mon, 31 Jul 2006 10:04:28 -0400 3 From: "Richard B. Gilbert" <rgilbert88@comcast.net> ) Subject: Re: unix search list logicals ?? : Message-ID: <e9ydnYaSlc5wkFPZnZ2dnUVZ_rOdnZ2d@comcast.com>   Chris Sharman wrote:  A > A bit off-topic, this - but I'm asking here because you'll all   > understand the question! > > > Is there an equivalent to vms search list logicals on unix ? > 1 > We have php 'templates', under different roots. F > Most of these templates are standard, and could easily be kept in a H > common root - there's just one or two that would be specific to their  > own root.  > = > In VMS, this is easily achieved with a search list logical. G > In Unix (fc4 linux), we can't see any easy way to do it that doesn't  J > involve duplicating large numbers of files (or links to files) across a   > tree, making maintenance hard. > J > Suggestions welcome - not even knowing the right terminology to ask the < > question on linux makes it difficult to find the solution. >  > fc4, apache, mysql, php. >  > Thanks > Chris    On a unix system try: 
 echo $PATH  C That's the first thing that comes to mind.  Bear in mind that Unix  C environment variables are NOT logical names.  Don't expect them to   follow VMS rules.    ------------------------------  % Date: Mon, 31 Jul 2006 16:59:16 +0100 0 From: Chris Sharman <chris.sharman@sorry.nospam>) Subject: Re: unix search list logicals ?? 4 Message-ID: <eal9al$47p$1$8300dec7@news.demon.co.uk>   Richard B. Gilbert wrote:  > Chris Sharman wrote:? >> Is there an equivalent to vms search list logicals on unix ?  >>2 >> We have php 'templates', under different roots.G >> Most of these templates are standard, and could easily be kept in a  I >> common root - there's just one or two that would be specific to their   >> own root. >>> >> In VMS, this is easily achieved with a search list logical.H >> In Unix (fc4 linux), we can't see any easy way to do it that doesn't I >> involve duplicating large numbers of files (or links to files) across  # >> a tree, making maintenance hard.  >>G >> Suggestions welcome - not even knowing the right terminology to ask  A >> the question on linux makes it difficult to find the solution.  >> >> fc4, apache, mysql, php.  >>	 >> Thanks  >> Chris >  > On a unix system try:  > echo $PATH  ? Yes - but that's implemented somewhere inside the shell, afaik? D Is there something similar for php, or would I have to roll my own ? Eg: , (in php) include('$MYLIST:myfile.template');( where $MYLIST gives a list of locations.G On VMS I wouldn't need the application to know about the search list -  7 rms would take care of it, if I'd defined it correctly.    Thanks Chris    ------------------------------    Date: 31 Jul 2006 11:22:44 -0500 From: briggs@encompasserve.org) Subject: Re: unix search list logicals ?? 3 Message-ID: <c9mUw+j$jMX1@eisner.encompasserve.org>   g In article <eal9al$47p$1$8300dec7@news.demon.co.uk>, Chris Sharman <chris.sharman@sorry.nospam> writes:  > Richard B. Gilbert wrote:  >> On a unix system try:
 >> echo $PATH  > A > Yes - but that's implemented somewhere inside the shell, afaik? F > Is there something similar for php, or would I have to roll my own ? > Eg: . > (in php) include('$MYLIST:myfile.template');  < Did you look at the documentation for php?  Specifically theC include_path configuration setting that can be set in your php.ini?    ------------------------------    Date: 31 Jul 2006 06:33:22 -0700  From: "Ian Miller" <ijm@uk2.net> Subject: Re: V8.2 is outB Message-ID: <1154352801.989932.110700@75g2000cwc.googlegroups.com>  ( >From the May 8th openvms.org newsletter  3 "The logical disk driver utility now has a new home    http://www.digiater.nl/lddriver   4 There is not yet much content but the latest version: (V8.2) is available for download. This is the version that will ship with OpenVMS V8.3"  ; I see that there is now more content than there was in May.    ------------------------------  # Date: Mon, 31 Jul 2006 15:10:49 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com> Subject: Re: V8.2 is out1 Message-ID: <Z3pzg.1302$yJ6.917@news.cpqcorp.net>    Ian Miller wrote:   5 > "The logical disk driver utility now has a new home  > ! > http://www.digiater.nl/lddriver  > 6 > There is not yet much content but the latest version< > (V8.2) is available for download. This is the version that > will ship with OpenVMS V8.3"  H    That version of LD has (also) been at the Freeware V8.0 staging area A for a while now (it was used during the EFT of V8.2, among other  H applications), and it's the version that is to be found on the Freeware B V8.0 distro, the version of the Freeware that is currently in the 4 release process along with the OpenVMS V8.3 release.  +    <http://www.hp.com/go/openvms/freeware/>   G    The OpenVMS.Org site and/or mailing lists are arguably the de facto  H announcement paths for this sort of stuff, but I certainly haven't been H very good at passing along details of individual updates for kits found  on the Freeware.  G    I will be posting a note here when the Freeware V8.0 kit itself has  G been posted to the external site, something that I presently expect to    occur over the next week or two.   ------------------------------    Date: 31 Jul 2006 14:55:25 -02006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) Subject: [LD] V8.2 is out , Message-ID: <44ce19dd$1@news.langstoeger.at>   In case you haven't noted   G LD Freeware (used to be from VMS eng) V8.2 (eg. support for 8.3) is out H (mail changed from lddriver at hp dot com to lddriver at digiater at nl) and works now on VAX too   Thanks a lot folks   --   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.423 ************************                                                                                                                                                                                                                                                                                                                                                                                                                                        YߑqElkص;29;25ٲ$OX`=:[Ode#1[WHK$Dsʎpz
,^򏝕g^M[{29f"ʌpv&+;<[uv{lzTll-Yvvx3`wl6+;j呸]Z<7H2je_V}牅~v6ʮsͮ,rͮ6+;zL`;ǮsͮOY]O
lVv6
7v7oӶ#8mڞa1v<z#S,[od{eٹ)A/kWc]d^`eF8;C66`جv]ˣl9w6+;lsʰ];ߪ7vno)'6+;v
l3[emfe}1gf,8.$3S(C#hnۤL4Ro(SnRfj]bR.i,3ճP&`R&\cZfLЌgKP&nR94IJʴٸCV22mB6m7Ц&e64mc{uPhnS=61)#iڴMm:`RFl&e62)#qCWMW԰TW}.]ՕDYˣlXt~D>tTo׃޽k}[e{kzpG[j{UYl@='OٴiSۚBMhCH]S( ww'v,Q]׽}B$!Xu,.ǀF-$YZa,XHvei7i;i;MnNδ!cwL(N'~Uq44;̨Y<[wkϽ{	h;s=sϽSH4VR/JOeҠx]޺M7}x»Hjڷ4omk_U"sdhoiLGS#}jmM6=[k32렻n>x(P.emyFR2*$^Hj0펦&KAOdٕl4Bf/ڶzt =PFo҈<C>wwop7Pm8hCm-
nNhZ;Xm]1&3QGM29px8h 3Z47[)H%iHe&'F?Pdӎ nYf8Ҧ2׭V֐:&p߭876AR
^nW[<a`1͏^X>vO)u{vR"DvAmE}{v<
$̳)69vK
IprizSkL̡z6Q4VFGߚLhӠZ3cGJc6T:q\'zGG1WDow<:946Ao)3қh_rM܁'~;@)_4O{kl>g+c1!3du͑w"okxZQ#\rxl4smPUsltE%|`UeUD%0?-]Mmjr݃Mm Auޞ[hGS|[F<O~fjx꣜?
!R`z\z0<:Ҽ4h^wݡ
~q=468sؑ#}bt##)F5T XI*>Jtu٫R<e5)RfN<ndB(Bbjmt(0
5DhۖoX_
Ғo+3׽MEgpbxGā𘶼}5w3S q.(fL>Pg>G~ r1<hxj%2=Bޯny=1@1 u=Dx6.m~xr,v]˓x<[P)h<x;{}[:~[|}-=;MXTxx7K߸~}/oc3*Z}}yl/k~*^k_sSڝwMνݝV|3o;}_''щ_9ǝa|YbVWJRzH@:ji<MdSuwKGR;/}w-3CggwKM[5wM;2'11psYSfwT:Cl+|A;pF75YYT	^6%p!4@,z/>߫!yߴϑ+izd{\mquzpGۍbib;YKZǴqQ?&pOuv;G(gVsnNc	u(7^[
&Ln+A=`ayDZ GOÂm[-}'˂DM%e-;ģ>j2Lv:>G<a٫ѰM&]6!C@	i+c;~:?dyg;ǮiM9VwQ7)cZM
!ֶ-9>v\?csƟᎿb?ٱ8::mEzӫW
ͥwP_<<ߩe_ɔW~M6~BƹI|n4M{O돒:E>Ό4g"-7V{tĕ6POȈRl$/:ƁF1''(2lzg|r|'e~[9T'xztꃅhjHkB9wI-.O<G5{wzCÙR	&(bIH|vViǕhw{m0F1=c]bioϋ ݍeJ^UnGF'ު(\PӞA;bwZW0nY