0 INFO-VAX	Thu, 02 Feb 2006	Volume 2006 : Issue 66      Contents:  Boot Error on Shadowed Sys Disk.$ Re: Boot Error on Shadowed Sys Disk. Re: Cluster timeouts question  Re: DECnet: reconfigure TCPIP? Re: FOR070.DAT files appearing Re: FOR070.DAT files appearing Re: FOR070.DAT files appearing Re: IA64: Montecito info Re: IA64: Montecito info Re: IA64: Montecito info Re: IA64: Montecito info< Re: Intel boycott along with HP if they try to kill OpenVMS! null terminated strings  Re: null terminated strings  Re: Open VMS programing in C: Re: p2c (dave gillespie's pas to c converter) & VMS pascal: Re: p2c (dave gillespie's pas to c converter) & VMS pascal: Re: p2c (dave gillespie's pas to c converter) & VMS pascal: Re: p2c (dave gillespie's pas to c converter) & VMS pascal: Re: p2c (dave gillespie's pas to c converter) & VMS pascal: Re: p2c (dave gillespie's pas to c converter) & VMS pascal: Re: p2c (dave gillespie's pas to c converter) & VMS pascal Re: Phaser 560 and DCPS problem  Re: Phaser 560 and DCPS problem  Re: Phaser 560 and DCPS problem ) Print to (Canon) ImageRunner from OpenVMS  Re: SimH V3.5-2 released Re: SimH V3.5-2 released Re: SimH V3.5-2 released Re: SimH V3.5-2 released' Re: The Pentium Chronicles (2006.01.31) ' Re: The Pentium Chronicles (2006.01.31) , [OT] Vms V1.5 (was Re: SimH V3.5-2 released)  F ----------------------------------------------------------------------   Date: 2 Feb 2006 07:16:42 -0800 " From: dave.baxter@bannerhealth.com) Subject: Boot Error on Shadowed Sys Disk. C Message-ID: <1138893402.161511.185760@o13g2000cwo.googlegroups.com>   C      I currently run a 3-node Prod Cluster (2 x GS1280 (M16), and 1 A ES40).    I am running OpenVMS 7.3-2, fully patched (as far as my B vendor has certified), TCPIP Services V5.4, ECO 4.     The storageD subsystems are EVA5000, and the system disk is in the SAN.    I haveA been running in this configuration for over 18 months without any  issues. D     On Tuesday last I was trying to replace one of the GS1280(M16)'s4 with a new GS1280(M32).     My planned procedure was 1.   Shutdown old M16 G 2.   Give all of the old connections to the new M32 (Interconnect, SAN, 	 Network). D 3.   Boot the new M32 from the same root as was used by the old M16.@ i.e., the new system will take over the Name, DECNet address, IPB address, in other words "the complete identity" of the old system.D Note:    The additional SMP licences etc. were pre-loaded.   Nodes 2/ and 3 remained up and clustered the whole time.    Events.  Shutdown old M16 OK. Connections transfered OK 
 M32 booted OK G Logged in, reconfigured NIC for TCPIP and DECNet, (different Device and  Interface names on new system)( Carried out several boots without issue.   Problem:  G On about the 5th or 6th boot, the new system joined the cluster ok, but C then hung.   Checking the systems which were up, I noticed that the B system disk was in "Mount Verify".   Eventually the booting systemG "timed out (?)" and bugchecked, giving a message, the gist of which was ? "Unable to boot from shadowed system disk".    After the system G bugchecked, the other systems showed the system disk as back to normal. G (Because the new system is 96GB mem, and because of time constraints, I B couldn't wait for a crash dump to write so I Cntrl_P'd out of it).D I INIT'ed the system and tried to boot again, with the same results,C Halted, INITed again, and tried a third time, with the same result.   D At this point, I decided that I didn't have time for further trouble@ shooting and decided to rollback.     I was concerned about thisG because the problem looked to be software, particularly, a problem with E this specific root on the system pack.   I was concerned that the old  M16 might also fail to boot.  E The old system booted up without any problems however. (to my immense  relief).  B Can anyone shed any light on what might have caused this series of events.   F A possible answer occured to me this morning while driving in to work.  It is this;  G 1.     Because of other work which was going on, I had (early in the PM C window) reduced all of my shadowsets to a single member (one of the A EVA's was going to be disconnected from the SAN to be worked on.) * THIS INCLUDED one unit on THE SYSTEM DISK.E 2.     At some point in the procedings, the EVA was brought back into E the SAN, and at this point I ran a script on Node 3 to remount all of C the missing units and resync (all using mini-copy except the system D disk).    The full copy on the system disk would have taken ~30mins.  E I cannot remember the specific time that I ran the REMOUNT script, or < if it coincided with my getting these problems.     HOWEVER:  < IS IT POSSIBLE THAT MY PROBLEM WAS CAUSED BY THE SYSTEM DISK SHADOWCOPYING.  G This might explain why I had no problems with the old hardware, vis. by C the time I swapped all of the connections back, the shadow-copy had 	 finished.   - I would appreciate any comments on this issue    Thanks,  Dave.   ------------------------------   Date: 2 Feb 2006 10:28:19 -0800  From: mckinneyj@saic.com- Subject: Re: Boot Error on Shadowed Sys Disk. C Message-ID: <1138904899.587410.199210@g49g2000cwa.googlegroups.com>   C In a cluster where systems share a common shadowed system disk, all C systems must have access to all shadow members at boot time. You'll D want to insure, using WWIDMGR from the console, that the environmentF variables wwid_ define all your disks and that the N_ variables define@ valid paths to those disks (wwid show -ev). Then insure that theA console variable bootdef_dev on each of the nodes agrees on which  devices are used.    ------------------------------  # Date: Thu, 02 Feb 2006 17:58:44 GMT ( From: Alan Greig <greigaln@netscape.net>& Subject: Re: Cluster timeouts question? Message-ID: <oLrEf.240518$D47.143382@fe3.news.blueyonder.co.uk>    Dan Allen wrote: >  > / > Common for PDP-11's with core memory as well.   D The other part of the trick was for the operating system to respond E quickly to a power failure interrupt. I did read through the TOPS-20  D power failure routine and IIRC the code assumed it had about 1/50th E (might have been less) second to save volatile registers and machine  F state to non-volatile core after receiving the power failure hardware B interrupt. TOPS-20 then entered a loop with a timeout. Should the I timeout expire it assumed a false power failure indication and jumped to  I the recover from power failure code anyway. On a power restart the saved  F state in core was examined to determine if the power fail routine had H completed before the processor halted. If it had then machine state was F reloaded, devices re-initialised and all I/O in progress restarted so F everything ran merrily on. If it hadn't completed then a crash/reboot  was initiated.  H Interactive terminal sessions were detached by default (ATTACH or LOGIN B would get them back as on VMS) to prevent someone else grabbing a - previous interactive session some time later.    --  
 Alan Greig   ------------------------------   Date: 2 Feb 2006 08:35:59 -0800  From: etmsreec@yahoo.co.uk' Subject: Re: DECnet: reconfigure TCPIP? B Message-ID: <1138898159.497910.81190@g44g2000cwa.googlegroups.com>  9 Out of habit (and another way of doing things), I prefer:    LAT then DECnet then  IP then  anything else.  G The reason for this is simple: LAT rarely fails to start (though it may C start on the wrong interface if you haven't set them up correctly!) E whereas things can fail in IP, DECnet etc.  If you want to be able to F connect to your systems from another system on the same LAN if startup screws up, start LAT first!    Steve    Colin Butcher wrote:N > Just habit. Actually it's SCS first (it can tolerate the MAC address change,H > then DECnet (Phase IV addressing changes the MAC address, pure Phase VM > doesn't), then the rest. I generally do IP next, then LAT etc. Don't forget L > that you can stop SCS on an adapter with SCACP (or LAVC$STOP_BUS) and thatF > you can simply remove a DECnet line & circuit from the NCP permanentH > database to stop Phase IV starting on that adapter. Phase V is a whole: > different ballgame - you end up editing the NCL scripts. > M > A handy trick - if you want to prevent DECnet making the MAC address change M > (or indeed any other protocol poking the MAC address), then IP will prevent J > MAC address changes. Can be useful if you have lots of LAN adapters in aL > machine. I usually set up IP on all adapters (with silly addresses in mostK > cases) just so that there's something for most current IP centric network * > folk to see in the ARP cache or to PING. >  > -- >  > Hope this helps, Colin. + > colin DOT butcher AT xdelta DOT co DOT uk G > It's not mine, but I like this definition: Legacy = stuff that works.    ------------------------------   Date: 2 Feb 2006 14:39:49 GMT ( From: bill@cs.uofs.edu (Bill Gunshannon)' Subject: Re: FOR070.DAT files appearing + Message-ID: <44ejtkF1qiknU1@individual.net>   3 In article <M3++I7Xy+tA9@eisner.encompasserve.org>, > 	koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes:\ > In article <droll5$kav$1@news01.intel.com>, Ken Fairfield <my.full.name@intel.com> writes: >>  I >>     I'm afraid both of you are *WAY* out of date...by almost 15 years. I >> IMPLICIT NONE has been Standard Fortran since 1993 when the Fortran 90 H >> standard was formally approved.  When F90 was approved, it became the5 >> single, official, international Fortran standard.   > E >    When Fortran 90 was adopted, it was so different from Fortran 77 F >    that ANSI did something unusual:  it kept the Fortran 77 standardD >    as is, as an existing standard, and adopted Fortran 90 as a new8 >    standard.  I assume Fortran 95 replaced Fortran 90. > E >    I don't know what ISO did with Fortran 77, but as far as ANSI is E >    concerened there is not one single, official, American standard.   D And some of us really don't much care what ISO does!!  Driven mostlyH by international politics it is a safe bet that ISO will choose whatever is most likely to annoy the US.    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: 2 Feb 2006 08:16:26 -0600 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) ' Subject: Re: FOR070.DAT files appearing 3 Message-ID: <M3++I7Xy+tA9@eisner.encompasserve.org>   Z In article <droll5$kav$1@news01.intel.com>, Ken Fairfield <my.full.name@intel.com> writes: > H >     I'm afraid both of you are *WAY* out of date...by almost 15 years.H > IMPLICIT NONE has been Standard Fortran since 1993 when the Fortran 90G > standard was formally approved.  When F90 was approved, it became the 4 > single, official, international Fortran standard.   C    When Fortran 90 was adopted, it was so different from Fortran 77 D    that ANSI did something unusual:  it kept the Fortran 77 standardB    as is, as an existing standard, and adopted Fortran 90 as a new6    standard.  I assume Fortran 95 replaced Fortran 90.  C    I don't know what ISO did with Fortran 77, but as far as ANSI is C    concerened there is not one single, official, American standard.    ------------------------------  % Date: Thu, 02 Feb 2006 08:59:28 -0800 , From: Ken Fairfield <my.full.name@intel.com>' Subject: Re: FOR070.DAT files appearing + Message-ID: <drtdpg$ptg$1@news01.intel.com>    Bob Koehler wrote:\ > In article <droll5$kav$1@news01.intel.com>, Ken Fairfield <my.full.name@intel.com> writes:I >>     I'm afraid both of you are *WAY* out of date...by almost 15 years. I >> IMPLICIT NONE has been Standard Fortran since 1993 when the Fortran 90 H >> standard was formally approved.  When F90 was approved, it became the5 >> single, official, international Fortran standard.   > E >    When Fortran 90 was adopted, it was so different from Fortran 77 F >    that ANSI did something unusual:  it kept the Fortran 77 standardD >    as is, as an existing standard, and adopted Fortran 90 as a new8 >    standard.  I assume Fortran 95 replaced Fortran 90.   Yes and no.   ? I had initially forgotten the thing about ANSI holding onto F77 B as an ANSI Standard, but by the time F95 was approved, about 1998,D ANSI withdrew F77 and there is now just one, official, international; standard for Fortran.  It is the ANSI/ISO F95 standard, but = will be superseded by F2K3 whenever the new standard finishes  the approval process.   > On the point of F90 being so different from F77, F77 is proper@ subset of F90 (but not F95, for "standardeze" technical reasons,E i.e., a few language features were "deprecated", but from a practical C point of view, all extant F95 compilers support standard-conforming @ F77 source code).  In other words, ANSI was a little shy becauseA F90 is so much "bigger" than F77 was.  The user community was not C much better informed since people still talk about "converting" F77 F to F90.  The fact is, the conversion has already been done: F77 source code _is_ F90 code.   < Also note that, unlike C++ for example, the new F90 features; can be added to programs a little bit at a time as you find > you need them, rather than the "all or nothing" that is common experience with C++.  E >    I don't know what ISO did with Fortran 77, but as far as ANSI is E >    concerened there is not one single, official, American standard.   ! Yes there is.  ANSI withdrew F77.    	-Ken  --  6 I don't speak for Intel, Intel doesn't speak for me...  
 Ken Fairfield ! D1C Automation VMS System Support " who:   kenneth dot h dot fairfield where: intel dot com   ------------------------------  % Date: Thu, 02 Feb 2006 08:23:17 +0100 + From: Karsten Nyblad <nospam@nospam.nospam> ! Subject: Re: IA64: Montecito info = Message-ID: <43e1b35f$0$78283$157c6196@dreader1.cybercity.dk>    Dave Froble wrote:F >> If it's a cheap box you want, I suggest going to your local U-Haul - >> store. They sell a great variety of boxes.  >  > I > Your customer relations attitude leaves room for improvement, and that  A > room is great.  IBM and Sun owe you thanks for that little gem.  > C What is the difference between a box from U-haul and a box from HP?    :-)    ------------------------------  % Date: Thu, 02 Feb 2006 06:11:49 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> ! Subject: Re: IA64: Montecito info , Message-ID: <43E1E8E2.2BACDD72@teksavvy.com>   Karsten Nyblad wrote: E > What is the difference between a box from U-haul and a box from HP?   . UHAUL has 2 wheels. HP has 4 wheels (or legs).  1 UHAUL has industry standard interface to the car. * HP has non standard proprietary CPU (IA64)  7 You can put anything in the UHAUL (as long as it fits). G You can only put IA64 specific software inside an HP box, and that is a " small subset of what is available.   ------------------------------   Date: 2 Feb 2006 05:39:23 -0800  From: bob@instantwhip.com ! Subject: Re: IA64: Montecito info C Message-ID: <1138887563.596098.279540@g14g2000cwa.googlegroups.com>   * what about one chip???????????????????????   ------------------------------   Date: 2 Feb 2006 14:15:55 GMT ( From: bill@cs.uofs.edu (Bill Gunshannon)! Subject: Re: IA64: Montecito info + Message-ID: <44eigrF1pborU1@individual.net>   C In article <1138887563.596098.279540@g14g2000cwa.googlegroups.com>,  	bob@instantwhip.com writes:, > what about one chip???????????????????????   # Lay's says you can't eat just one!!   C Why don't you stop being such an idiot and include a little context ; so people can at least have a clue what your talking about.    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: 2 Feb 2006 02:32:03 -0800 + From: "Dr. Dweeb" <comp.os.vms@hotmail.com> E Subject: Re: Intel boycott along with HP if they try to kill OpenVMS! B Message-ID: <1138876323.224211.22680@f14g2000cwb.googlegroups.com>  E I am in Holland just now.  But I get the "subscriber" screen on parts $ I-IV, while part V is still visible.  B I guess they get archived after a few days and then become "pay to view"   	 Dr. Dweeb    ------------------------------   Date: 2 Feb 2006 16:20:47 GMT ( From: bill@cs.uofs.edu (Bill Gunshannon)  Subject: null terminated strings+ Message-ID: <44epquF1rojsU2@individual.net>   F Just an interesting (at least it was to me!) little side note.  PeopleE frequently attack C because of it's use of null terminated strings. I D have pointed out int he pst that this was apparently not unique to CD and Unix as the PDP-11 had a print routine in the Macro Library thatD expected null terminated string.  As another interesting data point,E I am in the process of examining the binary of a Z80 program from the E late 70's or very early 80's and, surpirse, surprise, all the strings A are null terminated.  Being as I know this program was built from C Pascal source, it looks even more like null terminated strings were C pretty much industry standard by the time Unix and C decided to use  them.   C Not saying they are better than anything else, or even a good idea, A just that they seem to have been standard for more than just Unix  and C.   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: Thu, 2 Feb 2006 17:52:26 +0000 (UTC)- From: klewis@OMEGA.MITRE.ORG (Keith A. Lewis) $ Subject: Re: null terminated strings. Message-ID: <drtgsq$p4m$1@newslocal.mitre.org>  s bill@cs.uofs.edu (Bill Gunshannon) writes in article <44epquF1rojsU2@individual.net> dated 2 Feb 2006 16:20:47 GMT: G >Just an interesting (at least it was to me!) little side note.  People F >frequently attack C because of it's use of null terminated strings. IE >have pointed out int he pst that this was apparently not unique to C E >and Unix as the PDP-11 had a print routine in the Macro Library that E >expected null terminated string.  As another interesting data point, F >I am in the process of examining the binary of a Z80 program from theF >late 70's or very early 80's and, surpirse, surprise, all the stringsB >are null terminated.  Being as I know this program was built fromD >Pascal source, it looks even more like null terminated strings wereD >pretty much industry standard by the time Unix and C decided to use >them. > D >Not saying they are better than anything else, or even a good idea,B >just that they seem to have been standard for more than just Unix >and C.   J Yeah, I used ASCIZ data in an assembly language course on LSI-11 machines, so it's not unique to C.  E I got bit by a strange interaction in a PL/I+C integrated app.  I was L creating a string in C using malloc() and passing to PL/I.  Since the stringH was zero-terminated, I figured I didn't need to pass the length.  Wrong!  I I got an access violation on the PL/I SEARCH() function looking for the 0 I (i.e. trying to determine the length).  Apparantly either PL/I or VMS was L loading beyond the string's page because I declared it with a large constantC length in PL/I.  The solution, of course, was to pass in the length K calculated by strlen() as another parameter and use that in the declaration $ (PL/I is quite flexible that way).    0 --Keith Lewis              klewis {at} mitre.org> The above may not (yet) represent the opinions of my employer.   ------------------------------   Date: 2 Feb 2006 08:33:53 -0600 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) % Subject: Re: Open VMS programing in C 3 Message-ID: <A4AgQAi7j4su@eisner.encompasserve.org>   V In article <44btmcF1e5p6U1@individual.net>, Paul Sture <paul.sture@bluewin.ch> writes: > H > My first editor war! My introduction to VMS was with EDT, but the RSX G > die-hards still favoured EDI, and the documentation guy favoured SOS.   D    My 11/780 was burning up much CPU in compatability mode soley dueB    to a couple users using SOS because they didn't want to have to    learn a new editor.  C    So I spent five minutes showing them EDT in full screen mode and 8    they never looked back.  Idle time certainly went up.   ------------------------------  % Date: Thu, 02 Feb 2006 08:45:47 +0000 0 From: Chris Sharman <chris.sharman@sorry.nospam>C Subject: Re: p2c (dave gillespie's pas to c converter) & VMS pascal 4 Message-ID: <drsgrs$3b6$1$8300dec7@news.demon.co.uk>   John Reagan wrote: > Chris Sharman wrote: >  >>I >> I've looked at vms/apache/mysql/php, but standard packages don't seem   >> to work out of the box.' >> Hence the decision to move to linux.  >  > I > What didn't work "out of the box" with these?  I certainly know people  I > who use Apache/php on VMS all the time.  Mysql runs on OpenVMS as well   > if I remember correctly. > K > If there is something we could do better, then let us know and we'll see   > what we can do.   D I had some initial problems with mysql, iirc - something to do with I innodb (using it or not using it - there's a choice of two technologies,  E one is default and must be used for the system tables; the other one   works!).B A few problems with Issue Tracker, and couldn't get either of the 9 shopping carts I tried to work at all. phpMyAdmin was ok. C I'm on Alpha VMS 7.3-1, and unable to upgrade (until we remove our   appletalk dependency).  ? Of course, it may be me, or it may be poor quality packages ... G Moving to Linux, we have cheaper hardware, a very widely used standard  K platform, the choice of hosting services rather than in-house hosting, etc.    Chris    ------------------------------   Date: 2 Feb 2006 08:18:20 -0600 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) C Subject: Re: p2c (dave gillespie's pas to c converter) & VMS pascal 3 Message-ID: <+naw5TFAIfWD@eisner.encompasserve.org>   c In article <43DF83D4.9413.5DCD7575@localhost>, "Stanley F. Quayle" <squayle@insight.rr.com> writes:  > G > There is a version of CHARON-VAX that uses a real-time OS under it.   . > Perhaps that would be more to your liking...  "    That's news to me.  Which RTOS?   ------------------------------   Date: 2 Feb 2006 08:22:07 -0600 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) C Subject: Re: p2c (dave gillespie's pas to c converter) & VMS pascal 3 Message-ID: <7ySIKUTQP+8r@eisner.encompasserve.org>   c In article <43DF83D4.9413.5DCD7575@localhost>, "Stanley F. Quayle" <squayle@insight.rr.com> writes:  > H > I'm not sure where the "shove" would come from.  All Windows services @ > are disabled except for those required by the product.  Also, F > supported configurations require at least 1 processor more than the C > number of VAX processors being emulated.  This allows "overhead"  C > functions and network interface emulation to stay out of the VAX   > processors' way.  A   OK, this invokes a Windows question:  how do I know that my VAX C   will run on one CPU and the Windows kernel and overhead will run  
   on another?   D   Is there a hook in Windows that will force the kernel and overhead?   to only run on one specific processor while attaching the VAX *   emulation task to a different processor?   ------------------------------   Date: 2 Feb 2006 08:25:07 -0600 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) C Subject: Re: p2c (dave gillespie's pas to c converter) & VMS pascal 3 Message-ID: <s1psNUVj6z+E@eisner.encompasserve.org>   g In article <drq70v$smu$1$8302bc10@news.demon.co.uk>, Chris Sharman <chris.sharman@sorry.nospam> writes:  > K > Well, ok, I mean real-time as in "user not tempted to give up or retry",  G > rather than the "got to be there in x ms", that I used to work to in   > aerospace.  H    OK, properly implemented that can be done on just about any platform.G    Users may not even notice delays of up to 500ms, and keep going with      delays of only a few seconds.  D    Which is "forever" compared to a hard real-time system even on a 
    PDP-11/34.    ------------------------------   Date: 2 Feb 2006 08:28:07 -0600 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) C Subject: Re: p2c (dave gillespie's pas to c converter) & VMS pascal 3 Message-ID: <v92SmF5Tqdr2@eisner.encompasserve.org>   d In article <43E0A252.21718.622C7B8B@localhost>, "Stanley F. Quayle" <squayle@insight.rr.com> writes: > E > I agree.  The Task Manager does have a "Realtime" priority option,  H > but that doesn't mean much.  Maybe the Embedded version of Windows is > > designed with deterministic behavior -- that's one possible # > requirement for a "real-time" OS.   B    If you're refering to Windows CE, it is "embedded" but not hardB    real-time, and to a large part because it is not deterministic.  F    To MS, the embedded market is millions of PDAs and cell phones.  MSE    will call CE real-time, but they won't even mention determinism or C    latency.  What they will tell you is that it supports MS Office.    ------------------------------  % Date: Thu, 02 Feb 2006 10:18:34 -0500 2 From: "Stanley F. Quayle" <squayle@insight.rr.com>C Subject: Re: p2c (dave gillespie's pas to c converter) & VMS pascal . Message-ID: <43E1DC7A.22023.370D648@localhost>  ) On 2 Feb 2006 at 8:18, Bob Koehler wrote: D > In article <43DF83D4.9413.5DCD7575@localhost>, "Stanley F. Quayle"G > <squayle@insight.rr.com> writes: > > There is a version of CHARON-VAX E > that uses a real-time OS under it.  > Perhaps that would be more to  > your liking... > $ >    That's news to me.  Which RTOS?   QNX.  
 --Stan Quayle  Quayle Consulting Inc.  
 ----------8 Stanley F. Quayle, P.E. N8SQ  Toll free: 1-888-I-LUV-VAX3 8572 North Spring Ct., Pickerington, OH  43147  USA 0 stan-at-stanq-dot-com       http://www.stanq.com) "OpenVMS, when downtime is not an option"    ------------------------------  % Date: Thu, 02 Feb 2006 10:18:01 -0500 2 From: "Stanley F. Quayle" <squayle@insight.rr.com>C Subject: Re: p2c (dave gillespie's pas to c converter) & VMS pascal - Message-ID: <43E1DC59.9771.3705BF5@localhost>   ) On 2 Feb 2006 at 8:22, Bob Koehler wrote: H >   OK, this invokes a Windows question:  how do I know that my VAX willB >   run on one CPU and the Windows kernel and overhead will run on >   another? > F >   Is there a hook in Windows that will force the kernel and overheadA >   to only run on one specific processor while attaching the VAX , >   emulation task to a different processor?  B Yes.  This became a *very* important issue in the SMP versions of > CHARON-VAX -- processor context-switching was a big killer of B performance.  The emulated VAX processors now grab hold of a host  processor and don't let go.   
 --Stan Quayle  Quayle Consulting Inc.  
 ----------8 Stanley F. Quayle, P.E. N8SQ  Toll free: 1-888-I-LUV-VAX3 8572 North Spring Ct., Pickerington, OH  43147  USA 0 stan-at-stanq-dot-com       http://www.stanq.com) "OpenVMS, when downtime is not an option"    ------------------------------   Date: 2 Feb 2006 08:06:15 -0800 # From: "Galen" <gltackett@gmail.com> ( Subject: Re: Phaser 560 and DCPS problemC Message-ID: <1138896375.873434.200370@g14g2000cwa.googlegroups.com>   D Looks like you could use Northlake Software's PrintKit product. It'sG highly compatible with DCPS, including the standard DCL PRINT commands, F print parameters, and just about all of DCL's job and queue management
 capabilities.   F A license for a single printer is around $400, but they offer a 30 day1 free trial. See their site at http://www.nls.com.   C At another job I used PrintKit with a couple different Xerox Phaser @ models. It worked well for us. (I have no connection at all with Northlake Software.)   ------------------------------  # Date: Thu, 02 Feb 2006 16:23:02 GMT * From: Paul Anderson <paul.anderson@hp.com>( Subject: Re: Phaser 560 and DCPS problem5 Message-ID: <020220061037449444%paul.anderson@hp.com>   C In article <1138839942.678083.287510@g44g2000cwa.googlegroups.com>, + rcyoung <rcyoung@aliconsultants.com> wrote:   G > I am trying to get a Xerox ( Tektronix) Phaser 560 PS printer to work @ > on a Vax ( using the VMS FAQ and the DCPS Management Guide) asF > references. I have DCPS 2.1 installed on VMS 7.3, but the Phaser 560 > is not listed.  G DCPS V2.1 is old.  V2.5 is the current version, although the Phaser 560 ( is not supported in any version of DCPS.  F > I extracted the Xerox Phaser 750 files on a "long shot", and created8 > a new device control library w/ them...so far so good.  C What exactly did you do here?  If you took the Phaser 750 files and D renamed them to "unrecognized" in the new library, good.  (Note thatE DCPS, starting with V2.3, allows you to define the product name for a ? printer queue so you could skip this step with a DCPS upgrade.)   @ > It tries to print (the Phaser light blinks). but then it gives > 7 > Queue PHASER: %DCPS-W-NOT_READY, Printer is not ready  > E > and just "hangs" repeating the above periodically....So close...Any  > ideas of suggestions?   D First, make sure the printer is configured correctly, paying specialF attention to settings for port 9100.  AppSocket settings are describedE in the DCPS documentation.  Also make sure the printer/port is set to   PostScript or automatic sensing.  A If there is still no joy, you could try defining the DCPS NO_SYNC C logical name for the queue as described in the documentation.  This & might help in getting the job started.  E The next problem might be an issue at the _end_ of the job, but let's  take this one step at a time.    Paul   --    Paul Anderson   OpenVMS Engineering    Hewlett-Packard Company    ------------------------------   Date: 2 Feb 2006 08:13:01 -0800 , From: "rcyoung" <rcyoung@aliconsultants.com>( Subject: Re: Phaser 560 and DCPS problemC Message-ID: <1138896781.749683.310270@g49g2000cwa.googlegroups.com>   > I used the "unrecognized" route. Appsocket is set per the DCPSD description (Postscript & InterpreterBased) for another model Phaser> printer (seemed closest to what I had) . I'll try the log fileC generation & the NO_SYNC  and see what I can get to post here later  today.   ------------------------------  $ Date: Thu, 2 Feb 2006 13:50:28 -0500 From: norm.raphael@metso.com2 Subject: Print to (Canon) ImageRunner from OpenVMSQ Message-ID: <OF20EAC852.542069F9-ON85257109.0066FBC9-85257109.00677F72@metso.com>   C Someone in our shop just swapped an HPLJ5N for a Cannon ImageRunner  xsomethingx,G and is now surprised that print from VMS (Via MULTINET_STREAM_SYMBIONT)  dies.   K Does anyone know how to get a simple text file to print to this device.  If 
 I need DCPS I 7 can get it installed, but I have no experience with it.    OpenVMS V7.3-1  Alpha    ------------------------------   Date: 2 Feb 2006 08:37:22 -0600 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) ! Subject: Re: SimH V3.5-2 released 3 Message-ID: <fk1+V+mEG7W+@eisner.encompasserve.org>   x In article <1138612454.529926.236540@g14g2000cwa.googlegroups.com>, "vaxorcist" <hoelscher-kirchbrak@freenet.de> writes:  3 > I have tested the SIMH VAX-11/780 emulator under:  > - VMS V1.5 (new)  G    OK, so that tells me you did include compatability mode.  Seeing how 7    SIMH already had PDP-11 that's an appropriate touch.   @    Can I be sure I'll get OPDEC if I code up a MARK instruction?   ------------------------------  $ Date: Thu, 2 Feb 2006 16:33:42 +0100A From: Christian Corti <Christian.Corti@studserv.uni-stuttgart.de> ! Subject: Re: SimH V3.5-2 released + Message-ID: <kbl9b3-tom.ln1@news.online.de>   C In alt.sys.pdp11 Bob Supnik <bob.supnik@sicortex.nospam.com> wrote: / > Yeah, I knew I should have written this up ;)    ;-)   8 > - Make an image copy of the floppy to your hard drive.  L I've made floppy disk dumps some time ago, file size 256256 bytes per image.8 They include track 0 and all sectors in "natural" order.  H > - Using one of the tools that understands RT11 disk format (PUTR worksH > great on Windows systems), extract the file you need (whether it's VMB: > or standalone backup, etc) to a file on the host system.  C Now here's the next problem: PUTR can't read these disk images. The E console floppy (part no. AS-T213A-DE RSI VAX-11/780 STANDARD CONSOLE)  mounted in PUTR:  ' (C:\TEMP)>mount x: disk.dsk /rx01 /rt11  (C:\TEMP)>dir x: [...]  JKHJKH.JKH 16448  02-XXX-2004  ?Corrupt directory  C *BUT*, running the simh pdp11 simulator I can list the directory of  the same disk image:   sim> set ry0 single  sim> att ry0 disk.dsk  RY: buffering file in memory sim> go  .dir/ful/blo/vol dy0:     Volume ID: 780_CONSOLE   Owner    : HOODG ESZAB .VS0     0  14-Jul-1982    14    CONSOL.SYS    31  14-Jul-1982	14 G VMB   .EXE    33  14-Jul-1982    45    WCS124.PAT    73  14-Jul-1982	78 H ABBREV.HLP     4  14-Jul-1982   151    BOOT  .HLP    13  14-Jul-1982	155H CONSOL.HLP    11  14-Jul-1982   168    ERROR .HLP    19  14-Jul-1982	179H REMOTE.HLP     4  14-Jul-1982   198    WCSMON.HLP     6  14-Jul-1982	202H CRASH .        1  14-Jul-1982   208    CI780 .BIN    36  14-Jul-1982	209H CIBOO .CMD     2  14-Jul-1982   245    CS1BOO.CMD     2  14-Jul-1982	247H CS1GEN.        2  14-Jul-1982   249    DB0BOO.CMD     2  14-Jul-1982	251H DB0BOO.ILV     3  14-Jul-1982   253    DB0GEN.        2  14-Jul-1982	256 [...]   81 Files, 372 Blocks   108 Free blocks  / But that's not the diskette I'm interested in.  H The standalone backup is on disks AS-M759A-BE (VAX/VMS V3.0 S/A BKUP RX1D 1/2) and AS-M760A-BE (BKUP RX1 2/2), and these are *not* RT11 disks.   .dir/ful/blo/vol dy0:     Volume ID: STABACKUPA  Owner    : FIELD  ?DIR-F-Invalid directory   With disk 2:   .dir/ful/blo/vol dy0:     Volume ID: STABACKUPB  Owner    : FIELD  ?DIR-F-Invalid directory  ) Trying to boot disk 2 (it has to fail...)  .boot/foreign dy0:$ STABACKUPB      is not a system disk   HALT instruction [...] sim>  4 Trying to boot the first disk (now mounted at rx0!):
 sim> boot rx0   % HALT instruction, PC: 000006 (000035)     " So I'm completely stuck for now...  	 Christian    ------------------------------   Date: 2 Feb 2006 09:10:00 -0800 2 From: "vaxorcist" <hoelscher-kirchbrak@freenet.de>! Subject: Re: SimH V3.5-2 released C Message-ID: <1138900200.603590.122330@g14g2000cwa.googlegroups.com>   B Someone had a tape image of VMS V1.5 available and I guessed couldE probably be a DSC (Disc Save and Compress) disk backup. I dug deep in 4 my VMS V3 manuals and found help on the DSC command. It is so simple, just: $ RUN SYS$SYSTEM:DSC2  DSC2>DBA2:=MSA0:VAXVMSRL1  and that's all! ? Now I've got a bootable VMS V1.5 RP06 disk image, see yourself:   (   VAX/VMS Version 1.50 12-APR-1979 09:30    A PLEASE ENTER DATE AND TIME (DD-MMM-YYYY  HH:MM)  1-MAY-1979 10:00   G    OPCOM,  1-MAY-1979 10:00:17.70, LOGFILE INITIALIZED, OPERATOR=_OPA0:    $ ! & $ ! VAX/VMS system startup - Release 1 $ !  $ SHOW TIME     1-MAY-1979 10:00:17 $ SET NOVERIFY0 %MOUNT-I-MOUNTED, CONSOLE      mounted on _DXA1:B   Login quotas - Interactive limit=64, Current interactive value=08   SYSTEM       job terminated at  1-MAY-1979 10:00:18.50     Accounting information: D   Buffered I/O count:          136      Peak working set size:    98D   Direct I/O count:             28      Peak virtual size:       110D   Page faults:                 283      Mounted volumes:           1G   Elapsed CPU time:     0 00:00:00.56   Elapsed time:     0 00:00:00.75  Username: SYSTEM	 Password: '         Welcome to VAX/VMS Version 1.50  $  $  $ sh sys9     VAX/VMS  Processes on          1-MAY-1979 10:01:06.36 C     Pid    Process Name     UIC  State Pri Dir. I/O    CPU     Page  flts Ph.Mem ?   00010000 NULL           000,000 COM    0        0 00:01:13.75  0    0?   00010001 SWAPPER        000,000 HIB   16        0 00:00:00.00  0    0?   0001003B ERRFMT         001,006 HIB    7        4 00:00:00.01  28   30 ?   0001003C OPCOM          001,004 LEF    6        2 00:00:00.01  29   34 ?   0001003D JOB_CONTROL    001,004 HIB   11        6 00:00:00.05  31   62 ?   0001003E DBA2ACP        001,003 HIB    9       72 00:00:00.15  33   88 ?   0002003F SYSTEM         001,004 CUR    5        3 00:00:00.04  58   93  $   % Bob, where shall I send the image to? % Is there a FTP-Server to put it onto?  I'm happy to help!     Regards    Ulli   ------------------------------   Date: 2 Feb 2006 09:20:26 -0800 2 From: "vaxorcist" <hoelscher-kirchbrak@freenet.de>! Subject: Re: SimH V3.5-2 released C Message-ID: <1138900826.869974.252620@g49g2000cwa.googlegroups.com>    I think I can help you. G I had problems booting the Stand Alone Backup floppies, too, so I built G Stand Alone Backup on an RP06 disk image. Would you like a copy of such D a disk image? Which Version, V3.0, 3.2 or 3.5? The image is so small5 when compressed that it can be sent via email easily.      Regards    Ulli   P.S.E I'm still looking for VMS V4.1, 4.2 and 4.3 as well as for DECnet-VAX ! V3.x and the VMS V4.7 LAVC Kit -   Can you help me there?   ------------------------------   Date: 2 Feb 2006 02:44:28 -0800 + From: "Dr. Dweeb" <comp.os.vms@hotmail.com> 0 Subject: Re: The Pentium Chronicles (2006.01.31)B Message-ID: <1138877068.447781.74990@o13g2000cwo.googlegroups.com>  B Sadly, CompaQ killed the x86 BLISS compiler just as Rdb/NT started@ shipping. Oracle could not ship a commercial product based on anE unsupported/dead compiler and reportedly tried to buy the compiler to ; maintain themselves.  Apparently the price CompaQ asked was E prohibitively high, so with no real options, Oracle killed the Rdb/NT F release. The product was essentially still born and Oracle swallowed aA big R&D expenditure with little to show for it other than a truly G outstanding Windows database engine that nobody can use, and even fewer  have heard of.  F It is available for download at the Oracle website, should anyone needB a quality database engine for Windoze rather than the crud that is generally available.   All so very sad ...   	 Dr. Dweeb    ------------------------------    Date: 02 Feb 2006 13:53:37 +0100( From: Andreas Davour <ante@update.uu.se>0 Subject: Re: The Pentium Chronicles (2006.01.31)4 Message-ID: <cs9y80tkjla.fsf@Psilocybe.Update.UU.SE>  - "Dr. Dweeb" <comp.os.vms@hotmail.com> writes:   D > Sadly, CompaQ killed the x86 BLISS compiler just as Rdb/NT startedB > shipping. Oracle could not ship a commercial product based on anG > unsupported/dead compiler and reportedly tried to buy the compiler to = > maintain themselves.  Apparently the price CompaQ asked was G > prohibitively high, so with no real options, Oracle killed the Rdb/NT H > release. The product was essentially still born and Oracle swallowed aC > big R&D expenditure with little to show for it other than a truly I > outstanding Windows database engine that nobody can use, and even fewer  > have heard of. > H > It is available for download at the Oracle website, should anyone needD > a quality database engine for Windoze rather than the crud that is > generally available.  G Interesting. Do you have a link? I tried to find it at the Oracle site,  and failed.    /andreas   --  A A: Because it fouls the order in which people normally read text. ' Q: Why is top-posting such a bad thing?  A: Top-posting. ; Q: What is the most annoying thing on usenet and in e-mail?    ------------------------------  $ Date: Thu, 2 Feb 2006 12:24:08 -0500 From: norm.raphael@metso.com5 Subject: [OT] Vms V1.5 (was Re: SimH V3.5-2 released) Q Message-ID: <OF56780894.111A0115-ON85257109.005F676C-85257109.005F983A@metso.com>   I "vaxorcist" <hoelscher-kirchbrak@freenet.de> wrote on 02/02/2006 12:10:00  PM:   D > Someone had a tape image of VMS V1.5 available and I guessed couldG > probably be a DSC (Disc Save and Compress) disk backup. I dug deep in 6 > my VMS V3 manuals and found help on the DSC command. > It is so simple, just: > $ RUN SYS$SYSTEM:DSC2  > DSC2>DBA2:=MSA0:VAXVMSRL1  > and that's all! A > Now I've got a bootable VMS V1.5 RP06 disk image, see yourself:  > * >   VAX/VMS Version 1.50 12-APR-1979 09:30 >   F Wow.  First Version with which I worked, first year I worked on a VAX. Wow!   > [snip] > 	 > Regards  >  > Ulli >    ------------------------------   End of INFO-VAX 2006.066 ************************