INFO-VAX Wed, 06 Aug 2008 Volume 2008 : Issue 426 Contents: Re: CD written on Alpha won't mount on Integrity DVD ROM Re: CD written on Alpha won't mount on Integrity DVD ROM Re: HP buys EDS Re: HP buys EDS Re: Monitor Utility Re: Monitor Utility Re: OT: Marketing OpenVMS Re: OT: Marketing OpenVMS Re: PDF docs ---------------------------------------------------------------------- Date: Tue, 05 Aug 2008 21:26:43 +0100 From: baldrick <nospam@[127.0.0.1]> Subject: Re: CD written on Alpha won't mount on Integrity DVD ROM Message-ID: <AtCdnS7IeLcZKgXVRVnyjAA@posted.plusnet> R.A.Omond wrote: > baldrick wrote: >> [...snip...] >> My INIT command for the container file is: >> >> init lda1:/index=end/nohigh/system/cluster=4/erase/max='maxfil' 'label' > ^^^^^^^^^^ > > Nic, I'm always suspicious of "stuff" at the end of a CD, given > that some (all?) drives work with 2,048-byte blocks, and you're > never quite sure *exactly* how much you can really get on the CD. > > Just a hunch: try sticking the index file at the beginning, > and since you're such a newbie I'll give you the command: > > $ init lda1:/index=beginning ... > > ;-) Roy, thank you ! However, there is a cunning reason why the index is positioned at the rear end, which is that sometimes I wish to use MKISOFS for a dual standard windows/VMS cd, as per Brian's page http://www.tmesis.com/CDrom/ I don't have immediate access to another VMS integrity Box to try another (SCSI) DVD drive, but my puzzle remains as I wish to be able to create a CD that can be universally mounted on all platforms, but this is the first time I tried one of my home cooked CDs on an Itanium. Anyone done this and it works ? I am going to try using SIM and connect the image through virtual connect and see what happens... That should eliminate the physical drive as a cause. Nic -- nclews at csc dot com aka Mr. CP Charges "The idea that Bill Gates has appeared like a knight in shining armour to lead all customers out of a mire of technological chaos neatly ignores the fact that it was he who, by peddling second-rate technology, led them into it in the first place."- DNA ------------------------------ Date: Tue, 05 Aug 2008 16:31:37 -0400 From: "Richard B. Gilbert" <rgilbert88@comcast.net> Subject: Re: CD written on Alpha won't mount on Integrity DVD ROM Message-ID: <UZKdnakz_bviJAXVnZ2dnUVZ_o_inZ2d@comcast.com> baldrick wrote: > R.A.Omond wrote: >> baldrick wrote: >>> [...snip...] >>> My INIT command for the container file is: >>> >>> init lda1:/index=end/nohigh/system/cluster=4/erase/max='maxfil' 'label' >> ^^^^^^^^^^ >> >> Nic, I'm always suspicious of "stuff" at the end of a CD, given >> that some (all?) drives work with 2,048-byte blocks, and you're >> never quite sure *exactly* how much you can really get on the CD. >> >> Just a hunch: try sticking the index file at the beginning, >> and since you're such a newbie I'll give you the command: >> >> $ init lda1:/index=beginning ... >> >> ;-) > > Roy, thank you ! However, there is a cunning reason why the index is > positioned at the rear end, which is that sometimes I wish to use > MKISOFS for a dual standard windows/VMS cd, as per Brian's page > http://www.tmesis.com/CDrom/ > > I don't have immediate access to another VMS integrity Box to try > another (SCSI) DVD drive, but my puzzle remains as I wish to be able to > create a CD that can be universally mounted on all platforms, but this > is the first time I tried one of my home cooked CDs on an Itanium. > Anyone done this and it works ? > > I am going to try using SIM and connect the image through virtual > connect and see what happens... That should eliminate the physical drive > as a cause. > > Nic There are many people in the Unix world who seem to be having similar problems, they can read factory made CDs without problems but the home brew CDs just will not work! Some drives seem to work better than others. The conventional wisdom on the Unix side is, to burn using the slowest possible speed. ------------------------------ Date: 5 Aug 2008 13:06:58 -0500 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: HP buys EDS Message-ID: <B1aKKQpx2eOU@eisner.encompasserve.org> In article <126ff51f-253c-4c14-8767-bf203175dece@r66g2000hsg.googlegroups.com>, AEF <spamsink2001@yahoo.com> writes: > > "To make as much money as we can without going to jail." That's to much morality for some CEOs. ------------------------------ Date: Tue, 05 Aug 2008 22:52:54 -0400 From: =?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk> Subject: Re: HP buys EDS Message-ID: <489911ff$0$90274$14726298@news.sunsite.dk> Bob Koehler wrote: > In article <126ff51f-253c-4c14-8767-bf203175dece@r66g2000hsg.googlegroups.com>, AEF <spamsink2001@yahoo.com> writes: >> "To make as much money as we can without going to jail." > > That's to much morality for some CEOs. That has been the case for some of them. But I believe that most of them are smart enough not to cross that border. Arne ------------------------------ Date: 5 Aug 2008 13:10:07 -0500 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: Monitor Utility Message-ID: <Ur2koNgXSAxv@eisner.encompasserve.org> In article <525817.47530.qm@web83908.mail.sp1.yahoo.com>, "James J. O'Shea" <seamas_ose@ameritech.net> writes: > I have an ES45 running VMS 8.3. > > When I type $MONITOR SYSTEM/ALL one of the rows is > "Idle Time". And one of it's colum's is "MIN". But > the value of that column never changes from "0.00" > Can anyone tell me why? Please see the comic strips for "Mr. Obviousman". He can tell you. 8-( ------------------------------ Date: Tue, 05 Aug 2008 11:53:14 -0700 From: Joe Bloggs <JBloggs@acme.com> Subject: Re: Monitor Utility Message-ID: <2b8h94pb4d3lmo69t97qn6891kt3drm3dt@4ax.com> On Mon, 4 Aug 2008 20:12:02 -0700 (PDT), "James J. O'Shea" <seamas_ose@ameritech.net> wrote: >I have an ES45 running VMS 8.3. > >When I type $MONITOR SYSTEM/ALL one of the rows is >"Idle Time". And one of it's colum's is "MIN". But >the value of that column never changes from "0.00" >Can anyone tell me why? > > >Thanks, >Jim O'Shea >Chicago We collect monitor data on a daily basis, (mostly on ES45's coincidentally enough), replaying the data later, emailing summaries. The recent monitor eco, VMS83A_MONTOR-V0100 (included in VMS83A_UPDATE-V0600) ,seemed to introduce a problem with the MON MODES summary. On systems with the ECO, the min idle-time is always reported as 0.00, in the summary report, no matter what interval is chosen. Systems without the ECO (same compute load) report what look like reasonable non-zero min idle times. As I collect enough round tuits, I was going to query the CSC on this. For now, we've worked around it, using T4 instead. (iirc, T4 uses its own 'no-drift' MONITOR image) The release notes for that ECO suggest some amount of work was directed at addressing average values displayed as zero. among other things. http://www12.itrc.hp.com/service/patch/patchDetail.do?patchid=VMS83A_MONTOR-V0100 $ monitor DECNET - ,DISK - ,DLOCK - ,FCP - ,FILE_SYSTEM_CACHE - ,IO - ,LOCK - ,MODES - ,PAGE - ,PROCESSES - ,STATES - ,SYSTEM - /all - /nodisplay - /record='out_file' - /flush=30 - /beg="06:29:55.00" - /end="07:30:00.00" $ monitor MODES - /input='out_file' - /nodisplay - /summ = 'summ_file' ------------------------------ Date: Tue, 05 Aug 2008 14:20:14 -0400 From: JF Mezei <jfmezei.spamnot@vaxination.ca> Subject: Re: OT: Marketing OpenVMS Message-ID: <48989a7f$0$1806$c3e8da3@news.astraweb.com> Richard B. Gilbert wrote: > The "VMS is dead" chorus has been going on for years. Does anyone > remember "Monty Python and the Holy Grail" and "Bring out your dead"? In the past, it was "Digital is killing VMS". Then, it was "Compaq is killing VMS". Now, it is "HP is letting VMS die". The problem is that initially, VMS still had a lot of installed base power. Now, after all the engineering cutbacks, and move into smaller offices, and with the installed based having shrunk, HP might still be able to legally say that VMS is still being developped, but I think VMS is now more on "maintenance" mode than anything else. They will assign resources to suport new HP hardware, but not much more. HP hasn't yet announced VMS was dead. So VMS is still dying. It isn't dead yet. But it is so deep into a coma that, from a marketplace point of view, it has been dead for a long while. ------------------------------ Date: 5 Aug 2008 15:40:21 -0500 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: OT: Marketing OpenVMS Message-ID: <vFTy+$emSFW9@eisner.encompasserve.org> In article <48989a7f$0$1806$c3e8da3@news.astraweb.com>, JF Mezei <jfmezei.spamnot@vaxination.ca> writes: > Now, after all the engineering cutbacks, and move into smaller offices, > and with the installed based having shrunk, HP might still be able to > legally say that VMS is still being developped, but I think VMS is now > more on "maintenance" mode than anything else. They will assign > resources to suport new HP hardware, but not much more. So is the plan to add clusters over IP "maintenance" or new HW support? ------------------------------ Date: Tue, 5 Aug 2008 22:44:49 -0400 From: "John Reagan" <johnrreagan@earthlink.net> Subject: Re: PDF docs Message-ID: <atidndQfaeiVjQTVnZ2dnUVZ_sWdnZ2d@earthlink.com> <VAXman- @SendSpamHere.ORG> wrote in message news:4884c295$0$20907$607ed4bc@cv.net... > > Save that Jack asked for *VAX* calling standard. The VAX calling standard > has been elided from the V8 docs. > Uh, chapter 2 is "VAX conventions"! The single Calling Standard covers all three platforms. John (the current owner of the Calling Standard) ------------------------------ End of INFO-VAX 2008.426 ************************