1 INFO-VAX	Mon, 23 Jun 2003	Volume 2003 : Issue 345       Contents:% Re: Backup Software for VMS and Linux % Re: Backup Software for VMS and Linux % Re: DSSI disks and allocation classes % Re: DSSI disks and allocation classes % Re: DSSI disks and allocation classes % Re: DSSI disks and allocation classes 
 GNV and ODS-5  Re: GNV and ODS-5  Re: HP to drop hpux? Re: HP to drop hpux? Re: HP to drop hpux?! Re: OpenVMS (TM) VAX Version X7G7  __PAL_REMQUEQ from C  F ----------------------------------------------------------------------  % Date: Sun, 22 Jun 2003 20:08:18 +0100 % From: Alan Fay <alan.fay@veritas.com> . Subject: Re: Backup Software for VMS and Linux8 Message-ID: <pan.2003.06.22.19.08.10.675001@veritas.com>  4 On Tue, 17 Jun 2003 23:31:02 -0500, Rob Young wrote:  ] > In article <3EEFE10B.80CABE78@fsi.net>, "David J. Dachtera" <djesys.nospam@fsi.net> writes: # >> CHANGE username to westes wrote:  >>  J >>> What backup applications implement good agents for both VMS and Linux?O >>> Could we run the LTO-1 drives on a Linux backup server, and then backup and H >>> restore data for VMS through a VMS agent that works with that backup >>> application? >>   >> None. >>   > > > 	Sure, but you will have to do the rest of the digging. . .  >  > 	TSM has a server for Linux: > J > http://www-3.ibm.com/software/tivoli/products/storage-mgr/platforms.html > 7 > http://www-3.ibm.com/software/tivoli/solutions/linux/  > = > 	IBM has been hot after LTO since intro.  Ultrium is LTO-1.  > @ > 	The TSM client for OpenVMS is sold by Storsol.  Their support? > 	is excellent.  Their product works and works very well.  The E > 	client is surprisingly cheap, I believe less than $2000 for Alpha  . > 	departmental server but would have to look. > P > http://www.storserver.com/main.cfm?menu=2&submenu=abc&detail=include/p_abc.inc > " >>> What other options do we have? >  > 	Maybe Legato? > 	 > 				Rob   F There is also VERITAS NetBackup. The latest v4.5 MP4 (Maintenance Pack$ Four) User Guide is available from:-  I ftp://ftp.emea.support.veritas.com/pub/support/Products/NetBackup_OpenVMS        nbu_vms.pdf   ? Before you decide please perform some backup performance tests.    Alan Fay VERITAS Software Corporation Roseville Engineering    ------------------------------  # Date: Mon, 23 Jun 2003 00:28:45 GMT * From: "Mark Buda" <buda_NO@SPAM.yahoo.com>. Subject: Re: Backup Software for VMS and Linux= Message-ID: <1RrJa.14967$Jw6.6433381@news1.news.adelphia.net>    Also test the restore portion.  I When everything goes south and you are trying to restore, but it takes 64 J for the restore to complete, that would be a tough cookie to swallow.  NotE saying any software has this problem, just remember, restore speed is H actually more important then back up speed, when you have to recover....   --  
 Sincerely,	 Mark Buda     2 "Alan Fay" <alan.fay@veritas.com> wrote in message2 news:pan.2003.06.22.19.08.10.675001@veritas.com...6 > On Tue, 17 Jun 2003 23:31:02 -0500, Rob Young wrote: > ? > > In article <3EEFE10B.80CABE78@fsi.net>, "David J. Dachtera"  <djesys.nospam@fsi.net> writes: % > >> CHANGE username to westes wrote:  > >>L > >>> What backup applications implement good agents for both VMS and Linux?F > >>> Could we run the LTO-1 drives on a Linux backup server, and then
 backup andJ > >>> restore data for VMS through a VMS agent that works with that backup > >>> application? > >>
 > >> None. > >> > > > > > Sure, but you will have to do the rest of the digging. . . > >  > > TSM has a server for Linux:  > > L > > http://www-3.ibm.com/software/tivoli/products/storage-mgr/platforms.html > > 9 > > http://www-3.ibm.com/software/tivoli/solutions/linux/  > > > > > IBM has been hot after LTO since intro.  Ultrium is LTO-1. > > A > > The TSM client for OpenVMS is sold by Storsol.  Their support @ > > is excellent.  Their product works and works very well.  TheE > > client is surprisingly cheap, I believe less than $2000 for Alpha / > > departmental server but would have to look.  > >  > > L http://www.storserver.com/main.cfm?menu=2&submenu=abc&detail=include/p_abc.i nc > > $ > >>> What other options do we have? > >  > > Maybe Legato?  > >  > > Rob  > H > There is also VERITAS NetBackup. The latest v4.5 MP4 (Maintenance Pack& > Four) User Guide is available from:- > K > ftp://ftp.emea.support.veritas.com/pub/support/Products/NetBackup_OpenVMS  >       nbu_vms.pdf  > A > Before you decide please perform some backup performance tests.  > 
 > Alan Fay > VERITAS Software Corporation > Roseville Engineering  >  >  >    ------------------------------  % Date: Sun, 22 Jun 2003 23:45:48 +0200 + From: "Hans Vlems" <hvlems.nieuw@zonnet.nl> . Subject: Re: DSSI disks and allocation classes5 Message-ID: <bd582h$p96qm$1@ID-143435.news.dfncis.de>   L "Phillip Helbig---remove CLOTHES to reply" <helbig@astro.multiCLOTHESvax.de>1 schreef in bericht news:bd56fe$lp9$1@online.de... D > In article <bd46go$ouurp$1@ID-143435.news.dfncis.de>, "Hans Vlems"" > <hvlems.nieuw@zonnet.nl> writes: > F > > > Based on this and other responses, I think I can change the DSSI stuff.H > > > What is still unclear is the relationship of this parameter to the: > > > normal allocation class parameter used in a cluster. > > I > > A DSSI disk is not really a local, directly attached device. The DSSI  bus K > > may be a cousin of SCSI but behaves more like a CI bus. In a CI cluster  you K > > need ALLOCLASS on VMS nodes and HSx nodes because the disk (or tape for  thatI > > matter) must  (1) have a unique name and (2) in case of dual hosting:  must% > > have the same name on both nodes. H > > So under VMS you've got SYSGEN to set ALLOCLASS, on the HSC there is SETSHOW L > > to set ALLOCLASS and on the DSSI devices there is PARAM to set ALLCLASS.G > > Of course you know all this and think why bother since DSSI is dual  hostedH > > anyway. IIRC there's a way to put three VMS systems in a shared DSSIE > > configuration. That allows possible conigurations where VMS based 	 ALLOCLASS K > > wouldn't do. Hence the need for some intelligence on the DSSI tapes and ; > > disks. And you ending up with this particular question. , > > Or did I miss the point of the question? > I > I'm not sure how I can change the ALLOCLASS for the DSSI disk.  Several D > folks have posted suggestions, but they don't work out of the box. > @ So SET HOST/DUP did not work then? Could you elaborate somewhat?  I > To simplify things: what if I leave the DSSI ALLOCLASS as it is (1) but E > set the VMS allocation class to something else (2).  Will this be a = > problem as long as only one machine talks to the DSSI disk?   I Correct, if there's only one system connected to it then there won't be a  problem at all.    ------------------------------  + Date: Sun, 22 Jun 2003 21:18:38 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply). Subject: Re: DSSI disks and allocation classes$ Message-ID: <bd56fe$lp9$1@online.de>  B In article <bd46go$ouurp$1@ID-143435.news.dfncis.de>, "Hans Vlems"! <hvlems.nieuw@zonnet.nl> writes:    K > > Based on this and other responses, I think I can change the DSSI stuff. F > > What is still unclear is the relationship of this parameter to the8 > > normal allocation class parameter used in a cluster. > K > A DSSI disk is not really a local, directly attached device. The DSSI bus M > may be a cousin of SCSI but behaves more like a CI bus. In a CI cluster you N > need ALLOCLASS on VMS nodes and HSx nodes because the disk (or tape for thatL > matter) must  (1) have a unique name and (2) in case of dual hosting: must# > have the same name on both nodes. N > So under VMS you've got SYSGEN to set ALLOCLASS, on the HSC there is SETSHOWJ > to set ALLOCLASS and on the DSSI devices there is PARAM to set ALLCLASS.L > Of course you know all this and think why bother since DSSI is dual hostedF > anyway. IIRC there's a way to put three VMS systems in a shared DSSIM > configuration. That allows possible conigurations where VMS based ALLOCLASS I > wouldn't do. Hence the need for some intelligence on the DSSI tapes and 9 > disks. And you ending up with this particular question. * > Or did I miss the point of the question?  H I'm not sure how I can change the ALLOCLASS for the DSSI disk.  Several B folks have posted suggestions, but they don't work out of the box.  H To simplify things: what if I leave the DSSI ALLOCLASS as it is (1) but D set the VMS allocation class to something else (2).  Will this be a ; problem as long as only one machine talks to the DSSI disk?    ------------------------------  + Date: Sun, 22 Jun 2003 21:21:02 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply). Subject: Re: DSSI disks and allocation classes$ Message-ID: <bd56ju$lp9$2@online.de>  H In article <bd4ej1$lph$1@pcls4.std.com>, moroney@world.std.spaamtrap.com (Michael Moroney) writes:   K > Since you are unfamiliar with CI/HSC configurations, think of things this H > way, although this is not strictly correct.  Think of the HSC/HSJ/DSSIL > controllers as cluster members which do nothing but serve their disks (andI > tapes, if any)  They have an alloclass like true cluster members do, as F > well as a nodename (equivalent to SCSNODE).  Since the alloclass andK > nodename belong to the DSSI controller and not to the VMS system, a fresh " > VMS install doesn't change them.  I In that case, it would be more logical to have the DSSI allocation class  E be different than the SCSI allocation class on the same machine---at  @ least if (for various reasons) each machine in my cluster has a E different allocation class.  (After all, if the controller should be  " thought of as being its own node.)   ------------------------------  % Date: Sun, 22 Jun 2003 22:03:39 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> . Subject: Re: DSSI disks and allocation classes' Message-ID: <3EF66E0B.9E0538B3@fsi.net>   / Phillip Helbig---remove CLOTHES to reply wrote:  > [snip]I > I'm not sure how I can change the ALLOCLASS for the DSSI disk.  Several D > folks have posted suggestions, but they don't work out of the box.  C It's been some ten-plus years since I had to do this, but I seem to D recall actually having to do this through NCP using CONNECT, not SETE HOST/DUP. I'm not saying that's even remotely helpful, just hoping it D will jog someone's memory and result in another post with more info.  B One place I just thought to look: the on-line doc.'s including theF archived doc.'s re: cluster configurations. I need to get ready for my& Monday, else I'd go digging right now.  I > To simplify things: what if I leave the DSSI ALLOCLASS as it is (1) but E > set the VMS allocation class to something else (2).  Will this be a = > problem as long as only one machine talks to the DSSI disk?   ' If you find that acceptable, why not...    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  # Date: Sun, 22 Jun 2003 22:17:07 GMT 4 From: brad@.gateway.2wire.net (Bradford J. Hamilton) Subject: GNV and ODS-5, Message-ID: <DVpJa.62219$vq.13355@sccrnsc04>   Folks,  H The subject line says it all.  I attempted to install GNV on my hobbyist? Alpha (V7.3-1).  The install failed with the following message:   P %PCSI-E-OPENIN, error opening DISK$RABBIT_0731:[SYS0.SYSCOMMON.][GNV.SRC.GNV.BZI# P2]BZIP2^.1.PREFORMATTED;* as input / -RMS-E-FND, ACP file or directory lookup failed - -SYSTEM-W-BADFILEVER, bad file version number   K I'm assuming that because the filename referenced contains two "dots", that J ODS-5 is a prerequisite, even though it is not listed at the hp website as such:   9 http://h71000.www7.hp.com/opensource/gnvreadme_first.html   M Anyone know if I need ODS-5?  Anyone have any problems using ODS-5?  I recall K that I had problems restoring an incremental backup on an ODS-5 disk a year & or so ago, when I was "testing" ODS-5.   ------------------------------  # Date: Mon, 23 Jun 2003 00:44:36 GMT - From: "John E. Malmberg" <wb8tyw@qsl.network>  Subject: Re: GNV and ODS-5= Message-ID: <U3sJa.14973$Jw6.6438555@news1.news.adelphia.net>    Bradford J. Hamilton wrote:  > O > Anyone know if I need ODS-5?  Anyone have any problems using ODS-5?  I recall M > that I had problems restoring an incremental backup on an ODS-5 disk a year ( > or so ago, when I was "testing" ODS-5.  , I am not sure that it works on ODS-5 either.  @ It is a known issue and is expected to be fixed in a future kit.  H When the next kit shows up on the web site, I recommend doing a product D remove of the old GNV kit before doing a PRODUCT INSTALL instead of H installing over, otherwise you may see errors as it tries to remove the  non-existant files.      -John  wb8tyw@qsl.network Personal Opinion Only    ------------------------------  + Date: Sun, 22 Jun 2003 21:09:03 +0000 (UTC) 0 From: "insomnee_a" <robert.heyes@btinternet.com> Subject: Re: HP to drop hpux? / Message-ID: <bd55tf$aj2$1@titan.btinternet.com>   L As a user of HPUX and OpenVMS, I would drop HPUX too. In fact, all Unix, its crap.   ; "Fabio Cardoso" <fabiopenvms@yahoo.com.br> wrote in message : news:20030619233105.77662.qmail@web20210.mail.yahoo.com... > Well > 3 > HP may discontinue HP-UX, OVMS, etc... and return 2 > to be a printer business/services-only company !: > May be for HP, operating systems are not important... if, > they can have Linux for free for example ! > 	 > Regards  >  > FC > / > --- Bob Ceculski <bob@instantwhip.com> wrote: A > > it says here that its a rumor ... maybe Carly is smarter than  > > we think! :) > > A > > http://www.infoworld.com/article/03/06/18/HNsapfiorina_1.html  >  >  > =====  > ========================== > Fbio dos Santos Cardoso > OpenVMS System Manager > Rio de Janeiro - Brazil  > fabiopenvms@yahoo.com.br > ========================== > $ > __________________________________ > Do you Yahoo!?- > SBC Yahoo! DSL - Now only $29.95 per month!  > http://sbc.yahoo.com   ------------------------------  % Date: Sun, 22 Jun 2003 23:18:05 -0400 ( From: David Froble <davef@tsoft-inc.com> Subject: Re: HP to drop hpux? * Message-ID: <3EF6716D.80509@tsoft-inc.com>   Bill Todd wrote:    M > Customers who want something other than Windows/Linux/Intel in their future M > would be well-advised to consider looking for it elsewhere:  both Carly and L > the team she acquired from Compaq have by their actions made it clear thatK > they can't be trusted in other areas.  Don't forget that EV79 development L > was radically scaled back (in schedule, in clock speed, and in cache size)J > despite promises by both Compaq and HP to adhere to the 'plan of record'F > that was established immediately after the Alphacide - when EV79 was? > *created* as a sop to those upset about the EV8 cancellation.     : Bill, are you saying that these people are (gasp!), liars?    O I guess that if COMMITMENTS don't mean a thing, then breaking promises isn't a  . problem either.  (Pretty much the same thing.)  @ Maybe it's a memory thing.  They just forget about the promises.  ? You don't think it has anything to do with comparison to IA-64?    Dave   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com6 T-Soft, Inc.  170 Grimplin Road  Vanderbilt, PA  15486   ------------------------------  % Date: Sun, 22 Jun 2003 23:21:50 -0400 ( From: David Froble <davef@tsoft-inc.com> Subject: Re: HP to drop hpux? , Message-ID: <3EF6724E.4050705@tsoft-inc.com>    Peter 'EPLAN' LANGSTOEGER wrote:    3 > Bashing HP is obviously totally on-topic here ;-)   M I totally disagree with that statement.  However, I would agree that bashing  & stupidity anywhere is always on-topic.   Dave   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com6 T-Soft, Inc.  170 Grimplin Road  Vanderbilt, PA  15486   ------------------------------  # Date: Mon, 23 Jun 2003 00:25:56 GMT * From: "Mark Buda" <buda_NO@SPAM.yahoo.com>* Subject: Re: OpenVMS (TM) VAX Version X7G7= Message-ID: <oOrJa.14966$Jw6.6432108@news1.news.adelphia.net>    Hello,  4 It is not a problem, as long as you end up with V7.3   --  
 Sincerely,	 Mark Buda     L "Phillip Helbig---remove CLOTHES to reply" <helbig@astro.multiCLOTHESvax.de>/ wrote in message news:bd3rh9$edf$1@online.de... E > In article <iAcJa.14702$Jw6.6190527@news1.news.adelphia.net>, "Mark ( > Buda" <buda_NO@SPAM.yahoo.com> writes: > K > > That is an internal build ident that is used in VMS engineering.  It is H > > incremented each time a new build occurs.  Base 36 number (A-Z, 0-9) > J > So it's perfectly normal to see this version number when booting the CD?J > (When booting the system after installation, all appears as normal, i.e. > Version 7.3 shows up.) >    ------------------------------  # Date: Mon, 23 Jun 2003 02:40:41 GMT / From: "Brian Kennedy" <kennedybg@earthlink.net>  Subject: __PAL_REMQUEQ from C E Message-ID: <JMtJa.60930$Io.5695755@newsread2.prod.itd.earthlink.net>   K Has anyone used the __PAL_REMQUEQ function defined in the BUILTINS.H header J file? This function differs from the other REMQUEx functions in that it isI suppose to remove an entry from anywhere in a queue, not just the head or I the tail. However, I get an ACCVIO when I use the function. The following J code will generate the ACCVIO on an Alpha running OpenVMS 7.2. Can someoneK shed some light on why this is happening? Documentation on this function is ' almost non-existent. Thanks in advance.     #pragma required_pointer_size 64   #include <builtins.h>  #include <ints.h>  #include <stdio.h> #include <stdlib.h>  #include <lib$routines.h>    typedef struct {      uint64 l[2]; } Link;    typedef struct {      Link l;      unsigned long value; } Data;   ' _align(OCTAWORD) static Link QueueHead;   , int main( int arg_count, char* arg_array[] ) {  #define MAX_ENTRIES 32      Data*    array[MAX_ENTRIES];     Data*    queueitem;      uint64    vmsize;      unsigned long counter;     unsigned int result;  8     for ( counter =0; counter < MAX_ENTRIES; counter++ )     {          vmsize = sizeof(Data);5         LIB$GET_VM_64( &vmsize, &array[counter], 0 ); (         array[counter]->value = counter;=         result = __PAL_INSQTIQ( &QueueHead, array[counter] );      }        /* This works fine.      */>     result = __PAL_REMQTIQ( &QueueHead, (void**) &queueitem );0     fprintf( stdout, "%d\n", queueitem->value );       /* This access violates.     */E     result = __PAL_REMQUEQ( (void*) array[14], (void**) &queueitem ); 0     fprintf( stdout, "%d\n", queueitem->value );       exit( 1 ); }    ------------------------------   End of INFO-VAX 2003.345 ************************