INFO-VAX Sun, 13 Jan 2008 Volume 2008 : Issue 25 Contents: Re: "file locked by another user" mystery Re: "file locked by another user" mystery Re: Anyone interested in building a vms-like OS? Re: Anyone interested in building a vms-like OS? Re: Anyway to "smarten up" the console terminal? Re: IA64 VMS installation DVD creation. Re: IA64 VMS installation DVD creation. Re: IA64 VMS installation DVD creation. Re: IA64 VMS installation DVD creation. Re: IA64 VMS installation DVD creation. Re: Mystery of X-windows colours/resources OT - EISNER:: upgrade complete (was:Re: default e-mail editor) Re: OT - EISNER:: upgrade complete (was:Re: default e-mail editor) print queues and IP Re: print queues and IP Request: LD Enhancement to allow "volume groups" Re: Request: LD Enhancement to allow "volume groups" run /detached always fails with loginout.exe Re: run /detached always fails with loginout.exe Re: run /detached always fails with loginout.exe Re: USB-stick Re: USB-stick ---------------------------------------------------------------------- Date: Sat, 12 Jan 2008 16:29:21 -0800 (PST) From: "winston19842005@yahoo.com" Subject: Re: "file locked by another user" mystery Message-ID: <6ca81a6c-bff4-4c6a-bdde-7308f8ffe600@k2g2000hse.googlegroups.com> On Jan 10, 9:37 am, bri...@encompasserve.org wrote: > In article <26e60ac2-0753-40f8-8bfc-9581649f1...@c4g2000hsg.googlegroups.com>, "winston19842...@yahoo.com" writes: > > > As my memory fails, I seem to remember going into a utility and > > executing a command, something about show channels, after a set > > command to setup the file or disk (can't remember) you were interested > > in... > > > Can anybody "reboot" my memory here? I remember it gave me more > > details than a show dev/files... > > $ ANALYZE /SYSTEM > SDA> SET PROCESS /INDEX=xx > SDA> SHOW PROCESS /CHANNELS > > Could that have been it? I don't recall "SET PROCESS/INDEX", but yes, that is it! Thanks for the memory! (I thought I'd be interviewing for a VMS position last week, but alas! No response...) ------------------------------ Date: Sun, 13 Jan 2008 00:46:25 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: "file locked by another user" mystery Message-ID: In article <6ca81a6c-bff4-4c6a-bdde-7308f8ffe600@k2g2000hse.googlegroups.com>, "winston19842005@yahoo.com" writes: > > >On Jan 10, 9:37 am, bri...@encompasserve.org wrote: >> In article <26e60ac2-0753-40f8-8bfc-9581649f1...@c4g2000hsg.googlegroups.com>, "winston19842...@yahoo.com" writes: >> >> > As my memory fails, I seem to remember going into a utility and >> > executing a command, something about show channels, after a set >> > command to setup the file or disk (can't remember) you were interested >> > in... >> >> > Can anybody "reboot" my memory here? I remember it gave me more >> > details than a show dev/files... >> >> $ ANALYZE /SYSTEM >> SDA> SET PROCESS /INDEX=xx >> SDA> SHOW PROCESS /CHANNELS >> >> Could that have been it? > >I don't recall "SET PROCESS/INDEX", but yes, that is it! OK... SDA> SHOW PROCESS/INDEX=xx /CHANNELS >Thanks for the memory! > >(I thought I'd be interviewing for a VMS position last week, but alas! >No response...) Et tu? -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM "Well my son, life is like a beanstalk, isn't it?" http://tmesis.com/drat.html ------------------------------ Date: Sat, 12 Jan 2008 19:57:01 -0600 From: pechter@pechter.dyndns.org (William Pechter) Subject: Re: Anyone interested in building a vms-like OS? Message-ID: <4IOdnRlPrspw8hTanZ2dnUVZ_h-vnZ2d@comcast.com> In article , wrote: >In article , >pechter@pechter.dyndns.org (William Pechter) writes: >> >> >>In article , wrote: >>>In article <4783B4F2.3070807@comcast.net>, "Richard B. Gilbert" >>> writes: >>>>{...snip...} >>>> >>>>It's been done already. It was called PCVMS. It gave you a DCL shell >>>>and, IIRC, some VMS-like APIs. A toy, really. This was twelve or >>>>fifteen years ago. . . . >>> >>>Try 20! Wendin Associates in Wash. state. >> >>It was kind of slick. >>I had a copy in my Fort Monmouth days... I still have the docs but >>can't find the disks. >> >>> >>>The biggest issue, IMO, for PC-VMS at that time was the lack of a more >>>robust and sophisticated processor to run on. That was the era of the >>>80286 and, toward the end of the 80s, the 80386. I'd had a copy of it >>>back when I worked at Lakehurst NAEC. It was, like you've said, a toy >>>but fun to play with. CP/M ran on the box when there was something to >>>do beside see what would fail in PC-VMS DCL when you typed in a certain >>>command. >> >> >>Lakehurst, eh. I remember a figher jock tailgaiting me when I was down >>there fixing some PDP one afternoon. Shades of Top Gun. I thought I >>saw him laughing in the rear view mirror. >> >>In my Pre-DEC days I did newspapers for Leisure Village West and a >>couple of the other Leisure Village's. I always wanted to see the >>heavy lifting blimp-helocopter mix they were building there before the >>crash. >> >>You sound like a local... > >I'm pretty sure we've discussed this before. I spent a number of years >at Lakehurst at the ATE software center. Left there to go to GE Astro- >Space for a stint. Left there and spent five years in the Myers Center >(aka, the hexagon) at Ft. Monmouth. GE Astro... I remember the RCA Astro on 571 in Hightstown became GE Astro... when the GE takeover of RCA went down around '86. I left DEC Princeton shortly after that. Ah... I was the DEC Field Service guy there from 81-85... Did Lakehurst after the DEC stint with a short stop with TRW. Which area at the hex... Left Fort Monmouth around 85 to go to DEC Princeton for second shift work and came back to the Fort as a contractor. > >I did my undergraduate and graduate studies at Monmouth University (was >College at that time). I've lived in Long Branch, West LB, Asbury Park >and now I'm in Jackson. I finally got my self into Bell Labs just in tine to watch the bottom fall out. Did a bit of a stint (5 years) with a Telecom dot com and now I'm doing Unix Sysadmin at Seton Hall University. > >Drop me a line. We should get together for a meetup. > Too bad most of the DEC users in the area have disappeared. The area used to be a hotbed of interesting stuff from Industrial and Power Plant and Refinery Control (Autodynamics, Electronics Associates Inc, Ft. Monmouth, RCA Astro, RCA Semiconductor, Princeton University, Naval Air Propulsion - Trenton, Lakehurst, Naval Weapons Station Earle (an offshoot of Fort Monmouth located their PDP11/40 there for test work). The Wall/Neptune area known used by Marconi later known as Fort Monmouth's Evans Area was a slick spot (one of my old customers as well...) >-- >VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM Sounds like a good idea. Bill -- "When I think back on all the crap I learned in Vax school It's a wonder I fixed anything at all." (to the tune of Kodachrome) pechter-at-gmail.com ------------------------------ Date: Sun, 13 Jan 2008 02:58:52 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: Anyone interested in building a vms-like OS? Message-ID: In article <4IOdnRlPrspw8hTanZ2dnUVZ_h-vnZ2d@comcast.com>, pechter@pechter.dyndns.org (William Pechter) writes: > > >In article , wrote: >>In article , >>pechter@pechter.dyndns.org (William Pechter) writes: >>> >>> >>>In article , wrote: >>>>In article <4783B4F2.3070807@comcast.net>, "Richard B. Gilbert" >>>> writes: >>>>>{...snip...} >>>>> >>>>>It's been done already. It was called PCVMS. It gave you a DCL shell >>>>>and, IIRC, some VMS-like APIs. A toy, really. This was twelve or >>>>>fifteen years ago. . . . >>>> >>>>Try 20! Wendin Associates in Wash. state. >>> >>>It was kind of slick. >>>I had a copy in my Fort Monmouth days... I still have the docs but >>>can't find the disks. >>> >>>> >>>>The biggest issue, IMO, for PC-VMS at that time was the lack of a more >>>>robust and sophisticated processor to run on. That was the era of the >>>>80286 and, toward the end of the 80s, the 80386. I'd had a copy of it >>>>back when I worked at Lakehurst NAEC. It was, like you've said, a toy >>>>but fun to play with. CP/M ran on the box when there was something to >>>>do beside see what would fail in PC-VMS DCL when you typed in a certain >>>>command. >>> >>> >>>Lakehurst, eh. I remember a figher jock tailgaiting me when I was down >>>there fixing some PDP one afternoon. Shades of Top Gun. I thought I >>>saw him laughing in the rear view mirror. >>> >>>In my Pre-DEC days I did newspapers for Leisure Village West and a >>>couple of the other Leisure Village's. I always wanted to see the >>>heavy lifting blimp-helocopter mix they were building there before the >>>crash. >>> >>>You sound like a local... >> >>I'm pretty sure we've discussed this before. I spent a number of years >>at Lakehurst at the ATE software center. Left there to go to GE Astro- >>Space for a stint. Left there and spent five years in the Myers Center >>(aka, the hexagon) at Ft. Monmouth. > >GE Astro... I remember the RCA Astro on 571 in Hightstown became GE >Astro... when the GE takeover of RCA went down around '86. I left DEC >Princeton shortly after that. I was there right at the cross over... I wasn't one of them and I wasn't one of them. It was the management that drove me out. I ported flight software from RCA 1802 to MIL-STD1760A by building an coding an embedded control in their cluster of VAXes. >Ah... I was the DEC Field Service guy there from 81-85... >Did Lakehurst after the DEC stint with a short stop with TRW. The ATE software center had 2 11/780s and 2 11/785s when I left there. I used to love writing code for those boxes. I wrote my first device drivers there to control some Harris system drives which used to have Atlas TPSs on them. >Which area at the hex... Left Fort Monmouth around 85 to go to DEC >Princeton for second shift work and came back to the Fort as a >contractor. For the most part, the 4th floor was a tenant activity of DREN/ET&DL. I used be the big cheese with all the VMS boxes there. The cluster in the glass house to the myriad uVAX controlling the electron microscopes and the 10/100 clean room ASIC lines to the nano-lithographic etching and ion-epitaxy machine to the various 11s in the cryogenics labs. >>I did my undergraduate and graduate studies at Monmouth University (was >>College at that time). I've lived in Long Branch, West LB, Asbury Park >>and now I'm in Jackson. > >I finally got my self into Bell Labs just in tine to watch the bottom >fall out. Did a bit of a stint (5 years) with a Telecom dot com >and now I'm doing Unix Sysadmin at Seton Hall University. Most of my EE profs when I was working on my MSEE worked at Bell Labs. Did you ever run into a Dr. Cimini there? >>Drop me a line. We should get together for a meetup. >> > >Too bad most of the DEC users in the area have disappeared. >The area used to be a hotbed of interesting stuff from Industrial >and Power Plant and Refinery Control (Autodynamics, Electronics >Associates Inc, Ft. Monmouth, RCA Astro, RCA Semiconductor, Princeton >University, Naval Air Propulsion - Trenton, Lakehurst, Naval Weapons >Station Earle (an offshoot of Fort Monmouth located their PDP11/40 there >for test work). The Wall/Neptune area known used by Marconi later known >as Fort Monmouth's Evans Area was a slick spot (one of my old customers >as well...) I had an uncle who used to teach math at Lehigh Univ. When I was in my 5th or 6th grade I was solving systems of linear equations with the determinant and various other things he taugh me. I thought then I would probably go to Lehigh. In HS, I built my own computer from a popular electronics article. I learned to write the programs out, count bytes, etc., and then toggled in the code with switches. I was immediately taken with the computer. I also had a strong interest in electronic music and figured that one day the computer would fit in there too. I learned about Monmouth College because I had a relative working for EAI. During my undergrad, I worked in the school's physics lab and I had access to an EAI 8800 as well as several micros and a PDP. When I was working on my grad, I had to teach course in applied calculus. I went into the lab and hooked up the PDP, micros and the EAI 8800 to a large HP bed plotter and wrote programs and drivers to graph out the concepts of things I was trying to teach these undergrads. I would go into the classroom and (we had magnetic chalkboards) magnet a sheet of paper from the plotter with a graphic of a bessel function for example on the board and begin a lesson. The next semester (I had to only do it for one) the students BEGGED me to come back and teach the class. Anyway, that is how I became more interested in the operating system and device drivers. I spent time in the Evans Area too... some Joint STARS work was handled there. They had VMS boxes there for that too. Sheesh. We shared so much common ground, how is it we've never met up? -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM "Well my son, life is like a beanstalk, isn't it?" http://tmesis.com/drat.html ------------------------------ Date: Sat, 12 Jan 2008 11:47:32 -0800 (PST) From: H Vlems Subject: Re: Anyway to "smarten up" the console terminal? Message-ID: <42044139-6beb-4257-9c5b-91fbfeeb682b@v29g2000hsf.googlegroups.com> On 12 jan, 09:12, Slor wrote: > This may be a really silly question, but here goes anyway... > > I have OpenVMS 8.3 running on an old DEC 3000 with only 64MB of memory. > Following suggestions from this group based on this system's specs, I chose > not to install any of the windowing components, so my console is the basic > black text screen. A bit of web searching tells me that this console is > pretty much as dumb as it gets, so there's really no valid terminal type to > be used unless some helper like DECWindows is loaded and doing terminal > emulation in its windows. My question - is there any other way to get the > physical console to behave in a more full-featured manner for screen- > oriented text apps, command line editing support, etc.? > > Obviously, I can emulate any sort of console I want using SSH/telnet or > even a serial console connection, but I'm interested in whether or not > there is any solution for the local console. > > thanks! > > -- > Jameshttp://www.e-host-direct.com > Reliable web hosting from $12/year. If you insist on having a pc-style monitor connected to the AXP then you're stuck with VT52 capabilities. Which aren't great. The alternative is to connect a VT100 (or any other VT model) to a/ the serial port of the AXP. Next: >>> set console serial and power off the machine for about a minute or so before switching it on again. Of course you can also connect a pc/laptop to the serial port and run a decent terminal emulator on the pc. Cabling may be a problem. Some systems (e.g. AS800 and possibly the AXP 3000's) just have an MMJ connector and MMJ cables are not that common any more. Others, like the AS1200, have DB9 connectors. USB-to- serial connectors are fairly common I guess. Hans ------------------------------ Date: Sat, 12 Jan 2008 19:31:45 GMT From: "John E. Malmberg" Subject: Re: IA64 VMS installation DVD creation. Message-ID: Steven M. Schweda wrote: > Let's imagine that I have a file named I64083.BCK-GZ, which can be > expanded into an image BACKUP save set of what looks like a real IA64 > VMS installation DVD. Let us further imagine that I'm doing all this > work on an Alpha system. Your save set may be missing the boot blocks of the real IA64 VMS installation DVD. The real IA64 VMS installation DVD is a dual format EL-Torito bootable CD-ROM. The IA64 boot blocks are in the ISO-9960 section. These sectors were located in the badblocks.sys file on the boot volume, unless something has been changed. While it was convenient to use the badblocks.sys file to keep VMS from using them, it is possible that a different method of tracking them might be used in the future. Backup/physical is needed to copy a IA64 bootable DVD. Backup/image skips the boot sectors of the dual format DVD. Those sectors are not installed on a magnetic disk. > If I were to create an LD container of an appropriate size, and > restore (BACKUP /IMAGE) this save set onto the corresponding LD device, > should I be able to use the resulting LD container to make a working > installation DVD, or would the LD device first need to be fiddled using > some exotic SET BOOTBLOCK command (which is, of course, "Valid on I64 > systems only.")? While the EFI console only officially supports booting Optical Media in the El-torito format, it has been known to boot other formats. The block size is different than on a magnetic disk, so the if you are setting the boot block on a Logical disk image that you intend to burn on a CD, you have to take that into account. > Or (and especially if the answer to that last one was "yes"), does > anyone have an actual IA64 DVD image lying about where I could stumble > across it? (If IA64 fiddling is needed, I suppose that I could push > everything up to an IA64 TestDrive system, fiddle as needed, and then > pull the fiddled result back, but this seems less efficient than it > might be. And what would the proper SET BOOTBLOCK command be?) You need to find out the exact ritual for generating a DVD from the saveset that you have. > Naturally, a VMS V8.3-1 kit would be preferred over the plain-old > V8.3 kit which I have, so if anyone knows the secret file name for such > a kit on the secret FTP server (or has a DVD image of that one), so much > the better. > > It's not actually urgent, but there is a ZX2000 here just crying out > for a good reason to run. You are best off getting a image copy of the DVD, or to do a network install. Sorry, that I can not be more precise at this time, but I have not worked with creating boot DVDs for IA64 for a couple of years. -John wb8tyw@qsl.network Personal Opinion Only ------------------------------ Date: Sat, 12 Jan 2008 23:38:13 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: IA64 VMS installation DVD creation. Message-ID: In article , "John E. Malmberg" writes: > > >Steven M. Schweda wrote: >> Let's imagine that I have a file named I64083.BCK-GZ, which can be >> expanded into an image BACKUP save set of what looks like a real IA64 >> VMS installation DVD. Let us further imagine that I'm doing all this >> work on an Alpha system. > >Your save set may be missing the boot blocks of the real IA64 VMS >installation DVD. > >The real IA64 VMS installation DVD is a dual format EL-Torito bootable >CD-ROM. The IA64 boot blocks are in the ISO-9960 section. > >These sectors were located in the badblocks.sys file on the boot volume, >unless something has been changed. While it was convenient to use the >badblocks.sys file to keep VMS from using them, it is possible that a >different method of tracking them might be used in the future. > >Backup/physical is needed to copy a IA64 bootable DVD. > >Backup/image skips the boot sectors of the dual format DVD. > >Those sectors are not installed on a magnetic disk. > >> If I were to create an LD container of an appropriate size, and >> restore (BACKUP /IMAGE) this save set onto the corresponding LD device, >> should I be able to use the resulting LD container to make a working >> installation DVD, or would the LD device first need to be fiddled using >> some exotic SET BOOTBLOCK command (which is, of course, "Valid on I64 >> systems only.")? > >While the EFI console only officially supports booting Optical Media in >the El-torito format, it has been known to boot other formats. > >The block size is different than on a magnetic disk, so the if you are >setting the boot block on a Logical disk image that you intend to burn >on a CD, you have to take that into account. > >> Or (and especially if the answer to that last one was "yes"), does >> anyone have an actual IA64 DVD image lying about where I could stumble >> across it? (If IA64 fiddling is needed, I suppose that I could push >> everything up to an IA64 TestDrive system, fiddle as needed, and then >> pull the fiddled result back, but this seems less efficient than it >> might be. And what would the proper SET BOOTBLOCK command be?) > >You need to find out the exact ritual for generating a DVD from the >saveset that you have. > >> Naturally, a VMS V8.3-1 kit would be preferred over the plain-old >> V8.3 kit which I have, so if anyone knows the secret file name for such >> a kit on the secret FTP server (or has a DVD image of that one), so much >> the better. >> >> It's not actually urgent, but there is a ZX2000 here just crying out >> for a good reason to run. > >You are best off getting a image copy of the DVD, or to do a network >install. > >Sorry, that I can not be more precise at this time, but I have not >worked with creating boot DVDs for IA64 for a couple of years. OK. I've gotten actual IA64 DVD media but wouldn't it behoove HP to have a DVD image that could be downloaded and burned? I'd be happy if I could download the V8.3+n versions of OpenVMS IA64 if I could use Toast to burn the DVD. A copy of the disk artwork on-line too so I could print a label for the DVD and then place in my archives. It seem to me this would save on DVD production and shipment for HP. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM "Well my son, life is like a beanstalk, isn't it?" http://tmesis.com/drat.html ------------------------------ Date: Sat, 12 Jan 2008 19:19:44 -0500 From: "Richard B. Gilbert" Subject: Re: IA64 VMS installation DVD creation. Message-ID: <47895920.1060809@comcast.net> VAXman- wrote: > In article , "John E. Malmberg" writes: > >> >>Steven M. Schweda wrote: >> >>> Let's imagine that I have a file named I64083.BCK-GZ, which can be >>>expanded into an image BACKUP save set of what looks like a real IA64 >>>VMS installation DVD. Let us further imagine that I'm doing all this >>>work on an Alpha system. >> >>Your save set may be missing the boot blocks of the real IA64 VMS >>installation DVD. >> >>The real IA64 VMS installation DVD is a dual format EL-Torito bootable >>CD-ROM. The IA64 boot blocks are in the ISO-9960 section. >> >>These sectors were located in the badblocks.sys file on the boot volume, >>unless something has been changed. While it was convenient to use the >>badblocks.sys file to keep VMS from using them, it is possible that a >>different method of tracking them might be used in the future. >> >>Backup/physical is needed to copy a IA64 bootable DVD. >> >>Backup/image skips the boot sectors of the dual format DVD. >> >>Those sectors are not installed on a magnetic disk. >> >> >>> If I were to create an LD container of an appropriate size, and >>>restore (BACKUP /IMAGE) this save set onto the corresponding LD device, >>>should I be able to use the resulting LD container to make a working >>>installation DVD, or would the LD device first need to be fiddled using >>>some exotic SET BOOTBLOCK command (which is, of course, "Valid on I64 >>>systems only.")? >> >>While the EFI console only officially supports booting Optical Media in >>the El-torito format, it has been known to boot other formats. >> >>The block size is different than on a magnetic disk, so the if you are >>setting the boot block on a Logical disk image that you intend to burn >>on a CD, you have to take that into account. >> >> >>> Or (and especially if the answer to that last one was "yes"), does >>>anyone have an actual IA64 DVD image lying about where I could stumble >>>across it? (If IA64 fiddling is needed, I suppose that I could push >>>everything up to an IA64 TestDrive system, fiddle as needed, and then >>>pull the fiddled result back, but this seems less efficient than it >>>might be. And what would the proper SET BOOTBLOCK command be?) >> >>You need to find out the exact ritual for generating a DVD from the >>saveset that you have. >> >> >>> Naturally, a VMS V8.3-1 kit would be preferred over the plain-old >>>V8.3 kit which I have, so if anyone knows the secret file name for such >>>a kit on the secret FTP server (or has a DVD image of that one), so much >>>the better. >>> >>> It's not actually urgent, but there is a ZX2000 here just crying out >>>for a good reason to run. >> >>You are best off getting a image copy of the DVD, or to do a network >>install. >> >>Sorry, that I can not be more precise at this time, but I have not >>worked with creating boot DVDs for IA64 for a couple of years. > > > OK. I've gotten actual IA64 DVD media but wouldn't it behoove HP to have > a DVD image that could be downloaded and burned? I'd be happy if I could > download the V8.3+n versions of OpenVMS IA64 if I could use Toast to burn > the DVD. A copy of the disk artwork on-line too so I could print a label > for the DVD and then place in my archives. It seem to me this would save > on DVD production and shipment for HP. > Well, Sun does that with Solaris but we all know that HP (at least the division responsible for VMS) isn't anywhere near as smart as Sun! ------------------------------ Date: 12 Jan 2008 18:21:30 -0600 From: Kilgallen@SpamCop.net (Larry Kilgallen) Subject: Re: IA64 VMS installation DVD creation. Message-ID: In article , VAXman- @SendSpamHere.ORG writes: > OK. I've gotten actual IA64 DVD media but wouldn't it behoove HP to have > a DVD image that could be downloaded and burned? I'd be happy if I could > download the V8.3+n versions of OpenVMS IA64 if I could use Toast to burn > the DVD. A copy of the disk artwork on-line too so I could print a label > for the DVD and then place in my archives. It seem to me this would save > on DVD production and shipment for HP. That has never been the VMS business practice for VAX or AXP. Why would IPF be different ? ------------------------------ Date: Sun, 13 Jan 2008 00:33:32 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: IA64 VMS installation DVD creation. Message-ID: In article , Kilgallen@SpamCop.net (Larry Kilgallen) writes: > > >In article , VAXman- @SendSpamHere.ORG writes: > >> OK. I've gotten actual IA64 DVD media but wouldn't it behoove HP to have >> a DVD image that could be downloaded and burned? I'd be happy if I could >> download the V8.3+n versions of OpenVMS IA64 if I could use Toast to burn >> the DVD. A copy of the disk artwork on-line too so I could print a label >> for the DVD and then place in my archives. It seem to me this would save >> on DVD production and shipment for HP. > >That has never been the VMS business practice for VAX or AXP. >Why would IPF be different ? Well, since the advent of DSPP, it's how I've been getting certain kits. They are now downloaded from the HP web site. VAX pretty much predates the internet so I would have expected the model to include such downloads. However, since the introduction of the Alpha, patch kits and various other layer products have been downloadable. LMF, if it were sufficient, should protect against misuse of these downloaded products. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM "Well my son, life is like a beanstalk, isn't it?" http://tmesis.com/drat.html ------------------------------ Date: Sat, 12 Jan 2008 15:59:22 -0600 From: jackson@Encompasserve.org Subject: Re: Mystery of X-windows colours/resources Message-ID: In article On 10 Jan 2008, Bob Koehler wrote: > In article <478300a1$0$15738$c3e8da3@news.astraweb.com>, JF Mezei writes: > > > > When a VMS application starts and has its output targetted at a remote X > > terminal, does the X protocol end up having that VMS application > > accessing resource files that are on the remote X terminal (other than > > window manager stuff) ? > > The X provides the fonts, although often via a fontserver. It also > maps color numbers to actual video driver commands. > > But I can reproduce some of what you see by running two sessions on > the same VXT from the same Alpha. X11 is not 100% deterministic. > OP should recall (a) that resources are defined hierarchically with more specific ones overriding inherited generalisations; and (b) that not all resources are persistent. A client sees resources built-in (possibly blue is), resources in 'standard' locations and resources in resource paths defined by or overridden in the client's invocation environment. The client also sees 'transient' resources in the window manager property of the server. 'Transient' in the sense that any client can destroy remove alter change vary those properties. An example is wsinit. At one time various nix distros' stock session startups trashed resources indiscriminantly and over- rode or added fontpath elements local to the client machine. I can echo what Bob said about reproducing what the OP sees using a similar setup. If running clients from multiple hosts, consistency is more easily achieved by maintaining (and if necessary, reinstating) server-side resources. ------------------------------ Date: Sat, 12 Jan 2008 15:30:16 -0500 From: bradhamilton Subject: OT - EISNER:: upgrade complete (was:Re: default e-mail editor) Message-ID: <47892358.8010401@comcast.net> VAXman- @SendSpamHere.ORG wrote: > You will need to figure out how to pass P1 and P2 to vim. I was going to > check this on EISNER for you but it's down (I believe it's being upgraded > to V8.3). EISNER:: is now available post-upgrade. ------------------------------ Date: Sun, 13 Jan 2008 01:27:43 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: OT - EISNER:: upgrade complete (was:Re: default e-mail editor) Message-ID: In article <47892358.8010401@comcast.net>, bradhamilton writes: > > >VAXman- @SendSpamHere.ORG wrote: >> You will need to figure out how to pass P1 and P2 to vim. I was going to >> check this on EISNER for you but it's down (I believe it's being upgraded >> to V8.3). > >EISNER:: is now available post-upgrade. Thanks Brad! :D Lookin' good! The new version of SYMBOL for V8.3 has now been installed there too. I hope the original poster of this thread can figure out how to invoke VIM from the command procedure I posted. I'm not sure how to tell VIM to write out to the P2 filename. It's a no brainer to have it read the P1 filename. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM "Well my son, life is like a beanstalk, isn't it?" http://tmesis.com/drat.html ------------------------------ Date: Sat, 12 Jan 2008 11:53:52 -0800 (PST) From: H Vlems Subject: print queues and IP Message-ID: Yesterday I bought an Alpha Server 1200 5/400 (a blue one, not a white box alpha). Since it is too heavy to put it in the same room as the others as yet, it sits noisily in the living room. The only available printer there is an old HP2100 with an IP printserver. I want to create a printerqueue that allows me to print to that HP2100, its IP address is 10.0.0.102. IIRC the TCPIP$TELNETSYM processor is needed, but where do I put the IP address? Hans ------------------------------ Date: Sat, 12 Jan 2008 22:39:40 GMT From: =?ISO-8859-1?Q?Jan-Erik_S=F6derholm?= Subject: Re: print queues and IP Message-ID: H Vlems wrote: > Yesterday I bought an Alpha Server 1200 5/400 (a blue one, not a white > box alpha). Since it is too heavy to put it in the same room as the > others as yet, it sits noisily in the living room. The only available > printer there is an old HP2100 with an IP printserver. > I want to create a printerqueue that allows me to print to that > HP2100, its IP address is 10.0.0.102. > IIRC the TCPIP$TELNETSYM processor is needed, but where do I put the > IP address? > Hans > From "TCPIP Services, Management", chap 23, "Setting Up and Managing TELNETSYM" : > For example, to set up a TELNETSYM queue named xyz_q to > print using TELNETSYM to host printserver.xyz.com at > TCP port 4242, enter: > $ INITIALIZE /QUEUE /PROCESSOR=TCPIP$TELNETSYM - > _$ /ON="printserver.xyz.com:4242" xyz_q "printserver.xyz.com" could of course be a plain IP address... But check the docs! Jan-Erik. ------------------------------ Date: Sat, 12 Jan 2008 20:38:07 -0600 From: David J Dachtera Subject: Request: LD Enhancement to allow "volume groups" Message-ID: <4789798F.3312FF46@spam.comcast.net> There's probably a better place to post this, but until I find it, this will do. The request is for an enhancement to LD to allow a block-range LD to span multiple physical devices, ala the following example: $ ld connect - dka100:/lbn=(start=0,count=3145728), - dka200:/lbn=(start=0,count=3145728), - lda1/allo=1 $ ld connect - dka100:/lbn=(start=3145728,count=3145728), - dka200:/lbn=(start=3145728,count=3145728), - lda2 The idea is to prototype a facility similar to the Logical Volume Manager in AIX. In the example above, DKA100 and DKA200 become a "volume group" and LDA1 and LDA2 are "logical volumes" within that group. Ideally, of course, this would need to morph into something more substantive. I could envision these extensions (thinking "out loud" here, so this is off-the-cuff, and anywhere from totally raw to little better than half-baked): LD CREATE /GROUP group-name /VOLUMES=(ddcu:,ddcu:[,ddcu:[,...]]) The command would reserve the first 512 blocks on each device for a VGCB (Volume Group Control Block) to contain the metadata describing the volume group and its contents. A Volume Group Database (VGDB) on the system disk would be created/updated to include the volume group name, the physical devices comprising it and the logical volumes within the volume group. LD MODIFY /GROUP group-name /VOLUMES=(ddcu:,ddcu:[,ddcu:[,...]]) The command would add volumes to an existing volume group. LD MODIFY /GROUP group-name /NOVOLUMES=(ddcu:,ddcu:[,ddcu:[,...]]) The command would remove the specified volumes from the volume group. LD DELETE /GROUP group-name[,group-name[,...]] The command would delete volume groups from the local VGDB while leaving the VGCBs on the physical devices intact. LD IMPORT /GROUP[ group-name] /VOLUMES=(ddcu:,ddcu:[,ddcu:[,...]]) The command would update the local VGDB using the VGCB data on the first (or any) device specified. All devices comprising the volume group would have to exist on the local machine. [Potential issue with duplicate device and/or logical volume names! May need to prompt the SysAdmin for help during the import.] LD CREATE /LOGICAL_VOLUME logical-volume-name /VOLUMES=((PVNn=(START=lbn,{SIZE=count|END=lbn)- [,PVNn=(START=lbn,{SIZE=count|END=lbn)) The command would populate the VGDB and the VGCBs on each PV to contain the metadata describing the named logical volume and its location(s) within the volume group. "PVN" is the Physical Volume Number within the group, or could be the actual Physical Device name. LD CONNECT/LOGICAL_VOLUME logical-volume-name LDAu: Creates the LD virtual device DCB and associates it with the block ranges on the physical devices which comprise the underlying volume group. The LD devices are then MOUNTed and processed like any other disk device. This begins to mimic what I'm seeing as the underlying disk storage strategy in AIX. It's almost like having an HSV built into the o.s.: You can stripe logical volumes across the physical volumes in the volume group, you can mirror and unmirror logical volumes, you can "migrate" logical volumes within the volume group between physical devices (for example, if a disk is going bad but is still at least marginally functional), ... It quite fascinating, really. Then again, it may just be another of those, "Gee ... if only VMS could do that!" things. David J Dachtera DJE Systems ------------------------------ Date: Sun, 13 Jan 2008 07:42:09 +0100 From: Jur van der Burg <"lddriver at digiater dot nl"> Subject: Re: Request: LD Enhancement to allow "volume groups" Message-ID: <4789b2c1$0$85794$e4fe514c@news.xs4all.nl> David, Thats a very interesting idea. I'm currently running linux on my main pc and have been playing with volume groups and containers as well and it's indeed a very flexible mechanism. I would love to implement something like this and will certainly look if it's feasable in the limited time that I currently have, especially because I develop LD in my spare time and also have a very busy job earning real money. A big bag of money may help considerably of course :-). Jur van der Burg lddriver at digiater.nl David J Dachtera wrote: > There's probably a better place to post this, but until I find it, this > will do. > > The request is for an enhancement to LD to allow a block-range LD to > span multiple physical devices, ala the following example: > > $ ld connect - > dka100:/lbn=(start=0,count=3145728), - > dka200:/lbn=(start=0,count=3145728), - > lda1/allo=1 > $ ld connect - > dka100:/lbn=(start=3145728,count=3145728), - > dka200:/lbn=(start=3145728,count=3145728), - > lda2 > > The idea is to prototype a facility similar to the Logical Volume > Manager in AIX. > > In the example above, DKA100 and DKA200 become a "volume group" and LDA1 > and LDA2 are "logical volumes" within that group. > > Ideally, of course, this would need to morph into something more > substantive. I could envision these extensions (thinking "out loud" > here, so this is off-the-cuff, and anywhere from totally raw to little > better than half-baked): > > LD > CREATE > /GROUP group-name > /VOLUMES=(ddcu:,ddcu:[,ddcu:[,...]]) > > The command would reserve the first 512 blocks on each device for a VGCB > (Volume Group Control Block) to contain the metadata describing the > volume group and its contents. A Volume Group Database (VGDB) on the > system disk would be created/updated to include the volume group name, > the physical devices comprising it and the logical volumes within the > volume group. > > > LD > MODIFY > /GROUP group-name > /VOLUMES=(ddcu:,ddcu:[,ddcu:[,...]]) > > The command would add volumes to an existing volume group. > > > LD > MODIFY > /GROUP group-name > /NOVOLUMES=(ddcu:,ddcu:[,ddcu:[,...]]) > > The command would remove the specified volumes from the volume group. > > > LD > DELETE > /GROUP group-name[,group-name[,...]] > > The command would delete volume groups from the local VGDB while leaving > the VGCBs on the physical devices intact. > > > LD > IMPORT > /GROUP[ group-name] > /VOLUMES=(ddcu:,ddcu:[,ddcu:[,...]]) > > The command would update the local VGDB using the VGCB data on the first > (or any) device specified. All devices comprising the volume group would > have to exist on the local machine. [Potential issue with duplicate > device and/or logical volume names! May need to prompt the SysAdmin for > help during the import.] > > > LD > CREATE > /LOGICAL_VOLUME logical-volume-name > /VOLUMES=((PVNn=(START=lbn,{SIZE=count|END=lbn)- > [,PVNn=(START=lbn,{SIZE=count|END=lbn)) > > The command would populate the VGDB and the VGCBs on each PV to contain > the metadata describing the named logical volume and its location(s) > within the volume group. "PVN" is the Physical Volume Number within the > group, or could be the actual Physical Device name. > > LD > CONNECT/LOGICAL_VOLUME logical-volume-name LDAu: > > Creates the LD virtual device DCB and associates it with the block > ranges on the physical devices which comprise the underlying volume > group. > > The LD devices are then MOUNTed and processed like any other disk > device. > > This begins to mimic what I'm seeing as the underlying disk storage > strategy in AIX. It's almost like having an HSV built into the o.s.: You > can stripe logical volumes across the physical volumes in the volume > group, you can mirror and unmirror logical volumes, you can "migrate" > logical volumes within the volume group between physical devices (for > example, if a disk is going bad but is still at least marginally > functional), ... It quite fascinating, really. > > Then again, it may just be another of those, "Gee ... if only VMS could > do that!" things. > > David J Dachtera > DJE Systems ------------------------------ Date: Sat, 12 Jan 2008 23:21:17 -0600 From: Slor Subject: run /detached always fails with loginout.exe Message-ID: Perhaps someone can give me a quick answer to this... In an effort to follow some instructions I found for shutting down VMS from a remote session, I am trying this command from my system account: run /detached /input=sys$system:shutdown.com sys$system:loginout.exe I've also tried more scoped examples such as these: run /detached sys$system:loginout.exe run /detached /input=donothing.com sys$system:loginout.exe No matter what I've tried, I always get the following trying to run loginout.exe as a detached process: Security alarm (SECURITY) and security audit (SECURITY) on DEC, system id: 65534 Auditable event: Detached process login failure Event time: 12-JAN-2008 21:28:00.20 PID: 000000BC Username: SYSTEM Process owner: [SYSTEM] Image name: DEC$DKA0:[SYS0.SYSCOMMON.][SYSEXE] LOGINOUT.EXE Posix UID: -2 Posix GID: -2 (%XFFFFFFFE) Status: %SYSTEM-F-NOLOGNAM, no logical name match This is OpenVMS 8.3 on an DEC 3000. Is there something I've neglected to do in order to make this viable? I was able to run a couple other .exe files without seeing the error, and from what I can tell this is the standard method for running any DCL-needing commands from a detached process. Thanks! -- James http://www.e-host-direct.com Reliable web hosting from $12/year. ------------------------------ Date: Sun, 13 Jan 2008 16:43:37 +1100 From: Jim Duff Subject: Re: run /detached always fails with loginout.exe Message-ID: <4789a50b@dnews.tpgi.com.au> Slor wrote: > Perhaps someone can give me a quick answer to this... In an effort to > follow some instructions I found for shutting down VMS from a remote > session, I am trying this command from my system account: > > run /detached /input=sys$system:shutdown.com sys$system:loginout.exe > > I've also tried more scoped examples such as these: > > run /detached sys$system:loginout.exe > run /detached /input=donothing.com sys$system:loginout.exe > > No matter what I've tried, I always get the following trying to run > loginout.exe as a detached process: > > Security alarm (SECURITY) and security audit (SECURITY) on DEC, system > id: 65534 > Auditable event: Detached process login failure > Event time: 12-JAN-2008 21:28:00.20 > PID: 000000BC > Username: SYSTEM > Process owner: [SYSTEM] > Image name: DEC$DKA0:[SYS0.SYSCOMMON.][SYSEXE] > LOGINOUT.EXE > Posix UID: -2 > Posix GID: -2 (%XFFFFFFFE) > Status: %SYSTEM-F-NOLOGNAM, no logical name match > > This is OpenVMS 8.3 on an DEC 3000. Is there something I've neglected > to do in order to make this viable? I was able to run a couple other > .exe files without seeing the error, and from what I can tell this is > the standard method for running any DCL-needing commands from a detached > process. > > Thanks! > Quick answer: add /OUTPUT=NL: to your command. Jim. -- www.eight-cubed.com ------------------------------ Date: Sun, 13 Jan 2008 00:54:11 -0500 From: JF Mezei Subject: Re: run /detached always fails with loginout.exe Message-ID: <4789a83a$0$16160$c3e8da3@news.astraweb.com> Slor wrote: > Perhaps someone can give me a quick answer to this... In an effort to > follow some instructions I found for shutting down VMS from a remote > session, I am trying this command from my system account: > > run /detached /input=sys$system:shutdown.com sys$system:loginout.exe Shutdown.com will be prompting for input. Where will that come from ? You would probably have to create a different command procedure to invoke shutdown.com with all the require parameters so that it can execute without any prompts, and then use that procedure as the /input. ------------------------------ Date: Sat, 12 Jan 2008 11:59:45 -0800 (PST) From: H Vlems Subject: Re: USB-stick Message-ID: <79e458bf-cd97-4323-ba53-ae27b5d7f4fc@c23g2000hsa.googlegroups.com> On 9 jan, 21:16, bri...@encompasserve.org wrote: > In article <4785169A.3050...@comcast.net>, "Richard B. Gilbert" writes: > > > > > Christoph Gartmann wrote: > >> Hello, > > >> is it possible to mount a FAT formatted 1 GB USB-stick under OpenVMS 8.3? > >> The device is recognized as DNA1: but I can't figure out how to mount it :-( > > >> Regards, > >> Christoph Gartmann > > > How about MOUNT /FOR > > > I don't think VMS supports FAT file systems. I don't think you are > > going to be able to do much with it. You might be able to format it > > and put an ODS-2 file system on it. Or, you might not. I doubt if > > supporting "USB Sticks" is high on the priority list at VMS Engineering. > > Try $ MCR PCDISK > > I don't know whether that came with MicroVaxen or with Pathworks or > both. But it knew about FAT file systems. And last I knew it could > deal with container file systems, so it wasn't just FAT on floppy > disk drives. > > No clue where to lay my hands on a copy, unfortunately. It was (is?) part of PCSA. I run it on AXP/VMS 7.3-2 and 8.3. You need three files to run it, PCDISK.EXE (in SYS$SYSTEM), a library in SYS$SHARE and a helplibrary file. That's all. If you want it, send me a mail at hvlems-at-zonnet-nl. Don't use the freenet.de address, it's just a spammagnet... Hans ------------------------------ Date: Sat, 12 Jan 2008 23:44:43 +0100 From: Evert van Dijken Subject: Re: USB-stick Message-ID: Christoph Gartmann schreef: > Hello, > > is it possible to mount a FAT formatted 1 GB USB-stick under OpenVMS 8.3? > The device is recognized as DNA1: but I can't figure out how to mount it :-( > > Regards, > Christoph Gartmann > I use a program called TotalCommander on my PC (http://www.ghisler.com/) to get data from an USB-stick on my PC and VMS and vice-versa. TotalCommander has two windows showing a directory structure with content. When you insert the USB-stick in your PC and open one window with the directory of the USB-stick and on the other window an FTP session with your VMS acount, you can copy files either in text or binary mode from and to VMS. It is even possible to make a zip file on VMS (itanium, alpha you need shareware i believe) and read it on your PC. Evert. ------------------------------ End of INFO-VAX 2008.025 ************************