1 INFO-VAX	Tue, 19 Oct 2004	Volume 2004 : Issue 580       Contents:+ Re: ANN: PWAIT$SDA freeware from Ian Miller 1 Re: CC /MMS_DEPENDENCIES and related difficulties 1 Re: CC /MMS_DEPENDENCIES and related difficulties & Cluster Ethernet Interconnect question Re: DECStation OS  ECU disk Re: ECU disk Re: File counts 2 Ghostscript v811 (from Freeware V6.0)and PS to PDF% Re: Humor   was Re: VMS for the blind  Re: J F on why USA is a regime# Re: Latest on Windoze Navy software # Re: Latest on Windoze Navy software # Re: Latest on Windoze Navy software # Re: Latest on Windoze Navy software & Re: Need Itanium2 (EPIC) Clarification& Re: Need Itanium2 (EPIC) ClarificationP Re: Obsucure Inquier article about Intel mentions VMS (and not anyother OS') OS' Question about Descriptors Re: Question about Descriptors Re: Question about Descriptors Re: Question about Descriptors Re: Question about Descriptors Re: Question about Descriptors Re: Question about Descriptors Re: Question about Descriptors Re: Question about Descriptors> Re: Routine to Resubmit print/batch entries from queue listing Re: RZ28B-VA drives wanted Re: RZ28B-VA drives wanted Re: RZ28B-VA drives wanted Re: RZ28B-VA drives wanted Re: RZ28B-VA drives wanted Re: RZ28B-VA drives wanted0 Re: Simulating monochrome to test Xwindows app ?0 Re: Simulating monochrome to test Xwindows app ? Re: VMS for the blind 3 RE: VMS related water bound powerful mammal artwork ; Re: VTfm - OpenVMS file manager for VT-compatible terminals   F ----------------------------------------------------------------------  % Date: Mon, 18 Oct 2004 19:46:43 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net>4 Subject: Re: ANN: PWAIT$SDA freeware from Ian Miller+ Message-ID: <417463F3.74D7A631@comcast.net>    Fabio Cardoso wrote: > g > David J Dachtera <djesys.nospam@comcast.net> wrote in message news:<4172ABF9.F4DBFEEA@comcast.net>...  > > Hunter Goatley wrote:  > > > I > > > Thanks to Ian Miller, PWAIT$SDA V0.8 for OpenVMS Alpha is available 6 > > > from my VMS freeware archives.  From the README: > > > F > > > PWAIT$SDA is a SDA extension (using the API first documented forF > > > VMS V7.2) which displays information about a process waiting andE > > > what it is waiting for.  It is intended to help investigate why  > > > a process appears hung.  > > L > > Gee - the folks at WEBES engineering could have used something like thatL > > earlier this year when we were trying to discover why DESTA Director - a6 > > JAVA program - was exhausting (leaking) its BIOLM. > > H > > As it was, I wrote PRCQUOTA.COM to try to examine process quotas andI > > detect an imminent exhaustion. It's derived from an hourly monitoring G > > proc. I run on the production cluster at work which watches process - > > quotas and sends e-mail when any get low.  > >  > > See:8 > > http://www.djesys.com/freeware/vms/4038_freeware.zip > > H > > ...for PRCQUOTA.COM and other goodies. (This is the freeware archiveK > > associated with the presentation I gave at this year's DECUS symposium, L > > HPworld-2004. I'm considering repackaging it adding some newer stuff and+ > > submitting it to the next freeware CD.)  > > 5 > Is there a way (tool) to DEBUG Java applications ??    Sure!     $ DELETE ddcu:[000000...]*.JAR;*   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------    Date: 18 Oct 2004 11:54:03 -07007 From: jones.computer.srv@worldnet.att.net (Daryl Jones) : Subject: Re: CC /MMS_DEPENDENCIES and related difficulties= Message-ID: <8a646952.0410181054.67477d72@posting.google.com>    Dear Steven M. Schweda:   H The way I would use MMS to build an single Image would be the following.J Lets say I create a MMS file called FREDA.MMS that contains the following:  J !=========================================================================   .FIRST    @WRITE SYS$OUTPUT " "5    @WRITE SYS$OUTPUT " FREDA IMAGE build has started"     @WRITE SYS$OUTPUT " "   .LAST     @WRITE SYS$OUTPUT " "7    @WRITE SYS$OUTPUT " FREDA IMAGE build has completed"     @WRITE SYS$OUTPUT " "    PURGE XXX_EXE:*.*    PURGE XXX_OBJ:*.*     .DEFAULT    @WRITE SYS$OUTPUT " "0    @WRITE SYS$OUTPUT " $(MMS$TARGET) is Missing"    @WRITE SYS$OUTPUT " "  # DEBUG = /WARN=NOINFO/NOLIST/OPTIMZE  CFLAG=$(DEBUG) LINKFLAGS=/BRIEF/MAP=XXX_OBJ:    .SUFFIXES :; .SUFFIXES ;     .EXE .OBJ .C .H   @ .C.OBJ    :;   - $(CC) $(CFLAGS) $(MMS$SOURCE)/OBJ=$(MMS$TARGET)O .EXE.OBJ  :;   - $(LINK) $(LINKFLAGS)$(LKDBG) /EXE=$(MMS$TARGET) $(MMS$SOURCE)    0 XXX_EXE:FREDA.EXE   DEPENDS_ON XXX_OBJ:FREDA.OBJ  > XXX_OBJ:FREDA.OBJ   DEPENDS_ON XXX_SRC:FREDA.C,XXX_SRC:FREDA.H  O !==============================================================================   1 Where XXX_EXE, XXX_OBJ, and XXX_SRC are logicals.   5 To create the Image you would execute the following:    "            $ MMS/DECRIPT=FREDA.MMS   I hope this helps    Daryl Jones     G sms@antinode.org wrote in message news:<04101620164825@antinode.org>... > > Complaint/Question 3.  How to make a useful dependency file.D >       ------------------------------------------------------------ > H >    I've found one more reason to complain about CC /MMS_DEPENDENCIES. I > Not only does the generated dependency file not include the destination H > directory for the object file, it does not even use the actual name of1 > the object file as the name of the object file.  > 0 >    In the following, FREDA.C includes FREDA.H. >  >    Part 1, Simple: > 7 > alp $ cc freda /MMS_DEP = (file = freda1.mmsd, nosys)  > alp $ type freda1.mmsd' > FREDA.OBJ :     ALP$DKA0:[SMS]FREDA.C ' > FREDA.OBJ :     ALP$DKA0:[SMS]FREDA.H  >  > What could go wrong? >  > + >    Part 2, Loss of destination directory:  > F > alp $ cc freda /MMS_DEP = (file = freda2.mmsd, nosys) /obj = [.test] > alp $ type freda2.mmsd' > FREDA.OBJ :     ALP$DKA0:[SMS]FREDA.C ' > FREDA.OBJ :     ALP$DKA0:[SMS]FREDA.H  > B > Object file goes where it's told.  Dependency file ignores this. >  > 2 >    Part 3, Wrong object name in dependency file: > N > alp $ cc freda /MMS_DEP = (file = fredX.mmsd, nosys) /obj = [.test]fredX.obj > alp $ type fredX.mmsd ' > FREDA.OBJ :     ALP$DKA0:[SMS]FREDA.C ' > FREDA.OBJ :     ALP$DKA0:[SMS]FREDA.H  > G > Object file goes where it's told.  Dependency file ignores everything ' > except the name of the _source_ file.  >  >    Is this a bug or not? > J >    Is anyone using this feature in any but the most trivial situations?  > (Is anyone using it at all?) > H >    Is there some easy way I'm not seeing to get it to do what I'd like > (that is, something useful)? > J > ------------------------------------------------------------------------ > 6 >    Steven M. Schweda               (+1) 651-699-98185 >    382 South Warwick Street        sms@antinode-org  >    Saint Paul  MN  55105-2547    ------------------------------  + Date: Mon, 18 Oct 2004 16:15:51 -0500 (CDT)  From: sms@antinode.org: Subject: Re: CC /MMS_DEPENDENCIES and related difficulties) Message-ID: <04101816155107@antinode.org>   ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)   E >    Ah, OK, I have separate directories for executeables for VAX and F >    Alpha, but I never bothered with objects that way because I don't: >    bother building on VAX until Alpha is fully debugged. > 9 >    A simple .LAST with a RENAME may solve your problem.   E    I don't think so.  I want to generate the .OBJ (and .OLB and .EXE) D files where they will be used, and leave them there, so that after IG make a change to some source file, I can get a reasonably minimal build H with reasonable ease.  If I start renaming files, the next MMS run won't see them where they need to be.   @    If I wanted only a one-time build procedure, I'd just use theG BUILD_[UN]ZIP.COM comand procedures I've already written.  I was hoping H also to come up with a more up-to-date DESCRIP.MMS which included a moreC realistic set of dependencies than the existing one, and do it in a E fairly automated way, to reduce the manual error introduction rate as A the source code changes.  So far, it's been more frustrating than 
 rewarding.    7 From: jones.computer.srv@worldnet.att.net (Daryl Jones)   J > The way I would use MMS to build an single Image would be the following.A > Lets say I create a MMS file called FREDA.MMS that contains the  > following: > [...]   C    None of this helps me automatically generate useful dependencies  using CC /MMS, does it?   H ------------------------------------------------------------------------  4    Steven M. Schweda               (+1) 651-699-98183    382 South Warwick Street        sms@antinode-org     Saint Paul  MN  55105-2547    ------------------------------  % Date: Mon, 18 Oct 2004 22:13:32 -0700 , From: James Nykiel <jnykiel@access4less.net>/ Subject: Cluster Ethernet Interconnect question < Message-ID: <pan.2004.10.19.05.13.31.544140@access4less.net>  
 Greetings:    F If I want to create a cluster with two AlphaStations using an Ethernet= Interconnect do I need to have two Ethernet adapters in each?   H I have been looking through the documents ovms_73_cluster_config.pdf andJ ovms_731_cluster_systems.pdf but still do not understand alot of what I amD reading so please excuse me if I have looked over something obvious.   Thanks - Jim   ------------------------------  % Date: Mon, 18 Oct 2004 20:00:25 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net> Subject: Re: DECStation OS+ Message-ID: <41746729.4691C3BD@comcast.net>   ( huw.davies@kerberos.davies.net.au wrote: > % > David Wade <g8mqw@yahoo.com> wrote:  > O > > I doubt they want you to buy VMS these days. They want VMS users to spend a  > > fortune on# > > services migrating elsewhere...  > H > Given that HP have spent a lot of time (and money) porting VMS to IA642 > I doubt that they'd push VMS users elsewhere....  ! "Push" is perhaps the wrong word.   H A mentor of mine once said, "Herding buffalo is easy - so long you heard them where they want to go."  D Make them want to move away from VMS, and ... (finish the sentence).  F As foolish a strategy as it is, you gotta give 'em credit - the purity+ of its beauty lies in its utter simplicity!    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  + Date: Mon, 18 Oct 2004 23:01:39 +0000 (UTC) + From: "Rob H" <robert.heyes@btinternet.com>  Subject: ECU disk 2 Message-ID: <cl1i0j$n74$2@hercules.btinternet.com>  K Where can I obtain an EISA (ECU) disk for an Alpha Server 1000? Can anyone   send me a link or the files?   Ta V much.     ------------------------------    Date: 18 Oct 2004 20:49:45 -0700# From: dooleys@snowy.net.au (dooley)  Subject: Re: ECU disk = Message-ID: <1ca82fc6.0410181949.3e402e4a@posting.google.com>   e "Rob H" <robert.heyes@btinternet.com> wrote in message news:<cl1i0j$n74$2@hercules.btinternet.com>... M > Where can I obtain an EISA (ECU) disk for an Alpha Server 1000? Can anyone   > send me a link or the files?1 There was one on www.driverguide.com a while ago,   but I don't have the exact link. Phil   ------------------------------  % Date: Mon, 18 Oct 2004 19:34:07 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net> Subject: Re: File counts+ Message-ID: <417460FF.B2736393@comcast.net>    Fred Hoenisch wrote: > J > You can use DFU (Disk and File Utility).  I think the current version is > 2.7a >  > The command would be: 0 > $ dfu report /nobitmap/novolume disk4 /out=a.a   This should work, too:  D $ pipe dfu report /nobitmap/novolume disk4 | search sys$pipe: "Total files"   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  # Date: Mon, 18 Oct 2004 19:58:18 GMT " From:   VAXman-  @SendSpamHere.ORG; Subject: Ghostscript v811 (from Freeware V6.0)and PS to PDF 0 Message-ID: <00A398B3.CAAA2073@SendSpamHere.ORG>   $ gs -? " AFPL Ghostscript 8.11 (2003-08-16)D Copyright (C) 2003 artofcode LLC, Benicia, CA.  All rights reserved., Usage: gs [switches] [file1.ps file2.ps ...]< Most frequently used switches: (you can use # in place of =)M  -dNOPAUSE           no pause after page   | -q       `quiet', fewer messages L  -g<width>x<height>  page size in pixels   | -r<res>  pixels/inch resolutionJ  -sDEVICE=<devname>  select device         | -dBATCH  exit after last fileI  -sOutputFile=<file> select output file: - for stdout, |command for pipe, C                                          embed %d or %ld for page # P Input formats: PostScript PostScriptLevel1 PostScriptLevel2 PostScriptLevel3 PDF Default output device: x11 Available devices:D    bbox bit bitcmyk bitrgb bj10e bj200 bjc600 bjc800 cdeskjet cdj550E    cdjcolor cdjmono deskjet djet500 epswrite faxg3 faxg32d faxg4 jpeg K    jpeggray laserjet ljet2p ljet3 ljet3d ljet4 ljet4d ljetplus nullpage pbm I    pbmraw pcx16 pcx24b pcx256 pcxcmyk pcxgray pcxmono pdfwrite pgm pgmraw K    pgnm pgnmraw pj pjxl pjxl300 pkm pkmraw pksm pksmraw png16 png16m png256 E    pngalpha pnggray pngmono pnm pnmraw ppm ppmraw psgray psmono psrgb F    pswrite pxlcolor pxlmono tiff12nc tiff24nc tiffcrle tiffg3 tiffg32dJ    tiffg4 tifflzw tiffpack uniprint x11 x11alpha x11cmyk x11gray2 x11gray4J    tiffg4 tifflzw tiffpack uniprint x11 x11alpha x11cmyk x11gray2 x11gray4
    x11mono Search path:    [] , GS_LIB) For more information, see GS_DOC:Use.htm. F Report bugs to bug-gs@ghostscript.com, using the form in Bug-form.htm.   I used to use:  H $ GS "-sDEVICE=pdfwrite" to convert Postscript to PDF.  When I installedF this version, I can no longer do so.  I keep getting:  Unknown device:' %SYSTEM-E-BADPARAM, bad parameter value    --  < http://www.ProvN.com  for the *best* OpenVMS system security=                       solutions that others only claim to be.  --  , Cyber-Terrorism (si'-ber tayr'-or-iz-em) n.:M   The release of, the sale of, or the use of any Micro$oft software product!   --  K VAXman- A Bored Certified VMS Kernel Mode Hacker   VAXman(at)TMESIS(dot)COM    ------------------------------  % Date: Mon, 18 Oct 2004 19:44:52 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net>. Subject: Re: Humor   was Re: VMS for the blind+ Message-ID: <41746384.14900503@comcast.net>    John Smith wrote:  > J > When I saw the title of this thread "VMS for the blind", the first thing > that came to mind was: > E > Yes!!! Somebody has finally created a presentation for HP executive I > management about VMS at a simple enough level that even carly(tm) could A > understand - music, sing-along, follow the bouncing ball, .....   ( Purple dinosaur? ...or is that too much?  I > Imagine my chagrin when I discovered that while the thread was actually F > about a worthy and important use of VMS, it wasn't about changing HP > management perception of VMS.   H I'm certain it's a deeply engrained culture and will not die except with those who perpetuate it...  H ...which means our grand-children will know the OpenVMS success of which? such people robbed themselves - and us, HP's stockholders, etc.    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Mon, 18 Oct 2004 23:30:28 -0400 * From: "Bill Todd" <billtodd@metrocast.net>' Subject: Re: J F on why USA is a regime = Message-ID: <prGdnY0Gr4JrFOncRVn-iA@metrocastcablevision.com>   5 "David Froble" <davef@tsoft-inc.com> wrote in message " news:4172160D.503@tsoft-inc.com... > Bill Todd wrote: > / > It's always nice to hear fromt he far left...   K Not that one ever does around here.  I'm strictly a centrist, myself:  it's I just that a lot of people have been listening to rabid ideologues so long - that they have forgotten where the center is.    > 9 > > "David Froble" <davef@tsoft-inc.com> wrote in message * > > news:4170088A.6070901@tsoft-inc.com... > >  > > ...  > >  > > E > >>>>The day the USA began its illegal invasion of Iraq, it became a  > >>>>
 > > "regime".  > >  > >>J > >>It's even more illegal and a crime against humanity to allow something > >> > > like > > I > >>Saddam to remain in power and impose harm on those within and outside  > >>	 > > Iraq.  > > G > > Actually, the latter is not technically illegal at all, whereas the  invasion > > most assuredly was.  >  > K > I guess it depends who is defining 'illegal'.  In "Dave's World", someone  likeB > Saddam is definitely 'illegal'.  Possible not in "Bill's World".  J I hadn't realized that you had your own private fiefdom wherein you got toL define legality.  In the world that most of the rest of us inhabit, legalityK is defined by governmental entities, and that's the definition I was using.   L But in matters like this one you don't seem particularly concerned with muchI beyond your own prejudices, so I doubt that factual issues matter much to J you.  Which is why people like you should be prevented (by 'whatever means: necessary') from imposing their uninformed will on others.  H > > Perhaps you need to brush up on your international and United States law,G > > rather than speak from such abject ignorance while acting as if you  actuallyJ > > knew something about the subject.  Kofi Annan has (unfortunately, over 18L > > months too late) finally recently admitted the reality that the invasion was K > > indeed illegal:  not only was it a violation of the U.N. charter, which L > > restricts military action to self-defense unless authorized by the U.N., but D > > by extension it was also a violation of U.S. law, since the U.S. ratifiedH > > said charter as a treaty and the Constitution (Article VI, clause 2)F > > specifies that treaties are part of 'the supreme law of the land'.  L (I just thought that bore repeating, should you care to rejoin the civilized  world's definition of legality.)   ...   J > > Attitudes like yours are a significant part of the reason that a largeK > > portion of the world would stand up and cheer if Washington, D.C., were J > > wiped off the face of the earth - not as vengeance so much as to knock usG > > down enough pegs to make us cease being a threat to the rest of the  planet. H > > Until we change our attitude significantly, you can count me in that number.  > > 
 > > - bill >  > C > So you would actually cheer if hundreds of thousands of people in 
 Washington > D.C. were to die?   J Yes:  the currently-popular phrase for that is 'collateral damage', and ifL that's what it takes to stop our insanity (the condition I specified above),J so be it.  My guess is that it might well actually minimize the total loss: of life compared to the situation if we are *not* stopped.  6   I guess I just have to ask, did you cheer as the WTC > buildings fell?   K No:  it only became clear to me in retrospect just how justified the attack < had been, primarily due to the nature of our response to it.  >   They too were a symbol.  Be careful to avoid being on one of > dubya's lists.  L The only thing I'm at all careful about is running afoul of actual law (realI law, not "Dave's law"...).  Using protected free speech to give the thugs H running our country something to fume about is not only a pleasure but aK civic duty - and even the current reactionary Supreme Court is having a bit L of difficulty stomaching the idea that free speech is now something that can  only occur in specified 'zones'.   - bill   ------------------------------  % Date: Mon, 18 Oct 2004 15:39:25 -0400 ( From: David Froble <davef@tsoft-inc.com>, Subject: Re: Latest on Windoze Navy software, Message-ID: <41741BED.6020407@tsoft-inc.com>   Ed Vogel wrote:   7 > "Bill Gunshannon" <bill@cs.uofs.edu> wrote in message ' > news:2tdb8uF1v46k6U2@uni-berlin.de...  > F >>No, the question is quite clear.  "Does any language use descriptors
 >>natively ?"  >> > C >     I believe BASIC does.  BASIC strings are, by default, dynamic H >     strings.  When passing strings, BASIC will pass the descriptor (by >     reference).     Q Yep, for both dynamic and fixed length strings, when represented by descriptors.  Q   I believe the BASIC runtime image will use the descriptors appropriately, thus  O allowing dynamic and fixed length strings to be used.  The descriptor contains    information of types of strings.     >     Ed Vogel >     HP/Compaq C Engineering + >     (but worked on BASIC for many years).      Why the demotion?  :-)     Dave   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------  # Date: Mon, 18 Oct 2004 22:32:02 GMT  From: reb <natron@ntlworld.com> , Subject: Re: Latest on Windoze Navy software0 Message-ID: <opsf27hwxeaqvj2s@news.ntlworld.com>  . On Thu, 14 Oct 2004 17:35:02 -0400, JF Mezei  % <jfmezei.spamnot@teksavvy.com> wrote:    > Tom Wade wrote: G >> Yes, you can compensate for this with good programming practice, but K >> interfaces using string descriptors were always a much safer way to do    >> it. > . > Does any language use descriptors natively ?    0 As has been said, thats an implementation issue.  8 In RTL/2, for example (which is a language of around the7 same age as C), arrays of characters are implemented on 9 VMS using descriptors, but other types of arrays are not.   8 Unlike C, RTL/2 provides runtime array bound checking as7 a basic feature, so at various points in their code the  programmer can select to:  - check all array accesses9 - check "unsafe" array accesses (i.e. writes & reads from 2    arrays of REFs [typed pointers])  {the default} - suppress all checks   8 The inclusion of this kind of feature is probably mostly8 down to the target application/user of the language when5 it was developed; for RTL/2 this was safety sensitive = real-time software developed by application (not programming) 9 specialists to run on the early PDP-11s & similar beasts.      reb    ------------------------------  % Date: Mon, 18 Oct 2004 15:53:26 -0700 # From: "Tom Linden" <tom@kednos.com> , Subject: Re: Latest on Windoze Navy software( Message-ID: <opsf28jcg8zgicya@hyrrokkin>  B On Mon, 18 Oct 2004 22:32:02 GMT, reb <natron@ntlworld.com> wrote:  0 > On Thu, 14 Oct 2004 17:35:02 -0400, JF Mezei  ' > <jfmezei.spamnot@teksavvy.com> wrote:  >  >> Tom Wade wrote:H >>> Yes, you can compensate for this with good programming practice, butL >>> interfaces using string descriptors were always a much safer way to do   >>> it.  >>/ >> Does any language use descriptors natively ?  >  > 2 > As has been said, thats an implementation issue.= PL/I has always used them internally, although we have always ; called them Dope Vectors, but they are essentially the same  thing  > : > In RTL/2, for example (which is a language of around the9 > same age as C), arrays of characters are implemented on ; > VMS using descriptors, but other types of arrays are not.  > : > Unlike C, RTL/2 provides runtime array bound checking as9 > a basic feature, so at various points in their code the  > programmer can select to:  > - check all array accesses; > - check "unsafe" array accesses (i.e. writes & reads from 4 >    arrays of REFs [typed pointers])  {the default} > - suppress all checks  > : > The inclusion of this kind of feature is probably mostly: > down to the target application/user of the language when7 > it was developed; for RTL/2 this was safety sensitive ? > real-time software developed by application (not programming) ; > specialists to run on the early PDP-11s & similar beasts.  >  >  > reb        --  C Using Opera's revolutionary e-mail client: http://www.opera.com/m2/    ------------------------------   Date: 19 Oct 2004 00:19:04 GMT( From: bill@cs.uofs.edu (Bill Gunshannon), Subject: Re: Latest on Windoze Navy software+ Message-ID: <2tj4roF1vr800U1@uni-berlin.de>   1 In article <L8Tcd.1055$DV4.151@news.cpqcorp.net>, ) 	John Reagan <john.reagan@hp.com> writes:  > Bill Gunshannon wrote: >  >>  F >> Hmmmm....  I remember "pass-by-value" and "pass-by-reference" but IE >> sure don't remember "pass-by-descriptor" in any Pascal text I ever  >> read. >>   > = > Compaq Pascal User Manual for OpenVMS Systems, section 5.3   > Parameter-Passing Mechanisms > I > "By default, Compaq Pascal uses the by reference mechanism to pass all  J > actual parameters except those that correspond to conformant parameters I > and undiscriminated schema parameters, in which case the by descriptor   > mechanism is used."  > H > Then in section 5.3.3, By Descriptor, table 5-3, lists the descriptor J > classes chosen for the various conformant array types (the compiler can ) > generate CLASS_A, _NCA, _VS, and _VSA).  >   @ That's not Pascal, that's Compaq Pascal.  An implementation, not? a language.  So, if I decide to write a modifed C Library that  B uses some format other than the dreaded "null terminated characterA array" and distribute it with a some compiler does that mean that ; the C language would be changed?  Or just my quirky system?    bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------  % Date: Mon, 18 Oct 2004 23:12:11 -0400 * From: "Bill Todd" <billtodd@metrocast.net>/ Subject: Re: Need Itanium2 (EPIC) Clarification = Message-ID: <bvqdnW1IUqszGOncRVn-jA@metrocastcablevision.com>   7 "Chuck Chopp" <ChuckChopp@rtfmcsi.com> wrote in message 6 news:igDcd.178114$as2.135993@bignews3.bellsouth.net... > Neil Rieck wrote:  > E > > In the past few weeks I've read several articles (including Terry 	 Shannon's I > > SKHPCV11N36) which mentioned the fact that "Itanium2 (Montecito) will L > > shortly introduce multithreading". Here is a quote from Terry's article: > > L > > "Other enhancements to Montecito include multithreading. Debuting in theI > > Xeon chip server line and already implemented in Pentium 4 processors D > > and IBM POWER5 CPUs, multithreading allows a CPU to run multipleF > > applications concurrently. This technology will be integrated into Itanium / > > for the first time when Montecito arrives."  > J > This sounds like the "Hyper-threading" term that was introduced with theK > dual-core P4 CPUs.  It is one CPU package with dual processor cores so it  isH > effectively a dual CPU system in an SMP configuration.  This gives youJ > multi-processor SMP capabilities on a mother board that isn't equiped to4 > support multiple separate processors on the board.  K Actually, no.  'Hyper-threading' is at least somewhat similar to EV8's SMT, G in that it uses the multiple resources of a *single* processor core (no H dual-core P4s exist, yet) - e.g., multiple integer or FP execution unitsK that in a single thread are dedicated to exploiting parallelism within that L single thread - to execute multiple threads concurrently (just 2 threads, inL the case of the P4).  And Montecito's SMT is also at least somewhat similar,G though more coarse-grained (similar to earlier POWER cores, though IIRC K POWER5's is fine-grained now) in that instead of interleaving the execution K of threads (again, I think just 2) on a single core as much as the presence L of multiple execution units allows, it switches execution only when a threadD stalls for a long-latency event (e.g., a main-memory access), and isJ therefore sometimes called 'switch-on-event multi-threading' (and tends onF average to offer less improvement to throughput than the finer-grained
 variants).  J Montecito, however, is also a dual-core chip (as POWER4 and its successors: have been since 2001) - each core can run two SMT threads.     I don't recall whetherI > or not the cache memory on the CPU was increased or if both cores share  the L > same cache memory that was previously dedicated to a single core, so thereK > may be some performance-related issues that result in a dual-core CPU not L > offering as large of a performance increase as what you'd get if you had a- > system with dual CPUs in separate packages.   B IIRC Montecito has private on-chip caches for each core (the POWERI architecture has been more flexible in this regard).  The main compromise L (aside from being by far the largest processor chip I've ever heard of - 580H mm^2, by some accounts) may be in the area of heat dissipation:  it willD likely not be possible to run both cores at the highest speed that a single-core variant could.   - bill   ------------------------------  % Date: Mon, 18 Oct 2004 23:56:40 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> / Subject: Re: Need Itanium2 (EPIC) Clarification , Message-ID: <41749053.7A0D6FBF@teksavvy.com>   Bill Todd wrote:D > IIRC Montecito has private on-chip caches for each core (the POWER7 > architecture has been more flexible in this regard).    M AMD and Intel (for both 8086 and IA64) will have duplicated caches. Power has K a single shared cache. Competition between AMD and Intel has forced them to J release their dual core ASAP, thus not giving them enough time to work the" single shared cache into the chip.  R The big difference is that with a single 2meg cache, you have 2 meg of data in it.M With 2 separate 1meg caches, much of the data in each cache will be the same, L and thus your effective cache is closer to 1 meg even though you phsysically have 2 meg on board.   ------------------------------  % Date: Mon, 18 Oct 2004 19:31:22 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net>Y Subject: Re: Obsucure Inquier article about Intel mentions VMS (and not anyother OS') OS' + Message-ID: <41746059.9FAE8AD8@comcast.net>    Andrew Harrison wrote: >  > Bob Koehler wrote:v > >  Andrew Harrison <andrew_remove__harrison@sun__.com> wrote in message news:<ck11gn$9vu$1@new-usenet.uk.sun.com>... > > I > >>Things have changed. SRSS 3.0 (SunRay Server Software) is now in Beta I > >>for Linux. I have it running on JDS (SUSE) and it also runs on RedHat G > >>so the backend hardware does not need to be a Sun though we do sell J > >>the best 2 way and 4 way x86/AMD64 boxes so why would you go elsewhere > >>anyway.  > >  > >  > >     You know damn well why.  > >  > 9 > Could OpenVMS not running on Opteron be your problem ??   H Actually, it's OpenVMS's problem. They just haven't figured it out yet -G not likely to, either. I'm the only person in the world who understands  that.    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Mon, 18 Oct 2004 16:53:34 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> # Subject: Question about Descriptors , Message-ID: <41742D41.D46B5DB7@teksavvy.com>  L When descriptors were originally designed, why did they not put 2 lengths in the structure ?    	dsc$w_alloc 	dsc$w_size    ?   L This way, you would have a descriptor where you know its maximum length, but+ also know how many bytes are actually used.   N In their current incarnation, one must keep a separate variable, and sometimesK flip values when you need to supply a descriptor to a routine that uses the L dsc$w_length to find out the size of string, and then put back the allocatedF buffer length when calling another routine that will fill that buffer.  M I realise it can't be changed now. But am curious about historical resons for * the choice of descriptor structure format.   ------------------------------  # Date: Mon, 18 Oct 2004 21:16:45 GMT & From: John Reagan <john.reagan@hp.com>' Subject: Re: Question about Descriptors 2 Message-ID: <1pWcd.1081$ha5.1044@news.cpqcorp.net>   JF Mezei wrote: N > When descriptors were originally designed, why did they not put 2 lengths in > the structure ?  >  > 	dsc$w_alloc
 > 	dsc$w_sizeO >  > ?  > N > This way, you would have a descriptor where you know its maximum length, but- > also know how many bytes are actually used.l > P > In their current incarnation, one must keep a separate variable, and sometimesM > flip values when you need to supply a descriptor to a routine that uses thecN > dsc$w_length to find out the size of string, and then put back the allocatedH > buffer length when calling another routine that will fill that buffer. > O > I realise it can't be changed now. But am curious about historical resons forw, > the choice of descriptor structure format.  F The CLASS_D descriptor is used for dynamically-sized strings (managed I through the varous STR$ routines in LIBRTL) that you have in BASIC.  The  H CLASS_S descriptor was for the fixed-sized strings you have in Fortran. I   The C language and null-terminated strings were not a key component of o the descriptor designs.i  I For dynamically-sized strings that aren't managed via the STR$ routines, rF we have the CLASS_VS descriptor where the DSC$W_LENGTH is the maximum D length and the first word pointed by the DSC$A_POINTER contains the B current length.  That is what Pascal uses for VARYING OF CHAR and * STRING.  I suspect PL/I uses them as well.  B On could certainly invent some sort of CLASS_NTS (null-terminated H string) which contained the maximum length but required you to scan for I the null to find the current length.  However that would have value only  E   when you want to pass it to a routine that would want to update it -F (your example above).  If you are passing a null-terminated string to H some system routine that just reads the string (LIB$SPAWN for example), E a CLASS_S descriptor works just fine.  Just fill in the DSC$W_LENGTH 1F with the strlen() and jam the char array's address into DSC$A_POINTER.  C Nobody has ever come forward with a serious proposal to add such a >A descriptor type.  I can't see how that having both 'maxsize' and rI 'currentsize' in the descriptor would be much of a help.  You still have eG to keep the 'currentsize' valid by hand.  Routines like strcat(), etc. (C that just take the address of strings won't know that they need to f update your descriptor.w     -- d John Reagani/ HP Pascal/{A|I}MACRO for OpenVMS Project Leaderg Hewlett-Packard Company    ------------------------------  % Date: Mon, 18 Oct 2004 18:06:32 -0400s# From: sol gongola <sol@adldata.com>h' Subject: Re: Question about Descriptorsh+ Message-ID: <41743E68.15C418C4@adldata.com>e   JF Mezei wrote:  > N > When descriptors were originally designed, why did they not put 2 lengths in > the structure ?a >  >         dsc$w_alloc  >         dsc$w_size >  > ?n > N > This way, you would have a descriptor where you know its maximum length, but- > also know how many bytes are actually used.  > P > In their current incarnation, one must keep a separate variable, and sometimesM > flip values when you need to supply a descriptor to a routine that uses thetN > dsc$w_length to find out the size of string, and then put back the allocatedH > buffer length when calling another routine that will fill that buffer. > O > I realise it can't be changed now. But am curious about historical resons fors, > the choice of descriptor structure format.  : How would you define the length of actually used contents?9 With alphanumeric strings, why would you prefer C's null t> terminated length over the more commonly used fortran strings ; padded with "blanks". Fortran already has ways to get both -8 values. LEN(string) gives you the length of the fields. < The actual data length is available with LEN_TRIM in compaq " fortran, or LNBLNK in some others.  = On the other hand, why would you assume that strings have to n< have only printable characters. The null character has every/ right to be considered part of the information.l   sol    ------------------------------  % Date: Mon, 18 Oct 2004 15:19:22 -0700 # From: "Tom Linden" <tom@kednos.com>=' Subject: Re: Question about Descriptors ( Message-ID: <opsf26ykqrzgicya@hyrrokkin>  I On Mon, 18 Oct 2004 21:16:45 GMT, John Reagan <john.reagan@hp.com> wrote:L   > JF Mezei wrote:UF >> When descriptors were originally designed, why did they not put 2  
 >> lengths inT >> the structure ? >>  	dsc$w_alloc >> 	dsc$w_size >>  ?TF >>  This way, you would have a descriptor where you know its maximum   >> length, but. >> also know how many bytes are actually used.J >>  In their current incarnation, one must keep a separate variable, and   >> sometimesL >> flip values when you need to supply a descriptor to a routine that uses   >> theG >> dsc$w_length to find out the size of string, and then put back the  C >> allocatedI >> buffer length when calling another routine that will fill that buffer.NH >>  I realise it can't be changed now. But am curious about historical  
 >> resons for=- >> the choice of descriptor structure format.X >JI > The CLASS_D descriptor is used for dynamically-sized strings (managed  oL > through the varous STR$ routines in LIBRTL) that you have in BASIC.  The  K > CLASS_S descriptor was for the fixed-sized strings you have in Fortran.  .L >   The C language and null-terminated strings were not a key component of   > the descriptor designs.- >-L > For dynamically-sized strings that aren't managed via the STR$ routines,  I > we have the CLASS_VS descriptor where the DSC$W_LENGTH is the maximum  fG > length and the first word pointed by the DSC$A_POINTER contains the  sE > current length.  That is what Pascal uses for VARYING OF CHAR and  o, > STRING.  I suspect PL/I uses them as well. Yes it does.   >.E > On could certainly invent some sort of CLASS_NTS (null-terminated  dK > string) which contained the maximum length but required you to scan for  RL > the null to find the current length.  However that would have value only  H >   when you want to pass it to a routine that would want to update it  I > (your example above).  If you are passing a null-terminated string to  .K > some system routine that just reads the string (LIB$SPAWN for example),  MH > a CLASS_S descriptor works just fine.  Just fill in the DSC$W_LENGTH  H > with the strlen() and jam the char array's address into DSC$A_POINTER. >lF > Nobody has ever come forward with a serious proposal to add such a  D > descriptor type.  I can't see how that having both 'maxsize' and  L > 'currentsize' in the descriptor would be much of a help.  You still have  J > to keep the 'currentsize' valid by hand.  Routines like strcat(), etc.  F > that just take the address of strings won't know that they need to   > update your descriptor.  >v >        --  C Using Opera's revolutionary e-mail client: http://www.opera.com/m2/    ------------------------------  % Date: Mon, 18 Oct 2004 19:51:38 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>-' Subject: Re: Question about Descriptorse, Message-ID: <417456F4.97F86777@teksavvy.com>   John Reagan wrote:D > Nobody has ever come forward with a serious proposal to add such aB > descriptor type.  I can't see how that having both 'maxsize' andJ > 'currentsize' in the descriptor would be much of a help.  You still have+ > to keep the 'currentsize' valid by hand. 5  K Not if the systenm routines were to fill the "currentsize" as they fill ther buffer up to the "maxsize".a  I Right now, they fill the buffer up to maxsize, and return , in a separaterM argument, the currentsize. So the calling program must keep that current sizehK as a separate variable. It would have been nice if descriptors had had botho from day 1.I  K I realise it is too late now. Just wondering if there had been any thoughts 5 about this when descriptors were originally designed.I   ------------------------------  % Date: Tue, 19 Oct 2004 08:26:26 +0800 @ From: Tim Sneddon <first-initiallastname@bsddotinfomedia.com.au>' Subject: Re: Question about Descriptors + Message-ID: <2tj59jF1v55b7U1@uni-berlin.de>u   JF Mezei wrote:e > John Reagan wrote: > D >>Nobody has ever come forward with a serious proposal to add such aB >>descriptor type.  I can't see how that having both 'maxsize' andJ >>'currentsize' in the descriptor would be much of a help.  You still have+ >>to keep the 'currentsize' valid by hand. e >  > M > Not if the systenm routines were to fill the "currentsize" as they fill the  > buffer up to the "maxsize".d > K > Right now, they fill the buffer up to maxsize, and return , in a separatewO > argument, the currentsize. So the calling program must keep that current sizea  J What is wrong with using a DSC$K_CLASS_S string and passing the address ofJ DSC$W_LENGTH for the length argument too? The following is some BLISS code that explains what I mean:       literal- 	K_DCLBUF_MAX		= 4096;  	     local ' 	dclbuf			: vector[K_DCLBUF_MAX, byte],W! 	dcldsc			: $bblock[DSC$S_DSCDEF]r2 				  preset([dsc$w_length] = %allocation(dclbuf),$ 					 [dsc$b_dtype] = DSC$K_DTYPE_T,$ 					 [dsc$b_class] = DSC$K_CLASS_S,  					 [dsc$a_pointer] = dclbuf);       ! ...snip...     !c       lib$get_foreign(dcldsc,p 		    0, 		    dcldsc[dsc$w_length],s	 		    0);r  H There is no need to have a seperate variable. Just use DSC$W_LENGTH fromH the descriptor. If the string is needed later (in it's full length) just2 initialize that field before using the descriptor.  M > as a separate variable. It would have been nice if descriptors had had botha
 > from day 1.m  G I have never felt there is a need for this. Not when you have somethingh like DSC$K_CLASS_VS.   > M > I realise it is too late now. Just wondering if there had been any thoughtse7 > about this when descriptors were originally designed.S    
 Regards, Tim.6   ------------------------------  % Date: Mon, 18 Oct 2004 22:28:07 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> ' Subject: Re: Question about Descriptorsy, Message-ID: <41747B97.93AD2602@teksavvy.com>   Tim Sneddon wrote:L > What is wrong with using a DSC$K_CLASS_S string and passing the address ofL > DSC$W_LENGTH for the length argument too? The following is some BLISS code > that explains what I mean:  K Yeah, but still requires that you hold the allocated size separately so you H can reset the Ddsc$w_length field after you'd used the field to indicate current string length.  J I know how to work with the current design. But just wondered if there wasM some reason they didn't put in the 2 lengts (used, allocated) in the original C description definitions which would have made for cleaner programs.r   ------------------------------  % Date: Tue, 19 Oct 2004 02:41:49 +0000M7 From: David B Sneddon - bigpond <dbsneddon@bigpond.com>-' Subject: Re: Question about Descriptorsc* Message-ID: <41747EED.6050607@bigpond.com>   JF Mezei mentioned in passing: > Tim Sneddon wrote: > L >>What is wrong with using a DSC$K_CLASS_S string and passing the address ofL >>DSC$W_LENGTH for the length argument too? The following is some BLISS code >>that explains what I mean: >  > M > Yeah, but still requires that you hold the allocated size separately so youyJ > can reset the Ddsc$w_length field after you'd used the field to indicate > current string length. > L > I know how to work with the current design. But just wondered if there wasO > some reason they didn't put in the 2 lengts (used, allocated) in the originalaE > description definitions which would have made for cleaner programs.g >   ) How would it make for "cleaner" programs?t   Regards, Dave.- -- -I David B Sneddon (dbs)    VMS Systems Programmer     dbsneddon@bigpond.com I Sneddo's quick guide ...          http://www.users.bigpond.com/dbsneddon/DI DBS freeware at ...   http://www.users.bigpond.com/dbsneddon/software.htmsI "Life is what happens to you while you're busy making other plans" Lennon    ------------------------------  % Date: Tue, 19 Oct 2004 11:32:24 +0800 @ From: Tim Sneddon <first-initiallastname@bsddotinfomedia.com.au>' Subject: Re: Question about Descriptors + Message-ID: <2tjg68F209q38U1@uni-berlin.de>p   JF Mezei wrote:  > Tim Sneddon wrote: > L >>What is wrong with using a DSC$K_CLASS_S string and passing the address ofL >>DSC$W_LENGTH for the length argument too? The following is some BLISS code >>that explains what I mean: >  > M > Yeah, but still requires that you hold the allocated size separately so youoJ > can reset the Ddsc$w_length field after you'd used the field to indicate > current string length.  I That's what constants/literals/pre-processor directives are for. Which isl what my example showed.:   > L > I know how to work with the current design. But just wondered if there wasO > some reason they didn't put in the 2 lengts (used, allocated) in the originalfE > description definitions which would have made for cleaner programs.i  I I don't understand what you mean by cleaner. The steps needed to allocatexJ a static string descriptor require the use of a constant to set the length& of the buffer it will point to anyway.  
 Regards, Tim.    ------------------------------  % Date: Mon, 18 Oct 2004 17:24:58 -0400P From: norm.raphael@metso.comG Subject: Re: Routine to Resubmit print/batch entries from queue listingyQ Message-ID: <OF5C7DE24D.BA028DB1-ON85256F31.00757B8D-85256F31.0075BF2C@metso.com>t  + This is a multipart message in MIME format.g" --=_alternative 0075BF2885256F31_=, Content-Type: text/plain; charset="US-ASCII"  : Perhaps this is what you want (with homage to Mr. Parris):  
 $! FIXQUE.COM G $!  Copyright (c) 1991,1992 Digital Equipment Corporation.  All rights  	 reserved.mK $! - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - i -2J $! Procedure to try and gather all possible information out of an existing5 $! queue file, to prepare for an attempt at recovery.  $!I $! As output, creates a command procedure called FIXQUE_RELOAD.COM which t can ; $! be run to restore the previously existing queues, jobs, o characteristics,? $! and form definitions after creating a new, empty queue file.: $!7 $! Parameters to control operation, mostly for testing:h@ $!      V4      Parse assuming VMS 4.x SHOW QUEUE listing formatA $!      V5      Parse assuming VMS 5.x SHOW QUEUE listing format -
 (x=0,1,2,3,4)PI $!      V5.5    Parse assuming VMS 5.5 or later SHOW QUEUE listing formatuI $!      V6      Parse assuming VMS 6.x or later SHOW QUEUE listing formato= $!              (correction for DESCRIPTION field shift 1/99)MJ $!         (default is to look at the running system to determine version)= $!      RERUN   Run using old .LIST files from a previous run- $!G $!                                               Keith B. Parris 5/89, s 10/91a $! keith.parris@cxo.mts.dec.comrH $!                                               or parris@eisner.decus.  D "Fred Hoenisch" <Fred.Hoenisch@gems9.gov.bc.ca> wrote on 10/18/2004  11:59:55 AM:  H > Sorry, I see my wording wasn't very clear.  I specifically don't want  theaJ > routine to generate a queue listing file - I want to resubmit jobs from  anI > older (historic) queue file (ie. I did the SHOW /QUEUE /FULL /ALL /OUT=t > earlier).a > $ > Thanks for the responses thus far. >  > Yours truly, > Fred.c >  >   " --=_alternative 0075BF2885256F31_=+ Content-Type: text/html; charset="US-ASCII"t    F <br><font size=2><tt>Perhaps this is what you want (with homage to Mr. Parris):</tt></font> <br>. <br><font size=2><tt>$! FIXQUE.COM</tt></font>G <br><font size=2><tt>$! &nbsp;Copyright (c) 1991,1992 Digital Equipment 3 Corporation. &nbsp;All rights reserved.</tt></font>sG <br><font size=2><tt>$! - - - - - - - - - - - - - - - - - - - - - - - -J% - - - - - - - - - - - - -</tt></font>nL <br><font size=2><tt>$! Procedure to try and gather all possible information out of an existing</tt></font>V <br><font size=2><tt>$! queue file, to prepare for an attempt at recovery.</tt></font># <br><font size=2><tt>$!</tt></font>mW <br><font size=2><tt>$! As output, creates a command procedure called FIXQUE_RELOAD.COM- which can</tt></font>nI <br><font size=2><tt>$! be run to restore the previously existing queues,e" jobs, characteristics,</tt></font>H <br><font size=2><tt>$! and form definitions after creating a new, empty queue file.</tt></font>o# <br><font size=2><tt>$!</tt></font>lX <br><font size=2><tt>$! Parameters to control operation, mostly for testing:</tt></font>H <br><font size=2><tt>$! &nbsp; &nbsp; &nbsp;V4 &nbsp; &nbsp; &nbsp;Parse6 assuming VMS 4.x SHOW QUEUE listing format</tt></font>H <br><font size=2><tt>$! &nbsp; &nbsp; &nbsp;V5 &nbsp; &nbsp; &nbsp;ParseD assuming VMS 5.x SHOW QUEUE listing format (x=0,1,2,3,4)</tt></font>L <br><font size=2><tt>$! &nbsp; &nbsp; &nbsp;V5.5 &nbsp; &nbsp;Parse assuming6 VMS 5.5 or later SHOW QUEUE listing format</tt></font>H <br><font size=2><tt>$! &nbsp; &nbsp; &nbsp;V6 &nbsp; &nbsp; &nbsp;Parse? assuming VMS 6.x or later SHOW QUEUE listing format</tt></font>aS <br><font size=2><tt>$! &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(corrections- for DESCRIPTION field shift 1/99)</tt></font>vG <br><font size=2><tt>$! &nbsp; &nbsp; &nbsp; &nbsp; (default is to looko7 at the running system to determine version)</tt></font>uF <br><font size=2><tt>$! &nbsp; &nbsp; &nbsp;RERUN &nbsp; Run using old* LIST files from a previous run</tt></font># <br><font size=2><tt>$!</tt></font>eH <br><font size=2><tt>$! &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;L &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;J &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Keith B. Parris 5/89, 10/91</tt></font>H <br><font size=2><tt>$! &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;L &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;K &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; keith.parris@cxo.mts.dec.com</tt></font>iH <br><font size=2><tt>$! &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;L &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;F &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; or parris@eisner.decus.</tt></font> <br>T <br><font size=2><tt>&quot;Fred Hoenisch&quot; &lt;Fred.Hoenisch@gems9.gov.bc.ca&gt;$ wrote on 10/18/2004 11:59:55 AM:<br> <br>J &gt; Sorry, I see my wording wasn't very clear. &nbsp;I specifically don't want the<br>G &gt; routine to generate a queue listing file - I want to resubmit jobs  from an<br> F &gt; older (historic) queue file (ie. I did the SHOW /QUEUE /FULL /ALL	 /OUT=<br>r &gt; earlier).<br>	 &gt; <br> + &gt; Thanks for the responses thus far.<br>e	 &gt; <br>  &gt; Yours truly,<br>i &gt; Fred.<br>	 &gt; <br>p	 &gt; <br>r </tt></font>$ --=_alternative 0075BF2885256F31_=--   ------------------------------  # Date: Mon, 18 Oct 2004 17:57:22 GMThA From: "Colin Butcher" <colin_DOT.butcher_AT@xdelta_DOT.co_DOT.uk> # Subject: Re: RZ28B-VA drives wantedt< Message-ID: <6uTcd.10938$xb.4173@text.news.blueyonder.co.uk>   And where are you located?   -- h   Hope this helps, Colin.i) colin DOT butcher AT xdelta DOT co DOT ukfL Systems Archaeologist - Investigation & troubleshooting of older systems and	 networks.n   ------------------------------  % Date: Mon, 18 Oct 2004 12:18:56 -0700t, From: James Nykiel <jnykiel@access4less.net># Subject: Re: RZ28B-VA drives wanteds< Message-ID: <pan.2004.10.18.19.18.56.765839@access4less.net>  8 On Mon, 18 Oct 2004 17:57:22 +0000, Colin Butcher wrote:   > And where are you located?  $ Culver Oregon 97734 - United States.   ------------------------------  % Date: Mon, 18 Oct 2004 16:09:09 -0700 , From: James Nykiel <jnykiel@access4less.net># Subject: Re: RZ28B-VA drives wanted < Message-ID: <pan.2004.10.18.23.09.05.201523@access4less.net>  
 Greetings:    H I have a few items that I would be willing to offer up for trade for the+ (2) RZ28-VA drives if anyone is interested.    (1) RZ26N-VA (1) RZ28D-Eu (1) RZ29B-VW (1) RRD46-AB (white bezel).l1 (1) Elsa GLoria Synergy-8 (includes manual & cd).n     Thanks - Jim    7 On Sun, 17 Oct 2004 21:46:52 -0700, James Nykiel wrote:    > Greetings: >  > I > I am assembling a BA353 StorageWorks enclosure for use with my hobbyist-H > system and would like to obtain (2) RZ28B-VA drives.  Unfortunately myA > budget is fairly limited at this time so try and keep the price : > affordable if you can.  Please email me with your offer. >  >  > Thanks - Jim   ------------------------------  % Date: Mon, 18 Oct 2004 16:42:30 -0700u, From: James Nykiel <jnykiel@access4less.net># Subject: Re: RZ28B-VA drives wanteds< Message-ID: <pan.2004.10.18.23.42.23.124209@access4less.net>  
 Greetings:     Forgot to mention another item:i  	 (1) DE500s   Thanks - Jim  7 On Mon, 18 Oct 2004 16:09:09 -0700, James Nykiel wrote:e   > Greetings: >  > J > I have a few items that I would be willing to offer up for trade for the- > (2) RZ28-VA drives if anyone is interested.o >  > (1) RZ26N-VA
 > (1) RZ28D-Ea > (1) RZ29B-VW > (1) RRD46-AB (white bezel).p3 > (1) Elsa GLoria Synergy-8 (includes manual & cd).  >  >  > Thanks - Jim >  > 9 > On Sun, 17 Oct 2004 21:46:52 -0700, James Nykiel wrote:  > 
 >> Greetings:i >> : >>  J >> I am assembling a BA353 StorageWorks enclosure for use with my hobbyistI >> system and would like to obtain (2) RZ28B-VA drives.  Unfortunately my B >> budget is fairly limited at this time so try and keep the price; >> affordable if you can.  Please email me with your offer.  >> 0 >> : >> Thanks - Jim    ------------------------------  % Date: Mon, 18 Oct 2004 19:49:36 -0500e2 From: David J Dachtera <djesys.nospam@comcast.net># Subject: Re: RZ28B-VA drives wantedM+ Message-ID: <4174649F.6DF72BEC@comcast.net>    James Nykiel wrote:  >  > Greetings: > ! > Forgot to mention another item:  >  > (1) DE500>  D Do you have non-VMS drivers for it? (Preferably NDIS(any) for MS-DOS% V6.22 and later and/or W/9x drivers.)    -- t David J Dachtera dba DJE Systemsd http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/r   ------------------------------  % Date: Mon, 18 Oct 2004 18:20:15 -0700c, From: James Nykiel <jnykiel@access4less.net># Subject: Re: RZ28B-VA drives wantedn< Message-ID: <pan.2004.10.19.01.19.17.650459@access4less.net>   David,   Will this help?a  H http://h18003.www1.hp.com/support/digital_networks_archive/nics/drivers/   - Jim   ; On Mon, 18 Oct 2004 19:49:36 -0500, David J Dachtera wrote:n   > James Nykiel wrote:n >>  
 >> Greetings:  >>  " >> Forgot to mention another item: >> t >> (1) DE500 > F > Do you have non-VMS drivers for it? (Preferably NDIS(any) for MS-DOS' > V6.22 and later and/or W/9x drivers.)s   ------------------------------  % Date: Mon, 18 Oct 2004 16:44:26 -04001- From: JF Mezei <jfmezei.spamnot@teksavvy.com>c9 Subject: Re: Simulating monochrome to test Xwindows app ?-, Message-ID: <41742B1D.CDDACB38@teksavvy.com>   Fred Kleinsorge wrote:J > There is also DECW$BITONAL (again true/false) which makes it Black/White > only.  > ' > These are SPX-specific logical names.>   Thanks.   > > The SPX card was designed as a 24-plane 3D graphics option.   K So, is there some magic undocumented jumper that can be removed to make thew SPX into a 24 bit 3d card ? :-)   K > However, you should not use this for anything anyway.  You should look atiN > the visuals instead.  Even if a pixmap format of 24 is possible, it's pretty* > useless unless you have a 24 bit visual.  H > X11 *never* converts colors automatically.  Some X11 emulators on PC's > might.  K OK, I took a XPM generated pixmap converted to UIL file with a colour tablen that uses colours such as :s  , colour1:	colour("#3F3F3F3F3F3F",foreground);  ' Now, wouldn't those colours be 24 bit ?a  M Also, I remember reading a bit about the issue of foreground/background which N allows a bitonal server to decide whether a colour should be rendered as white	 or black.   H I find it very odd that X would not have tackled colour depths properly,L considering that Apple had colour support from teh start (even if early macsL didn't actually have colour, software supported colours and then, any colour8 application ran fine on bitonal displays and vice versa.   ------------------------------  % Date: Mon, 18 Oct 2004 18:24:00 -0500D/ From: Chris Scheers <chris@applied-synergy.com>-9 Subject: Re: Simulating monochrome to test Xwindows app ?p2 Message-ID: <41745090.6090700@applied-synergy.com>   JF Mezei wrote:1 > Fred Kleinsorge wrote: > M > OK, I took a XPM generated pixmap converted to UIL file with a colour table  > that uses colours such as :  > . > colour1:	colour("#3F3F3F3F3F3F",foreground); > ) > Now, wouldn't those colours be 24 bit ?   F You select the colors that you want, then the visual maps them to the  actual hardware.  A I don't remember for sure, but it is quite possible that the SPX s' hardware supports 24 bit color entries.o  I What you do need to keep in mind, however, is that the SPX hardware only nF has 256 color map slots, so you can only have (at most) 256 different  colors on the screen at a time.r  G -----------------------------------------------------------------------c$ Chris Scheers, Applied Synergy, Inc.  B Voice: 817-237-3360            Internet: chris@applied-synergy.com    Fax: 817-237-3074   ------------------------------  % Date: Mon, 18 Oct 2004 19:41:31 -0500m2 From: David J Dachtera <djesys.nospam@comcast.net> Subject: Re: VMS for the blind* Message-ID: <417462BB.C4F3038@comcast.net>   Zachary wrote: > < > "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message( > news:4172D165.8D1B0603@teksavvy.com...I > > Perhaps it would help if you could provide a lots of applications youe
 > > intendH > > or use on VMS, and whether you access it through a character cell or > > Xwindows interface.h > >  > > K > > There is a xwindow utility called "Magnify screen" which is supposed to  > > let L > > you look at the screen with a magnifying glass. (although I can't get it > > toK > > work properly right now). May not help if you are totally blind though.- > M > By the way, does anyone know what happened to the Deathrow OpenVMS cluster?eN > That is the cluster I signed up on.  It seems to have completely disappearedK > today.  At least for me.  This is odd, because other sites I've used have>  > also vanished without a trace.  C Some folks use a dynamic DNS service and that can be challenging at  times.   --   David J Dachtera dba DJE Systemsn http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Tue, 19 Oct 2004 08:30:29 +0930n: From: "Barratt, Chris (FMC)" <Chris.Barratt@fmc.sa.gov.au>< Subject: RE: VMS related water bound powerful mammal artworkP Message-ID: <E829CF9B8F94014887EBC61E1951B0CE0575BCD5@sagemshs001.fmc.sa.gov.au>  K Should have stuck with the shark....after all, I'm sure they eat penguins !  :-)    > -----Original Message-----E > From: Bob Koehler [mailto:koehler@eisner.nospam.encompasserve.org] n% > Sent: Monday, 18 October 2004 23:35  > To: Info-VAX@Mvb.Saic.Comu> > Subject: Re: VMS related water bound powerful mammal artwork > @ > In article <f30679fb.0410161427.6c17456d@posting.google.com>, 2 > fabiopenvms@yahoo.com.br (Fabio Cardoso) writes: > ; > > There is a great fauna (Linux Tux,  MS Bugs... why not o > OpenVMS Sharks)! > @ >    If you go to the VMS home page you'll find that HP now has  > a logo forC >    VMS:  the curly arrow.  Deriviation left to the easily amused.i >    ------------------------------  % Date: Mon, 18 Oct 2004 19:38:34 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net>D Subject: Re: VTfm - OpenVMS file manager for VT-compatible terminals+ Message-ID: <4174620A.E47B6086@comcast.net>d   vershinin-vk@mtu-net.ru wrote: > D > I present the new release 2.2-6 of my freeware open source programG > VTfm which is a Norton Commander-style file manager for OpenVMS. VTfmm- > works on VAX, Alpha and IA64 under OpenVMS.t >   > You can download VTFM.ZIP fromH > http://eisner.encompasserve.org/~vershinin/vtfm.zip, unzip archive and > read README.TXT in [.VTFM].a  C I pulled the source for this down and uploaded it to HP's testdrivelG cluster and compiled/linked it on both Alpha and Itanic. The process onc Itanic was MARKEDLY slower!c   -- p David J Dachtera dba DJE Systemse http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page:e" http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/r   ------------------------------   End of INFO-VAX 2004.580 ************************ted issues that result in a dual-core CPU not L > offering as large of a performance increase as what you'd get if you had a- > system with dual CPUs in separate packages.   B IIRC Montecito has private on-chip caches for each core (the POWERI architecture has been more flexible in this regard).  The main compromise L (aside from being by far the largest processor chip I've ever heard of - 580H mm^2, by some accounts) ma&4CVm#wQv3HgZ;p$-),x
jG[$UFp'*'d
Ջ6~cտN6b'&nd$i*fv6!SaXN0&)4E, "AJ E&&
f!WmJtQ5Ю~}؋#~FFQdFYAUI+^}kONx⠵kYn7 -9CZ]Y)ZFb~/8Q9޸Yw~CݫgG9MF2	V]V5 W8h)xF9ʿ}=",H^/ǜ_Y"'>.E2!sy8&8~\k\g("g
"c9*ɦaH&X5GC	X1X́>$Px|9
VYCu˜sv+,U%7(o26jfUыR5DL&
緟	
UjT#@U梱Q	;YQ[G,\k9>ッ}EuuY&z{d1` FN3I;%ǫ:nDܕkd:Ba= 
bPKAxyuՉM-ƪIԆ؈'@-|$hؙ'$j$up4i8׭'k0!sD"9l%%O0QHk]*7V0ac8
k>4Z8Kk7ܧ#ɩA(N\3Ň9I,=U0lŘw~1~:&ÌlAS &,Cf\S(C+w4MND)pܐ.|0[|Hp؜NWzw
=d$GB)BkMFI;k`JHs :~NM_h1'3p+{2@5Tqmݦ0K<ްJ,
s8y>WIEaS*rqj<³t$SlS|N_}	H'O^8Ig3^6WSA$<ᕅ_āY7Z㟗(OGP.9`J7WAkq#(PU	ȳ HS5.'s}S^zRfI&xBFMj81~dQ&Tbhc:p!_Wʍ5&PdS6ˆMjx$5i^]LLEuPڼ8ZXfpT/\1Orc4AR!)Ǻ1?V|f=_.?'_2#LY|SU*]ui]75R/l; ڷ%DO^ϰI	_-\U6'%g(&JEg&,2Hl,|M.Fb$Z
~<Φ2p[x34p߃<&GC:AOi+	; A㺀b6KP?< CNR}LuMw@u/*l5nДR!9KT1G썮`Y9BQmkr&αXiQ]ON\'N~VٺqHoP`x9y|#<g/僧U.bZPuJ'P%AS >Ne"M>lK<zjٔJ N	TrˎiMo~Z8N8%k45eD@;hr5F$^Jj?-?O>C)OreűMLYd,Y Al#V'gٕfSFU9ż[/Rdp$NJ<!
Su_u鍶>vHȃXXW
TK;/Wlq-ib a/}^QVC̻q[ƛX?8bERg4/\:AP5q:HWI@]U6CP=B$"Fhѹ<5p~t	wRVjdh9LINT-ՌpV  rP|BH# lάQqN`hN\cS	h"fM& C
;tՇ<


z~ŵ#W֤ɂ+Ԗ}*G}8wRfV80L[<''('dS̚N*@֙HɗB:##H r	Eکy;
AD2({I@bǐR^yhRA1 j`P./^6%fmC/وEע2}q՛C
BXWțc/\VbX]lO

sz*<5Н! +Hy
Qh я≥B9git,>>r)934'A:e
h轰16,w3ݸ_ǃ2J=U=|n{+S1$%('ɒsn,oQ&wLGJ_ggʀཕ$hJc}D(ۓ);/4:fg`|oerre⒧gt!3~j me>߫JrD,^3}^o }z6@N#agB]@ءϠ]zس)dyƞod7fu3 胂fcQ<
dd$@fLp|KNodJgAM	k.Qddb:cROQ'>2q-p9"j:K_YSC&U0=51Y~;<I,XGf3_B"rK@EssJgAKM?HkA3/nLE7M7tjI3җ|mmmհ?HpG^{bSEiaxR|Q9L9z+W+Oq:@7|cnN܁3ǝJ:j&vǜO$^QN3MDc\4Eذq":Z}~mw:9Tf=Md2I_twGc50tNExfTg o5Rg_l|/B6^jUvy~ǫ註Pw!A*+tI_w*ѭ.%|5H`vBu(8	c[z
/fDd"|	Fʇ'.t샕ɜGr2tt2e֯N5N')*7Yc:)IJO-&A<m88a=ffOrR5L/TL˝
AjZEQ^*xDgVBC@vp6e*XB!Xr!_<	{8,Si]