INFO-VAX Thu, 28 Jun 2007 Volume 2007 : Issue 350 Contents: Re: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Re: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Re: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Re: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Re: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Re: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Re: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Re: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Re: And the question was? (Re: Amazing, two new articles on Computerworld.com ac RE: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Re: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Re: Catch OPCOM messages (in PASCAL) creating firmware floppies on FreeBSD or VMS Re: creating firmware floppies on FreeBSD or VMS Re: cURL 7.16.3 available RE: HP "Support" for OpenVMS Re: mysql on vms Re: mysql on vms Re: mysql on vms Re: OpenVMS - When downtime is not an option Re: OpenVMS - When downtime is not an option Re: OpenVMS - When downtime is not an option Re: OpenVMS - When downtime is not an option Scripting question Re: Supercomputer rankings Re: Supercomputer rankings Re: Tech support Re: Tech support VTJ V10 Re: VTJ V10 ---------------------------------------------------------------------- Date: 28 Jun 2007 07:13:49 -0500 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Message-ID: In article <5efqh9F36vpmjU1@mid.individual.net>, bill@cs.uofs.edu (Bill Gunshannon) writes: > > Within the language or as compiler options? For C, both. The compiler option is /member_alignment and the language option is #pragma member_alignment . I haven't used Pascal enough to know, but since every other compiler I've used on VMS allows me to control alignment either through compiler options or language statements I'd be real suprised if the Pascal compiler doesn't do both. ------------------------------ Date: 28 Jun 2007 07:16:58 -0500 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Message-ID: In article <1182976479.389977.301100@q69g2000hsb.googlegroups.com>, Doug Phillips writes: > > Why, to think that any computer company would expect their customers > to convert and rebuild all of their software, or buy all new app's > just to upgrade to newer hardware is ridiculous. I mean, what company > in their right mind would do that? Twice? Right, most of them expect their customers to throw out the baby with the bath water and invest in all new applications. In today's IT environment you buy COTS apps and put them on the platform. Platform change time includes buying a new copy of the same COTS app, or a replacement. I'm glad I don't work in that environment, but I think it has a much bigger piece of the market. I'll be happy as long as I can count on VMS to do what I need, no matter the size of its market share. ------------------------------ Date: Thu, 28 Jun 2007 12:36:10 +0000 (UTC) From: m.kraemer@gsi.de (Michael Kraemer) Subject: Re: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Message-ID: In article , koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: > In article <5efqh9F36vpmjU1@mid.individual.net>, bill@cs.uofs.edu (Bill > Gunshannon) writes: > > > > Within the language or as compiler options? > > For C, both. The compiler option is /member_alignment and the > language option is #pragma member_alignment . > #pragma isn't part of the language, it depends on the compiler, so it's just another way to apply a compiler flag. If it would be a standardized attribute like "volatile" or "static", that would be "part of the language". ------------------------------ Date: 28 Jun 2007 14:34:12 GMT From: bill@cs.uofs.edu (Bill Gunshannon) Subject: Re: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Message-ID: <5ehv74F390uk2U2@mid.individual.net> In article , koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: > In article <5efqh9F36vpmjU1@mid.individual.net>, bill@cs.uofs.edu (Bill Gunshannon) writes: >> >> Within the language or as compiler options? > > For C, both. The compiler option is /member_alignment and the > language option is #pragma member_alignment . > > I haven't used Pascal enough to know, but since every other compiler > I've used on VMS allows me to control alignment either through > compiler options or language statements I'd be real suprised if the > Pascal compiler doesn't do both. But my point was that this is not the language. This is a proprietary extension to a language. In PL/I I am fairly certain it was a part of the language specifically. Right, Tom? bill -- Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves bill@cs.scranton.edu | and a sheep voting on what's for dinner. University of Scranton | Scranton, Pennsylvania | #include ------------------------------ Date: Thu, 28 Jun 2007 08:21:34 -0700 From: "Tom Linden" Subject: Re: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Message-ID: On Thu, 28 Jun 2007 07:34:12 -0700, Bill Gunshannon wrote: > In article , > koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: >> In article <5efqh9F36vpmjU1@mid.individual.net>, bill@cs.uofs.edu (Bill >> Gunshannon) writes: >>> >>> Within the language or as compiler options? >> >> For C, both. The compiler option is /member_alignment and the >> language option is #pragma member_alignment . >> >> I haven't used Pascal enough to know, but since every other compiler >> I've used on VMS allows me to control alignment either through >> compiler options or language statements I'd be real suprised if the >> Pascal compiler doesn't do both. > > But my point was that this is not the language. This is a proprietary > extension to a language. In PL/I I am fairly certain it was a part of > the language specifically. Right, Tom? Correct. > > bill > -- PL/I for OpenVMS www.kednos.com ------------------------------ Date: 28 Jun 2007 16:35:34 GMT From: bill@cs.uofs.edu (Bill Gunshannon) Subject: Re: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Message-ID: <5ei6amF38n80dU1@mid.individual.net> In article , "Tom Linden" writes: > On Thu, 28 Jun 2007 07:34:12 -0700, Bill Gunshannon > wrote: > >> In article , >> koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: >>> In article <5efqh9F36vpmjU1@mid.individual.net>, bill@cs.uofs.edu (Bill >>> Gunshannon) writes: >>>> >>>> Within the language or as compiler options? >>> >>> For C, both. The compiler option is /member_alignment and the >>> language option is #pragma member_alignment . >>> >>> I haven't used Pascal enough to know, but since every other compiler >>> I've used on VMS allows me to control alignment either through >>> compiler options or language statements I'd be real suprised if the >>> Pascal compiler doesn't do both. >> >> But my point was that this is not the language. This is a proprietary >> extension to a language. In PL/I I am fairly certain it was a part of >> the language specifically. Right, Tom? > > Correct. Thank you. Nice to know I haven't lost too many of the little grey cells just yet. bill -- Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves bill@cs.scranton.edu | and a sheep voting on what's for dinner. University of Scranton | Scranton, Pennsylvania | #include ------------------------------ Date: 28 Jun 2007 12:01:57 -0500 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Message-ID: <3aJntITrNGE2@eisner.encompasserve.org> In article , m.kraemer@gsi.de (Michael Kraemer) writes: > > #pragma isn't part of the language, #pragma is a defined prepocessor keyword in the ANSI C language standard. ------------------------------ Date: 28 Jun 2007 12:02:42 -0500 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Message-ID: In article <5ehv74F390uk2U2@mid.individual.net>, bill@cs.uofs.edu (Bill Gunshannon) writes: > In article , > koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: >> In article <5efqh9F36vpmjU1@mid.individual.net>, bill@cs.uofs.edu (Bill Gunshannon) writes: >>> >>> Within the language or as compiler options? >> >> For C, both. The compiler option is /member_alignment and the >> language option is #pragma member_alignment . >> >> I haven't used Pascal enough to know, but since every other compiler >> I've used on VMS allows me to control alignment either through >> compiler options or language statements I'd be real suprised if the >> Pascal compiler doesn't do both. > > But my point was that this is not the language. This is a proprietary > extension to a language. In PL/I I am fairly certain it was a part of > the language specifically. Right, Tom? The provision for #pragma is a part of the language standard. ------------------------------ Date: 28 Jun 2007 17:15:10 GMT From: bill@cs.uofs.edu (Bill Gunshannon) Subject: Re: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Message-ID: <5ei8kuF38m8poU1@mid.individual.net> In article , koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: > In article <5ehv74F390uk2U2@mid.individual.net>, bill@cs.uofs.edu (Bill Gunshannon) writes: >> In article , >> koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: >>> In article <5efqh9F36vpmjU1@mid.individual.net>, bill@cs.uofs.edu (Bill Gunshannon) writes: >>>> >>>> Within the language or as compiler options? >>> >>> For C, both. The compiler option is /member_alignment and the >>> language option is #pragma member_alignment . >>> >>> I haven't used Pascal enough to know, but since every other compiler >>> I've used on VMS allows me to control alignment either through >>> compiler options or language statements I'd be real suprised if the >>> Pascal compiler doesn't do both. >> >> But my point was that this is not the language. This is a proprietary >> extension to a language. In PL/I I am fairly certain it was a part of >> the language specifically. Right, Tom? > > The provision for #pragma is a part of the language standard. So is #define but what comes next is totally up to the user and not part of the language spec. You can't reasonably expect any #pragma to exist in any other compiler so it anything that follows it is a proprietary extension. The original point was that the PLI/I language took alignment into consideration and included alignment instructions as a part of the language which means it is reasonable to expect a program using it to be somewhat portable. C and Pascal do not share this feature. Any concern for alignment is little more than an after- thought. bill -- Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves bill@cs.scranton.edu | and a sheep voting on what's for dinner. University of Scranton | Scranton, Pennsylvania | #include ------------------------------ Date: Thu, 28 Jun 2007 07:50:23 -0400 From: "Main, Kerry" Subject: RE: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Message-ID: > -----Original Message----- > From: Stephen Hoffman [mailto:Hoff@HoffmanLabs-RemoveThis-.Org] > Sent: June 26, 2007 8:44 PM > To: Info-VAX@Mvb.Saic.Com > Subject: Re: And the question was? (Re: Amazing, two new articles on > Computerworld.com actual mention OpenVMS!) actual mention OpenVMS!) > actual mention OpenVMS!) >=20 > Main, Kerry wrote: >=20 > > Re: "modern developer" > > > > Well, if modern tools means SOA type technologies, then imho, I have > to > > smile at this. > > > > While there are no doubt a few areas where these technologies might > be > > useful, the sad reality is that App developers and tools vendors are > > telling the world "move to SOA or be lost forever", but they have no > > idea of how really tough this is and/or the huge culture shift in > their > > entire business that this requires. >=20 > There are some seriously cool tools in this area, powerful and > effective tools and techniques. Surprisingly little code, for what > you > get, too. Stuff I've been using, and that have made me more efficient > and effective than I was with older techniques and tools. > Enhancements > and improvements are the nature of the business, after all. >=20 > > Way to much hype, but "modern" App folks are off saying "we need SOA > > tools, we need SOA technologies ..we need SOA staff .." >=20 > There's always been hype and FUD. Key here is whether a > client-server, three-tier client-server, middleware, SOA or whatever > you > choose to call the particular design or tool or technique moves the > business forward. >=20 Absolutely. Like I stated, there certainly is a place for new technologies and tools as that is the nature of becoming more efficient. > Dismissing these tools out of hand is as hazardous as blindly > leaping > into the unknown. (My grandfather used a wooden hammer and nails. I > use a nail gun. Had my grandfather had the opportunity, he would have > purchased and used the first nail gun he could have afforded. I still > have a hammer around, and it gets some use. That older compiler I > have > around, too, still gets some use.) >=20 Yep, new tools and technologies are good, but one needs to understand the bigger cultural and organization challenges when making major directional changes. > > Reality check - think about the issues that DCE and common data > > dictionary initiatives had. Anyone ever experienced how difficult it > is > > for multiple App groups to share stds, processes, and agree on data > > models? >=20 > If you're working in an organization that's fairly rigid, that can > certainly be the case. >=20 Usually, if there is a very strong centralized IT group, then SOA (or DCE - SOA's older twin from the past) has a much larger chance of success vs a distributed IT org.=20 > I've been targeting modular designs for components for a while, and > object oriented (OO) design -- for all its faults -- does tend to > force > encapsulation and modular programming. While it's possible to > implement > modular programming in most languages, OO can be a particular > advantage > in specific development environments; it tends to force a degree of > discipline. >=20 > The first large-scale project I worked on that used modular > components was back around 1987 or so, and the encapsulated UI and > internal communications and the networking most definitely expedited > development and deployment. I was then writing what would now be > known > as middleware, or SOA. And the effort involved here gotten both > easier > and -- due to the ever-increased scale of the projects -- harder since > then. >=20 > Had I to do it over again, I'd be using XML and such. >=20 > > SOA is all this with even more process and culture changes required. > And > > all this at a time when the business is demanding massive cuts in IT > > spending. >=20 > Pressure to increase output and to decrease costs is nothing new. > The same pressures also apply to tasks including purchasing servers, > purchasing companies, or to most any other business expenses. (And > then > there's the furor over whether IT is a competitive advantage -- and in > various cases, it is not. Nicholas Carr ignited a maelstrom on this > topic a while back.) >=20 Yep and one also needs to examine why DCE and common data dictionaries were not successful in the past as well. These major initiative failures had little to do with tools and technologies. > > Anyway, perhaps a bit OT and not so much related to OpenVMS, but > when > > ever I hear this "modern developer" term, it starts my blood > boiling. At > > some point, someone has to tell the King (industry "modern > developer") > > they are wearing no clothes. >=20 > Watch out: some few of those developers are wearing some very > serious > and very modern armor. Some of what I've been working with recently > is > a whole lot less coding effort for a whole lot more output; it's far > more efficient. And far more competitive. >=20 >=20 Well, some would argue that in its time, the App promoters of DCE and common data dictionaries were also very well armed. As an example, for an enterprise SOA architecture strategy to be successful, various Application and OPS groups in different Business Units need to agree on how they will share code, libraries, how they will implement a common data security strategy, how they will handle numerous different data model differences (that is where common data dictionary failed), how will access to existing data be shared, how they will handle common authentication and auditing, how they will Operationally manage all of these different environments (monitoring, managing, backups, archiving etc), how will they handle things like data encryption, what will all of this mean to the network traffic bandwidth etc... This is where the culture, politics and real challenges of SOA (aka DCE) are. All of the above is required when things like SOX, HIPPA, FERPA regulatory and legal compliance requirement audits are being demanded and have much higher visibility than ever in the past. In some cases, failing to meet these requirements can result in jail time and/or big time fines for senior execs so these are high priority items. All of the above is happening when Data Center and server consolidation initiatives are being driven by the IT Operations groups. And oh yes, the BU's are also demanding massive cuts in IT spending at the same time as all of the above is happening. So, while I totally agree with new tools and technologies, one needs to balance these with the realities of the above. Unfortunately, many companies App groups are promoting SOA (J2EE, .Net etc) and OO technologies without fully understanding the previous points. Regards Kerry Main Senior Consultant HP Services Canada Voice: 613-592-4660 Fax: 613-591-4477 kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20 OpenVMS - the secure, multi-site OS that just works. ------------------------------ Date: Thu, 28 Jun 2007 11:13:41 -0400 From: John Reagan Subject: Re: And the question was? (Re: Amazing, two new articles on Computerworld.com ac Message-ID: Bill Gunshannon wrote: > In article , > koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: > >>In article <5efqh9F36vpmjU1@mid.individual.net>, bill@cs.uofs.edu (Bill Gunshannon) writes: >> >>>Within the language or as compiler options? >> >> For C, both. The compiler option is /member_alignment and the >> language option is #pragma member_alignment . >> >> I haven't used Pascal enough to know, but since every other compiler >> I've used on VMS allows me to control alignment either through >> compiler options or language statements I'd be real suprised if the >> Pascal compiler doesn't do both. > > > But my point was that this is not the language. This is a proprietary > extension to a language. In PL/I I am fairly certain it was a part of > the language specifically. Right, Tom? > > bill > > For C, the standard for struct just says that fields have addresses that increase in the order in which they are declared. The standard also says that there may be unnamed padding within (including the end) of a structure object,just no padding at the beginning. For Pascal, the standard doesn't try to specify a physical form at all. It is just says that the various fields have a list of known states (ie, all integer values plus the undefined state) and that the fields have one and only one state associated with them. A compiler can allocate them in any order it felt like or even not bother allocating fields that are unused. OpenVMS Pascal has several language extensions to control the alignment, position, and allocation of fields in a record. Beyond the various language standards, the OpenVMS Calling Standard does require additional record layout behavior of compilers. -- John Reagan OpenVMS Pascal/Macro-32/COBOL Project Leader Hewlett-Packard Company ------------------------------ Date: Thu, 28 Jun 2007 15:09:37 +0200 From: "Walter Kuhn" Subject: Re: Catch OPCOM messages (in PASCAL) Message-ID: <4683b313$0$2257$91cee783@newsreader01.highway.telekom.at> Many thanks to the group! It's working!!! Walter "Walter Kuhn" schrieb im Newsbeitrag news:46814a64$0$22641$91cee783@newsreader02.highway.telekom.at... > Hello group, > > I am trying to catch opcom messages from a (PASCAL) program, but it > doesn't work. The idea of the program is as follows: > > 1) Create a LTAx device > 2) Create a mailbox and associate it with the LTA device > 3) Set up a QIO on the mailbox > 4) Enable operator on the LTA device with $SENDOPR > 5) The program expects the operator messages on the mailbox. Right? > > The program (150 lines) is appended to this message. > Any idea? > > best regards & thank you > Walter > > ---------------------------------------------------------------------------------------------------------------------------- > > [INHERIT ('SYS$LIBRARY:STARLET', > 'SYS$LIBRARY:PASCAL$LIB_ROUTINES')] > PROGRAM OPCOM (OUTPUT); > > TYPE > > ubyte = [BYTE] 0..255; > uword = [WORD] 0..65535; > iosb = PACKED RECORD > condval: uword; > transcnt: uword; > dvi: UNSIGNED; > END; > > tOPCbuf = PACKED RECORD > CASE BOOLEAN OF > TRUE: (ms_type: ubyte; > ms_enab: ubyte; > ms_fil1: ubyte; > ms_fil2: ubyte; > ms_mask: INTEGER; > ms_devunit: uword; > ms_devname_len: ubyte; > ms_devname: PACKED ARRAY [1..19] OF CHAR); > FALSE: (str: PACKED ARRAY [1..30] OF CHAR); > END; > > VAR > > OPCbuf: tOPCbuf; > > devunit: INTEGER; > devunit_c: VARYING [5] OF CHAR; > devname: VARYING [19] OF CHAR; > devchan: [VOLATILE] uword; > > mbxname: VARYING [19] OF CHAR; > mbxchan: [VOLATILE] uword; > mbxchar: [VOLATILE] packed array [1..255] OF CHAR; > mbxiosb: [VOLATILE] iosb; > > msgsiz: INTEGER; > bufquo: INTEGER; > > > [ASYNCHRONOUS,UNBOUND] PROCEDURE check (s: INTEGER); > BEGIN > IF NOT ODD (s) THEN LIB$SIGNAL (s); > END; > > > [ASYNCHRONOUS,UNBOUND] PROCEDURE mbxast; > BEGIN { mbxast } > LIB$PUT_OUTPUT ('mbxast ' + > DEC (mbxiosb.condval) + ' ' + > DEC (mbxiosb.transcnt) + ' ' + > DEC (mbxiosb.dvi) + ' ' + > DEC (ORD (mbxchar[1]))); { test } > > check ($QIO (func := IO$_READVBLK, > chan := mbxchan, > iosb := mbxiosb, > astadr := %IMMED mbxast, > p1 := mbxchar, > p2 := 255)); > END { mbxast } ; > > > BEGIN { main } > > { > { Create LTAx device and assign it with a mailbox > {} > > msgsiz := 255; > bufquo := 10 * msgsiz; > > check (LIB$ASN_WTH_MBX ('LTA0:', msgsiz, bufquo, devchan, mbxchan)); > > WRITELN ('devchan = ', devchan: 1); > WRITELN ('mbxchan = ', mbxchan: 1); > > { > { Set up a QIO on mailbox > {} > > check ($QIO (func := IO$_READVBLK, > chan := mbxchan, > iosb := mbxiosb, > astadr := %IMMED mbxast, > p1 := mbxchar, > p2 := 255)); > > { > { Prepare command buffer for $SNDOPR > {} > > OPCbuf := zero; > OPCbuf.ms_type := opc$_rq_terme; { type of operator request } > OPCbuf.ms_enab := 1; { enable } > OPCbuf.ms_mask := OPC$M_NM_CARDS + > OPC$M_NM_CENTRL + > OPC$M_NM_SECURITY + > OPC$M_NM_CLUSTER + > OPC$M_NM_DEVICE + > OPC$M_NM_DISKS + > OPC$M_NM_NTWORK + > OPC$M_NM_TAPES + > OPC$M_NM_PRINT; { operator type } > > { > { Get terminal unit number for $SNDOPR buffer > {} > > check (LIB$GETDVI (DVI$_UNIT, devchan, , devunit)); > WRITELN ('lib$getdvi: devunit = ', devunit: 1); > OPCbuf.ms_devunit := devunit; > > { > { Get terminal name for $SNDOPR buffer > {} > > check (LIB$GETDVI (DVI$_FULLDEVNAM, devchan, , , devname.body, > devname.length)); > WRITELN ('lib$getdvi: devname = ', devname); > > { > { Get mailbox name (for info only) > {} > > check (LIB$GETDVI (DVI$_FULLDEVNAM, mbxchan, , , mbxname.body, > mbxname.length)); { Mailbox name } > WRITELN ('lib$getdvi: mbxname = ', mbxname); > > { > { Remove unit number from terminal name (for $SNDOPR buffer) > {} > > WRITEV (devunit_c, devunit: 1); > devname := SUBSTR (devname, 1, INDEX (devname, devunit_c) - 1); > OPCbuf.ms_devname_len := devname.length; > OPCbuf.ms_devname := devname.body; > > { > { Enable operator reply > {} > > check ($SNDOPR (OPCbuf.str, mbxchan)); > > check ($HIBER); > > OPCbuf.ms_enab := 0; { disable } > check ($SNDOPR (OPCbuf.str, mbxchan)); > > check ($dassgn (mbxchan)); > check ($dassgn (devchan)); > > END { main } . > ------------------------------ Date: Thu, 28 Jun 2007 17:15:51 +0100 From: Anton Shterenlikht Subject: creating firmware floppies on FreeBSD or VMS Message-ID: <20070628161551.GA22806@mech-aslap33.men.bris.ac.uk> I'd like to update the firmware to 7.3 on my ds10l. I'd like to use the floppies route. I'd like to make these floppies either on VMS or on FreeBSD. Now, I don't seem to be able to create the FAT floppies with binary files on my FreeBSD system. If I just use # fdformat -f 1440 -y /dev/fd0 # newfs_msdos /dev/fd0 and copy the files with cp, then I probably break the binary files, because I get the following offset error using disk1: >>>lfu Checking dqb0.0.1.13.0 for the option firmware files. . . dqb0.0.1.13.0 has no media present or is disabled via the RUN/STOP switch Checking dva0.0.0.0.0 for the option firmware files. . . Option firmware files were not found on CD or floppy. If you want to load the options firmware, please enter the device on which the files are located(ewa0), or just hit to proceed with a standard console update: dva0 Please enter the name of the options firmware files list, or Hit to use the default filename (ds10io.txt) : ds10fw.txt Copying ds10fw.txt from dva0. . . Copying DS10SRM from dva0. . . Cannot access data beyond an offset of 1474559 Offset requested was 91257344 Please insert next floppy containing the options firmware, Hit when ready. Or type DONE to abort. ************************************************ On the other hand if I use dd, then the floppy is probably in ufs, because I cannot even read the text file: >>>lfu Checking dqb0.0.1.13.0 for the option firmware files. . . dqb0.0.1.13.0 has no media present or is disabled via the RUN/STOP switch Checking dva0.0.0.0.0 for the option firmware files. . . Option firmware files were not found on CD or floppy. If you want to load the options firmware, please enter the device on which the files are located(ewa0), or just hit to proceed with a standard console update: dva0 Please enter the name of the options firmware files list, or Hit to use the default filename (ds10io.txt) : ds10fw.txt Couldn't read ds10fw.txt from dva0 *********************************************************** Doing newfs_msdos after dd obviously erases the files, and doing dd after newfs erases the fat filesystem. What do I do wrong? How can I create a fat floppy in vms? I searched under HELP INIT, but cannot see any related info. There is some info on how to make VMS bootable floppy in FAQ, but I don't know if that will work for firmware upgrade files. thanks a lot anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ------------------------------ Date: 28 Jun 2007 16:47:40 GMT From: bill@triangle.cs.uofs.edu (Bill Gunshannon) Subject: Re: creating firmware floppies on FreeBSD or VMS Message-ID: <5ei71cF38n80dU2@mid.individual.net> In article <20070628161551.GA22806@mech-aslap33.men.bris.ac.uk>, Anton Shterenlikht writes: > I'd like to update the firmware to 7.3 on my ds10l. I'd like to > use the floppies route. I'd like to make these floppies either on > VMS or on FreeBSD. > > Now, I don't seem to be able to create the FAT floppies with binary > files on my FreeBSD system. > > If I just use > # fdformat -f 1440 -y /dev/fd0 > # newfs_msdos /dev/fd0 Try: cd /usr/ports/emulators/mtools make install And then you can use: mattrib ATTRIB change MSDOS file attribute flags mcd CD change MSDOS directory mcopy COPY copy MSDOS files to/from Unix mdel DEL/ERASE delete an MSDOS file mdir DIR display an MSDOS directory mformat FORMAT add MSDOS filesystem to a low-level format mlabel LABEL make an MSDOS volume label. mmd MD/MKDIR make an MSDOS subdirectory mrd RD/RMDIR remove an MSDOS subdirectory mread COPY low level read (copy) an MSDOS file to Unix mren REN/RENAME rename an existing MSDOS file mtype TYPE display contents of an MSDOS file mwrite COPY alias for mcopy, will be removed soon bill -- Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves bill@cs.scranton.edu | and a sheep voting on what's for dinner. University of Scranton | Scranton, Pennsylvania | #include ------------------------------ Date: Thu, 28 Jun 2007 18:31:07 +0200 From: =?ISO-8859-1?Q?Jean-Fran=E7ois_Pi=E9ronne?= Subject: Re: cURL 7.16.3 available Message-ID: <4683e256$0$21694$426a34cc@news.free.fr> Great, is there any interest to include pycURL in Python for VMS? I remember it was request once. From http://pycurl.sourceforge.net/ """ PycURL is a Python interface to libcurl. PycURL can be used to fetch objects identified by a URL from a Python program, similar to the urllib Python module. PycURL is mature, very fast, and supports a lot of features. """ JFP ------------------------------ Date: Thu, 28 Jun 2007 07:59:10 -0400 From: "Main, Kerry" Subject: RE: HP "Support" for OpenVMS Message-ID: > -----Original Message----- > From: Kel Boyer [mailto:KelPhaedrus@gmail.com] > Sent: June 25, 2007 6:19 PM > To: Info-VAX@Mvb.Saic.Com > Subject: Re: HP "Support" for OpenVMS >=20 > On Jun 25, 9:16 am, "johnhreinha...@yahoo.com" > wrote: > > On Jun 25, 11:16 am, Kel Boyer wrote: > > > > > > > > > An interview with Ann Livermore. I find the last sentence of this > clip > > > rather telling. > > > > > = >http://computerworld.com/action/article.do?command=3DviewArticleBasic&t > ... > > > > > Q: Expertise and quality are a big issue. Last fall, I spoke with > two > > > high-profile HP partners who are OpenVMS consultants. They said > the > > > support technicians in places like China and India don't have the > > > required expertise and aren't getting the training they need. > What's > > > your response? > > > > > A: My view is that customer satisfaction and loyalty are at the > heart > > > of everything that HP does and stands for, and that the long-term > > > success of almost any services business, and more broadly [of] > almost > > > any corporation, has to do with how well they satisfy customers. > > > > > No matter where your resources are, at times you'll have an > employee > > > who, for some reason, may not meet the quality or performance > > > standard. What we try to do is take the feedback and address it. > We > > > actually followed up on the feedback from those partners to see if > we > > > had a training issue specifically with some individuals, or if we > had > > > a turnover issue, or what the nature was. In particular for our > > > OpenVMS customers, we are very focused on our installed base. We > want > > > our installed base to be happy, and if or when they ever want to > > > migrate, we want them to migrate to another HP platform. > > > > This is old news, Kel. > > > > See the long and meandering thread from June 19th -- > >http://groups.google.com/group/comp.os.vms/browse_frm/thread/6b549c01 > ... >=20 > Ah, so it is! >=20 > I see my own feelings were mirrored here. I guess I should have > expected no less. Bottom line summary is that HP says the same thing to HP-UX Cust's moving to Linux. IBM says the same thing when looking at AIX to Linux migrations. Sun says the same about Solaris to Linux. Simple business logic dictates that platform vendors wants to keep Customers on their platform products regardless of which OS they decide to adopt. Nothing really earth shattering here. Regards Kerry Main Senior Consultant HP Services Canada Voice: 613-592-4660 Fax: 613-591-4477 kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20 OpenVMS - the secure, multi-site OS that just works. ------------------------------ Date: Thu, 28 Jun 2007 18:13:33 +0200 From: =?ISO-8859-1?Q?Jean-Fran=E7ois_Pi=E9ronne?= Subject: Re: mysql on vms Message-ID: <4683de38$0$26415$426a34cc@news.free.fr> ChrisSharman a écrit : > Talking to myself - first sign of madness. > > The 5.1 kit tries to run run_mysqld.com - which doesn't exist. run _mysqld.com is provide as a template: run_mysqld.com_template It was requested to customize how mysql is launch. > Hacked the 4.1 one ... > Got this message, so dropped --innodb-safe-binlog > 070628 12:58:25 [ERROR] > /$2$DKA0/clu/clu/webenv/mysql051/vms/bin/mysqld.exe: unknown option > '--innodb-safe-binlog' > mysql options 4.1 and 5.1 are different use the provided template. > next run, got: > 070628 13:00:00 [Warning] No argument was provided to --log-bin, and > --log-bin-index was not used; so replication may break when thi > s MySQL server acts as a master and has his hostname changed!! Please > use '--log-bin=equus-bin' to avoid this problem. >[snip] Do you launch first_start_mysqld.com then load the mysql system table ? There is a video record of how to install mysql 5.1 on a VMS system. http://vmspython.dyndns.org/anonymous/kits/mysql051_installation.wmv I and others site run MySQL 4.1.14 and MySQL 5.1.11 on the same system without any problem. $ sh sys/proc=my* OpenVMS V7.3-2 on node BISOU 28-JUN-2007 18:06:37.67 Uptime 6 05:16:52 Pid Process Name State Pri I/O CPU Page flts Pages 20200450 MYSQL051_SERVER HIB 5 1012953 0 00:27:32.85 74553 10458 M 20200451 MYSQL_SERVER HIB 5 1676485 0 00:32:46.99 11832 6995 M Trace of a run: 060914 14:45:58 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 060914 14:46:12 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 186609491. InnoDB: Doing recovery: scanned up to log sequence number 0 186609491 InnoDB: Last MySQL binlog file position 0 12483, file name ./mysql-bin.000001 060914 14:46:19 InnoDB: Started; log sequence number 0 186609491 /DSA200/TOOLS/MYSQL051/VMS/BIN/mysqld.exe: Table 'general_log' is marked as cras hed and should be repaired /DSA200/TOOLS/MYSQL051/VMS/BIN/mysqld.exe: Table 'slow_log' is marked as crashed and should be repaired 060914 14:46:22 [Note] Recovering after a crash using mysql-bin 060914 14:46:22 [Note] Starting crash recovery... 060914 14:46:22 [Note] Crash recovery finished. 060914 14:46:27 [Note] /DSA200/TOOLS/MYSQL051/VMS/BIN/mysqld.exe: ready for conn ections. Version: '5.1.11-beta-log' socket: '' port: 3307 Source distribution 060914 14:46:27 [Note] SCHEDULER: Manager thread booting 060914 14:46:27 [Note] SCHEDULER: Loaded 0 events 060914 14:46:27 [Note] SCHEDULER: Suspending operations As recommended by MySQL Labs migration from 4.1 to 5.1 should be done using unloading database from 4.1 (using mysqlsump) then reloading a fresh 5.1 database. JF ------------------------------ Date: Thu, 28 Jun 2007 16:57:41 GMT From: Chris Sharman Subject: Re: mysql on vms Message-ID: <9MRgi.30174$aS5.19947@fe1.news.blueyonder.co.uk> Jean-François Piéronne wrote: > ChrisSharman a écrit : >> Talking to myself - first sign of madness. >> >> The 5.1 kit tries to run run_mysqld.com - which doesn't exist. > run _mysqld.com is provide as a template: run_mysqld.com_template Ah, missed that - just looked for .com > mysql options 4.1 and 5.1 are different use the provided template. > > Do you launch first_start_mysqld.com then load the mysql system table ? No - really wanted an upgrade, importing my existing setup - users and all. > http://vmspython.dyndns.org/anonymous/kits/mysql051_installation.wmv Ah - a proprietary format I can't read. Text would be better, I think. > I and others site run MySQL 4.1.14 and MySQL 5.1.11 on the same system > without any problem. > > As recommended by MySQL Labs migration from 4.1 to 5.1 should be done > using unloading database from 4.1 (using mysqlsump) then reloading a > fresh 5.1 database. Presumably with independent tables - no ability to share data between versions? I wasn't clear exactly how to make them coexist, or whether I needed my.cnf, or what. At 22 hours to load 1.75M records, & corrupting on first access (a simple select), I'm assuming vms/mysql isn't suitable for the project in hand (DHL routing). I was using MyISAM, because the tables are all readonly after the initial load. Thanks Chris ------------------------------ Date: Thu, 28 Jun 2007 19:10:20 +0200 From: =?ISO-8859-1?Q?Jean-Fran=E7ois_Pi=E9ronne?= Subject: Re: mysql on vms Message-ID: <4683eb87$0$967$426a34cc@news.free.fr> Chris Sharman a écrit : > Jean-François Piéronne wrote: >> ChrisSharman a écrit : >>> Talking to myself - first sign of madness. >>> >>> The 5.1 kit tries to run run_mysqld.com - which doesn't exist. >> run _mysqld.com is provide as a template: run_mysqld.com_template > > Ah, missed that - just looked for .com > >> mysql options 4.1 and 5.1 are different use the provided template. >> >> Do you launch first_start_mysqld.com then load the mysql system table ? > > No - really wanted an upgrade, importing my existing setup - users and all. > >> http://vmspython.dyndns.org/anonymous/kits/mysql051_installation.wmv > > Ah - a proprietary format I can't read. Text would be better, I think. > When I record the demo the only tool to do this was only able to generate a wmv file format. Since, I have found other tools able to generate others format, but I aven't record another session. >> I and others site run MySQL 4.1.14 and MySQL 5.1.11 on the same system >> without any problem. >> >> As recommended by MySQL Labs migration from 4.1 to 5.1 should be done >> using unloading database from 4.1 (using mysqlsump) then reloading a >> fresh 5.1 database. > > Presumably with independent tables - no ability to share data between > versions? No. > I wasn't clear exactly how to make them coexist, or whether I needed > my.cnf, or what. > You have both server running on your system, just listening on a different port. Again the demo show this. > At 22 hours to load 1.75M records, & corrupting on first access (a > simple select), I'm assuming vms/mysql isn't suitable for the project in > hand (DHL routing). I was using MyISAM, because the tables are all > readonly after the initial load. > MyISAM is know to be unreliable on VMS, only InnoDB work fine. It was reported from other sites that MyISAM on 5.1 seem to work much better than on 4.1, but I don't know if it is still buggy, I don't remember any problem reported on 5.1. JF ------------------------------ Date: Thu, 28 Jun 2007 05:06:14 -0700 From: Andrew Subject: Re: OpenVMS - When downtime is not an option Message-ID: <1183032374.908727.11410@c77g2000hse.googlegroups.com> On 26 Jun, 18:16, Russell Wallace wrote: > Andrew wrote: > > Not quite sure why this would be that impressive, VCS supports > > Solaris, AIX, HP-UX, Windows and Linux and has done for years. > > Does it do the same job (failover with no data loss, of arbitrary third > party software)? If so, I'm impressed at that too. > In so much as the solution demonstrated by HP provides for no loss of data so does VCS. VCS supports a number of apps out of the box such as Oracle SAP etc but is also allows you to build agents for apps which do not come with a pre-built agent. Of course if your third party app is not writing data synchronously then all bets are off. > -- > "Always look on the bright side of life." > To reply by email, replace no.spam with my last name. ------------------------------ Date: 28 Jun 2007 07:08:13 -0500 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: OpenVMS - When downtime is not an option Message-ID: In article <5eflf4F389bctU1@mid.individual.net>, bill@cs.uofs.edu (Bill Gunshannon) writes: > > There you go with all the geek speak again. What will management > types see when they watch that video? Guess again. I make recommendations and I've never had any of my recommendations overruled. ------------------------------ Date: Thu, 28 Jun 2007 06:18:42 -0700 From: AEF Subject: Re: OpenVMS - When downtime is not an option Message-ID: <1183036722.265124.192550@u2g2000hsc.googlegroups.com> On Jun 27, 9:02 am, b...@cs.uofs.edu (Bill Gunshannon) wrote: > In article <5BSqJKYqa...@eisner.encompasserve.org>, > koeh...@eisner.nospam.encompasserve.org (Bob Koehler) writes: > > > In article <54bb4$468246e6$cef8887a$31...@TEKSAVVY.COM>, JF Mezei writes: > > >> And here is a problem. Because it takes a lot of windows boxes to > >> accomplish simple tasks, Windows gets an exagerated market share because > >> that is counted based on number of boxes, not how much work they do. > > > But you CIO doesn't care because he can buy 2 Windows boxes for the > > price of a VMS box and have money left over to take the department > > out to lunch. > > > So if you need three VMS boxes to have a VMScluster that keeps quorum > > in a share-everything way when a datacenter goes down and six Windows > > boxes to convince the CIO he's getting the same thing in a > > shared-nothing way, he's happy. > > Ummm..... Didn't the exploding datacenter video that has everybody > in this group dancing in the street show Windows systems recovering > without data loss just like the VMS system, only a little bit slower? > Considering that the alternative int he past has been recovery mesaured > in days, weeks or even months I wold bet that most management types > would be more than pleased with the recovey time of the Windows boxes > in this demo. I know everyone loved it, but you do realize that even > though it was a rare mention of VMS it basicly showed that HPUX, Linux > and even Windows can do the same thing. Not so sure that was a big > help to extending the life of VMS. > > bill > > -- > Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves > b...@cs.scranton.edu | and a sheep voting on what's for dinner. > University of Scranton | > Scranton, Pennsylvania | #include Well, you can look at it different ways. Some might be impressed that HP came up with a solution that allowed even Windows to pass the test. Also, some might wonder just why VMS did so much better than the rest and think that there might be something more to VMS that the others don't have. The devil is in the details. Of course this was more to demonstrate HP's "disaster-proof" solution more than anything else. Still, no one can complain that OpenVMS didn't get fair mention with the other OSes! As far as extending the life of VMS, it shoore kent hoyt! And this draws attention to the white papers about each OS. That can't hurt. No, we're not out of the woods yet, but I'm still dancing! AEF ------------------------------ Date: 28 Jun 2007 14:30:52 GMT From: bill@cs.uofs.edu (Bill Gunshannon) Subject: Re: OpenVMS - When downtime is not an option Message-ID: <5ehv0sF390uk2U1@mid.individual.net> In article , "Main, Kerry" writes: >> -----Original Message----- >> From: bill@cs.uofs.edu [mailto:bill@cs.uofs.edu] On >> Behalf Of Bill Gunshannon >> Sent: June 27, 2007 8:33 AM >> To: Info-VAX@Mvb.Saic.Com >> Subject: Re: OpenVMS - When downtime is not an option >>=20 > > [snip...] > >> > If Windows server consolidation were really really taken to the >> limit, >> > you might find Windows has a small presence in the real data centres >> > because like for unix and vms and MVS, they'd have one box to do >> their work. >>=20 >> If Windows were consolidated at the rate of 10:1 it would still >> outnumber >> VMS by at least 100:1. People here really need to face reality. >> Windows >> is not as bad as you would like to think. Just because a bunch of >> home >> machines (mostly running the original Windows install they came with) >> get >> hacked doesn't mean that the boxes in the datacenter are that easy to >> break. >>=20 >> bill >>=20 > [snip...] > > Bill, > > What upsets readers on this list is when people like you make statements > like "Windows is not as bad as people here state that it is" when in > fact many of the readers here manage mission critical environments and > the concept of testing applications against *monthly* security patches > released by the host vendor is just plain ludicrous.=20 Yeah, well I "manage mission critical environments" to unless you don't consider DOD to be "mission critical". :-) In a mell managed system we just don't see the stuff you keep spouting. > > Readers here take security patches seriously and ensure they get applied > asap. So does DOD. :-) > This might happen once or twice every few years with OpenVMS. > Could be better? Possibly, but 5-20 security patches every month with > Linux and Windows? Most of which can be applied with no impact on operations. You know, when you haev 100,000 machines all running the same "mandated and un- changable) baseline you really don't need to test a patch on every box. The central authority tests against the baseline and then pushes the patch to all the other boxes. > > Then folks like you state "Windows can do the same job as OpenVMS.." Can and does. Every day in the real world. > > I deal with Windows, UNIX and OpenVMS environments and during > consolidation engagements talk all the time to Operations / Apps groups > and their managers about their major challenges... getting Windows > servers and the associated huge management issues under control is by > far the absolute biggest issue raised by these groups. When looking at > server consolidation, the number of Wintel server consolidation targets > is usually something like 70-80% Wintel as the primary focus today.=20 > > The readers here on this newsgroup are not from the "just reboot it" > stream of managing IT. Neither is DOD. (Well, maybe the Navy....) > When a problem occurs on OpenVMS, it is usually > thoroughly analyzed to ensure it does not happen again. Detailed > register information is available in system error logs so you can decode > which bits are set in which device registers. This provides one with the > ability to properly troubleshoot a problem down to a bus or device > level. > > I am sorry if it bothers you, Theonly thing that bothers me is people who bitch about FUD all the time tossing so much of it around. > but you seem to be unique in not having > the same challenges in operationally managing large numbers of Wintel > servers as most other med to large Customers today. Hardly unique. > It is not to say IT > is not that important in a University environment (I know it is), but it > just does not compare to many mission critical environments in private > industry today (e.g. OpenVMS lottery I was at a number of weeks here in > Canada measured down time during bigger pots at $1.5M/hr.) The University is not my only job. In my second job downtime might be measured in body counts, not dollars. > Check this out for what challenges the real world is facing today: > http://www.vista-control.com/itanium_success.htm > "Los Alamos, February 15th. 2007 After implementing mission-critical > systems on Windows-based computers for many years, a customer > experienced a virus in one of these systems that shut down production > for two days while the infected systems were diagnosed, restored and > tested. The impact was that plant production was severely impacted at no > small cost. Despite internal opposition because of the established > standard, Vsystem on HP Itanium servers running OpenVMS was chosen for > the next system to be replaced." You keep trotting out the same old tired examples. I read it. Not impressed. The fact that a virus got into the system is a management issue and nothing more. In January I went to a place where several thousand people gathered. Most bringing their laptops with them from their homestation. We had built a network, we integrated all these machines into this network. These machines included some that came from places not even under US control. During the entire operation we were actively targeted by determined (and well trained and ex- perienced) intruders. There were no virus incidents. There were no crashes or outages that could be blamed on Windows (the only real outage we had was network related and involved somebody doing something nasty to a CISCO box because they didn't know what they were doing. Windows worked flawlessly running lot's of intense applications. Go figure..... > > Another major issue - The reality is that the plain fact is that the > most common method of troubleshooting Windows servers today is to simply > reboot it. Even those who have experience with other platforms look at > Windows event logs and find minimal information beyond a basic cryptic > message (e.g. sample error - scsi error xxxx0906, which means not a > whole lot if you have 4 or 5 different scsi devices on 2 or 3 different > SCSI buses). This type of error means they will likely have to just > reboot the server. During the entire operation there was only one reboot of the servers and that was after a critical update was pushed down to us. This notion that Windows boxws have to be rebooted all the time is based on totally open and uncontrolled desktops. Not properly managed systems. > > When the folks here state Windows servers do not have the same bullet > proof operational capabilities of OpenVMS, they are usually talking from > experience and dealing with OpenVMS and "hardened" Wintel server > environments.=20 If your machine can be infected by a virus in any of the usual means, it isn't "hardened". > > It is not OS religion that drives the "Windows can not match OpenVMS" > statements in this newsgroup, but rather a form of educating the less > enlightened who do not really understand mission critical support > requirements. I am not saying Windows can match VMS. There is no doubt that VMS can do things that Windows can't. But the Windows picture is nowhere near as bleak as people here try to paint it. And when you consider all things, in the long run the few things that VMS does so much better than Windows are becoming less important to businesses. But when you base your decisions on bogus data, what do you expect. > > Unfortunately, sometimes it is like talking to teenagers - "talk to the > hand..". These "kids" are just going to have to go out and experience > for themselves what those with more experience tried to tell them in the > first place. Like I said, I work with "mission critical" systems, too. Windows systems can be secured. The users may not be happy that they can't play MS Hearts, but the box can be closed up made secure and made stable. But then, I don;t expect you or anyone else here to ever accept that fact. It's much easier to point at something like that Los Alamos article and interpolate that all systems are run just like it. Reality is otherwise. There are a lot of badly managed Windows systems. they are badly managed because the users don't care. If the same sloppiness were applied to VMS is would be just as vulnerable. This has been pointed out repeatedly. there are Windows boxes out there with no password on the administrator account and with the user running everything from the administrator account to boot. The sheer number of Windows boxes and the fact that so many of them are in the hands of and totally under the control of users guarantees this. It doesn't make Windows any less secure than someone not locking the door of their house makes Yale locks insecure. bill -- Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves bill@cs.scranton.edu | and a sheep voting on what's for dinner. University of Scranton | Scranton, Pennsylvania | #include ------------------------------ Date: Thu, 28 Jun 2007 07:24:59 -0700 From: Cuyler Subject: Scripting question Message-ID: <1183040699.610954.291670@k79g2000hse.googlegroups.com> I have the following script that's not behaving very well. If I watch the script and hit enter after the break is done then the NFS mount get mounted. If I do nothing and just wait the mounts fail. the print statement with the "Remounting shares" was added as the nfs_failover.com script runs fine now with that added - this one not so much. Any ideas --- Output --- VMSNODE::USERNAME_S $ @nfs_failback.com %TCPIP$DNFSDISMOUNT-S-DISMOUNTED, DNFS1:[000000] dismounted %TCPIP$DNFSDISMOUNT-S-DISMOUNTED, DNFS10:[000000] dismounted Authentication successful. The resync base snapshot will be: netapp02(0099907364)_vol1_mirror.1 These newer snapshots will be deleted from the destination: hourly.0 Volume vol1 will be briefly unavailable before coming back online. Revert to resync base snapshot was successful. Transfer started. Monitor progress with 'snapmirror status' or the snapmirror log. Transfer successful. Authentication successful. Transfer started. Monitor progress with 'snapmirror status' or the snapmirror log. Transfer successful. Authentication successful. snapmirror break: Destination vol1 is now writable. Volume size is being retained for potential snapmirror resync. If you would like to grow the volume and do not expect to resync, set vol option fs_size_fixed to off. Authentication successful. The resync base snapshot will be: netapp01(0099907364)_vol1.3 Volume vol1_mirror will be briefly unavailable before coming back online. Revert to resync base snapshot was successful. Transfer started. Monitor progress with 'snapmirror status' or the snapmirror log. Remounting shares %TCPIP$DNFSMOUNT-E-MOUNTFAIL, error mounting _DNFS10:[000000] -SYSTEM-W-NOSUCHFILE, no such file %TCPIP$DNFSMOUNT-E-MOUNTFAIL, error mounting _DNFS1:[000000] -SYSTEM-W-NOSUCHFILE, no such file VMSNODE::USERNAME_S $ type nfs_failback.com $ tcpip dismount dnfs1:[000000] $ tcpip dismount dnfs10:[000000] $ ssh -o "batchmode yes" root@netapp01 "snapmirror resync -f -S netapp02:vol1_mirror -w netapp01:vol1" $ ssh -o "batchmode yes" root@netapp01 "snapmirror update -S netapp02:vol1_mirror -w netapp01:vol1" $ ssh -o "batchmode yes" root@netapp01 "snapmirror break vol1" $ ssh -o "batchmode yes" root@netapp02 "snapmirror resync -f vol1_mirror" $ write sys$output "Remounting shares" $ tcpip mount dnfs10:[000000] /host="NETAPP02"/path="/vol/vol1"/system $ tcpip mount dnfs1:[000000] /host="NETAPP01"/path="/vol/vol1"/system VMSNODE::USERNAME_S $ type mountnfs.com $ tcpip mount dnfs10:[000000] /host="NETAPP02"/path="/vol/vol1"/system $ tcpip mount dnfs1:[000000] /host="NETAPP01"/path="/vol/vol1"/system VMSNODE::USERNAME_S $ @mountnfs.com %TCPIP$DNFSMOUNT-S-MOUNTED, /vol/vol1 mounted on _DNFS10:[000000] %TCPIP$DNFSMOUNT-S-MOUNTED, /vol/vol1 mounted on _DNFS1:[000000] ------------------------------ Date: Thu, 28 Jun 2007 05:36:48 -0700 From: Neil Rieck Subject: Re: Supercomputer rankings Message-ID: <1183034208.118052.38130@k29g2000hsd.googlegroups.com> On Jun 27, 4:17 am, JF Mezei wrote: [...snip...] > > The 28 out of 500 systems based on that IA64 thing represent 0.056% of > the total. Not quite "maintream" , "commodity" or "industry standard" > that HP would like us to believe. Check this out: IBM creates world's most powerful computer http://www.newscientisttech.com/article/dn12145 When I read stuff like this I'm reminded that technology companies (like IBM and SUN) which were actually run by technology people "kept their eyes on the prize" and didn't kill off their flag ship products. Neil Rieck Kitchener/Waterloo/Cambridge, Ontario, Canada. http://www3.sympatico.ca/n.rieck/ ------------------------------ Date: Thu, 28 Jun 2007 13:06:36 +0000 From: "Paul Raulerson" Subject: Re: Supercomputer rankings Message-ID: ----=_vm_0011_W3580230671_8788_1183035996 Content-Type: multipart/alternative; boundary="--=_vm_0016_W3580230671_8788_1183035996" ----=_vm_0016_W3580230671_8788_1183035996 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit SNORT! IBM not try to kill off flagship products? Oh my... let me tell you a story about the little OS that would not die... (google z/VM) Or more recently, IBM starting to shut out smaller developers from the mainframe platform... (google Flex-ES) Or... oh lordy. TRUST ME - HP is GREAT in the way they are STILL SUPPORTING VMS and other "legacy" systems. -Paul ----=_vm_0016_W3580230671_8788_1183035996 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

SNORT!

IBM not try to kill off flagship products? Oh my... let me tell you a = story about the little OS that would not die... (google z/VM)

Or = more recently, IBM starting to shut out smaller developers from the mainf= rame platform... (google Flex-ES)

Or... oh lordy.

TRUST ME - HP is GREAT in the way they are STILL SUPPORTING VMS and ot= her "legacy" systems.

-Paul

 

----=_vm_0016_W3580230671_8788_1183035996-- ----=_vm_0011_W3580230671_8788_1183035996 Content-Type: message/rfc822 Content-Transfer-Encoding: 8bit Content-Disposition: attachment From: "Neil Rieck" To: Info-VAX@Mvb.Saic.Com Message-ID: <1183034208.118052.38130@k29g2000hsd.googlegroups.com> Date: Thu, 28 Jun 2007 12:36:00 +0000 Received: (qmail 27808 invoked by uid 78); 28 Jun 2007 12:41:06 -0000 Received: from unknown (HELO ns-mr34.netsolmail.com) (10.49.16.29) by 0 with SMTP; 28 Jun 2007 12:41:06 -0000 Received: from MVB.SAIC.COM (mvb.saic.com [198.151.12.104]) by ns-mr34.netsolmail.com (8.13.6/8.13.6) with SMTP id l5SCf4U8016429 for ; Thu, 28 Jun 2007 08:41:05 -0400 X-Newsgroups: comp.os.vms Organization: http://groups.google.com Lines: 23 X-Trace: posting.google.com 1183034208 17064 127.0.0.1 (28 Jun 2007 12:36:48 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Thu, 28 Jun 2007 12:36:48 +0000 (UTC) In-Reply-To: User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 1.0.3705; .NET CLR 2.0.50727),gzip(gfe),gzip(gfe) Complaints-To: groups-abuse@google.com Injection-Info: k29g2000hsd.googlegroups.com; posting-host=67.70.206.37; posting-account=gqH8sgwAAADaD4iV8RaKl0E_zzbUK6eZ X-Gateway-Source-Info: USENET Subject: Re: Supercomputer rankings MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Jun 27, 4:17 am, JF Mezei wrote: [...snip...] > > The 28 out of 500 systems based on that IA64 thing represent 0.056% of > the total. Not quite "maintream" , "commodity" or "industry standard" > that HP would like us to believe. Check this out: IBM creates world's most powerful computer http://www.newscientisttech.com/article/dn12145 When I read stuff like this I'm reminded that technology companies (like IBM and SUN) which were actually run by technology people "kept their eyes on the prize" and didn't kill off their flag ship products. Neil Rieck Kitchener/Waterloo/Cambridge, Ontario, Canada. http://www3.sympatico.ca/n.rieck/ ----=_vm_0011_W3580230671_8788_1183035996-- ------------------------------ Date: Thu, 28 Jun 2007 08:30:53 +0200 From: "Gorazd Kikelj" Subject: Re: Tech support Message-ID: > "William Webb" wrote: > >> I have suggested to several senior people at HP that they need to add >> a field to >> whatever screen it is that comes up when they locate an individual in >> connection >> with a support contract that indicates something like "This customer >> knows what the heck he's talking about." >> >> That way it would bypass the almost-obligatory ten or fifteen minutes >> spent in attempts to explain the reason for your call to a Level 1 >> support technician who >> may or may not understand what you're talking about. In fact this is implemented in some way. For Mission Critical Customers we very well know to whom we talking to. And have a Red Flag raised when he call. Best, Gorazd ------------------------------ Date: Thu, 28 Jun 2007 03:16:14 -0700 From: IanMiller Subject: Re: Tech support Message-ID: <1183025774.218052.132250@c77g2000hse.googlegroups.com> Golden Eggs are available (including the latest servers) at http://www.openvms.org/pages.php?page=GoldenEggs and Matti will do custom diagrams for mere money, DSNlink went as there was noone left who knew how it worked. It was well over due for a update anyway. ISEE is the replacement http://h20219.www2.hp.com/services/cache/10709-0-0-225-121.html ------------------------------ Date: Thu, 28 Jun 2007 08:53:27 -0700 From: IanMiller Subject: VTJ V10 Message-ID: <1183046007.445480.6640@w5g2000hsg.googlegroups.com> If you want to read something positive for a change why not have a look at the latest VMS Technical Journal. http://www.openvms.org/stories.php?story=07/06/28/1382563 ------------------------------ Date: Thu, 28 Jun 2007 16:13:52 GMT From: =?ISO-8859-1?Q?Jan-Erik_S=F6derholm?= Subject: Re: VTJ V10 Message-ID: <47Rgi.3082$ZA.1240@newsb.telia.net> IanMiller wrote: > If you want to read something positive for a change why not have a > look at the latest VMS Technical Journal. > > http://www.openvms.org/stories.php?story=07/06/28/1382563 > And, as an related note... In the last Customer Times VMS was mentioned quite a lot, I think. 7 notes under the "OpenVMS" heading. Same number as for NonStop, just one less then for "Open Source/Linux". HPUX has 4 articles and T64 one, b.t.w... There are also VMS links in the "Blade" and "Integrity" sections. http://www.hp.com/products1/evolution/customertimes/pdfs/200706_Customer_Times.pdf ------------------------------ End of INFO-VAX 2007.350 ************************