INFO-VAX Sat, 19 Jul 2008 Volume 2008 : Issue 400 Contents: Re: "Network tape drive" for VMS Re: "Network tape drive" for VMS Re: Any known BASIC/SMG issues on Itanium? Re: Any known BASIC/SMG issues on Itanium? HPFMS025 Re: HPFMS025 Re: HPFMS025 Re: HPFMS025 Re: HPFMS025 Non-CDE DECwindows on Itanium? Re: Non-CDE DECwindows on Itanium? Re: Non-CDE DECwindows on Itanium? Re: Question about quoting inside a string ---------------------------------------------------------------------- Date: Fri, 18 Jul 2008 18:28:48 -0500 From: Michael Austin Subject: Re: "Network tape drive" for VMS Message-ID: Albrecht Schlosser wrote: > Is there anything available that could be called a > "network tape drive" that is supported with > > (a) OpenVMS / Alpha 7.3-2 > (b) OpenVMS / I64, 8.2 or 8.3 ff. ? > > The reason is to have the backup tape drive separated from the > server for easier access to change the backup tapes. > > Please don't ask, why would you want to do that. It's simply > because of a user's request. And this should *not* be another > VMS server (cluster node) with a tape drive ;-) > > Albrecht Does it absolutely have to be TAPE? I have a solution - might not be what they want, but it will work. Purchase 2 devices - a Netgear NAS 1100 (or smaller/similar). This device could live in the office where access was necessary. You would simply NFS mount your VMS box to this device, copy your data to this device and from there, back it up, move it or whatever... This device comes with a USB port where you can plug in one of the USB backup disks and has a one-button copy operation of pre-defined user-level backups. The USB device can even be a thumb-drive if requirements are small enough... ------------------------------ Date: Fri, 18 Jul 2008 21:26:23 -0400 From: Stephen Hoffman Subject: Re: "Network tape drive" for VMS Message-ID: I'm surprised no one has suggested a tape library or a loader, and/or a big rack of cheap/slow/capacious archival disks. Such a library solves several different problems that can arise here. The other question revolves around what the end users will be restoring, and how often, and at what cost the convenience might come. There are various alternative archival solutions that may well be applicable here, depending on the particular local requirements. Centralized backup can be feasible, though there are often distributed alternative around, as well. (And in most any approach, there are various considerations...) Tapes, too, are somewhat problematic. Disks can be a better near-line storage resource and for use in tiered archival processing; the boxes I manage are using 750 gigabyte and terabyte disk spindles, and the 1.5 TB drives have been announced and are coming on-line. (Tapes are having trouble keeping up with disk capacities here.) The client backup tool target for one workgroup is a terabyte spindle that deals with all of the processing over wired or wireless, for instance. No operator input, secured storage, but the end-users can restore their files. -- www.HoffmanLabs.com Services for OpenVMS ------------------------------ Date: Fri, 18 Jul 2008 13:57:41 -0400 From: John Sauter Subject: Re: Any known BASIC/SMG issues on Itanium? Message-ID: Rich Jordan wrote: > > BASIC V1.7 worked, after we recompiled the library modules as well as > the program source. I'm getting an informational link message now > > %ILINK-I-DIFTYPE, symbol VT.PRINT_SCREEN_PRT of type FUNC cannot be > referenced as type OBJECT > module VT.PRINT_SCREEN > file: DKA0:[TEST]VT.PRINT_SCREEN.OBJ;3 > > VT.PRINT_SCREEN_PRT is the user action subroutine passed to SMG > $PUT_PASTEBOARD, and VT.PRINT_SCREEN is the actual subroutine called > by the test program. > > I'm sure its something simple, but obviously the itanium is being more > picky about it than the VAX or Alpha were (though I haven't installed > V1.7 on the test VMS 8.3 Alpha yet so we'll see). > > Thanks for the suggestions. > > Rich I find this error message both astonishing and pleasing. As a software research project I proposed that the compilers be augmented to describe how entry points expected to be called. The linker would take this information from all the callers and from the subroutine definition, and output a warning message if there was a mismatch. I called it link-time argument checking. My proposal was rejected by the VMS group, using language similar to "over my dead body". The messages you are seeing tells me that wiser heads eventually prevailed, at least in a limited case, and part of what I proposed was implemented. I did a google search for diftype vms, and found this: Here is an excerpt: On OpenVMS I64 systems, if a module defines a variable as data (OBJECT), it must be referenced as data by all other modules. If a module defines a variable as a procedure (FUNC), it must be referenced as a procedure by all other modules. When a procedure is referenced as data, the following informational message is displayed: %ILINK-I-DIFTYPE, symbol symbol-name of type FUNC cannot be referenced as type OBJECT Type checking is performed by the linker on OpenVMS I64 because the linker must create function descriptors. The equivalent procedure descriptor was created by the compiler on OpenVMS Alpha, so this informational message is new for the linker on OpenVMS I64. John Sauter (John_Sauter@systemeyescomputerstore.com) ------------------------------ Date: Sat, 19 Jul 2008 02:20:27 GMT From: John Santos Subject: Re: Any known BASIC/SMG issues on Itanium? Message-ID: John Sauter wrote: > Rich Jordan wrote: > >> >> BASIC V1.7 worked, after we recompiled the library modules as well as >> the program source. I'm getting an informational link message now >> >> %ILINK-I-DIFTYPE, symbol VT.PRINT_SCREEN_PRT of type FUNC cannot be >> referenced as type OBJECT >> module VT.PRINT_SCREEN >> file: DKA0:[TEST]VT.PRINT_SCREEN.OBJ;3 >> >> VT.PRINT_SCREEN_PRT is the user action subroutine passed to SMG >> $PUT_PASTEBOARD, and VT.PRINT_SCREEN is the actual subroutine called >> by the test program. >> >> I'm sure its something simple, but obviously the itanium is being more >> picky about it than the VAX or Alpha were (though I haven't installed >> V1.7 on the test VMS 8.3 Alpha yet so we'll see). >> >> Thanks for the suggestions. >> >> Rich > > > I find this error message both astonishing and pleasing. As a software > research project I proposed that the compilers be augmented to describe > how entry points expected to be called. The linker would take this > information from all the callers and from the subroutine definition, and > output a warning message if there was a mismatch. I called it link-time > argument checking. > > My proposal was rejected by the VMS group, using language similar to > "over my dead body". The messages you are seeing tells me that wiser > heads eventually prevailed, at least in a limited case, and part of > what I proposed was implemented. > > I did a google search for diftype vms, and found this: > > > > Here is an excerpt: > > On OpenVMS I64 systems, if a module defines a variable as data (OBJECT), > it must be referenced as data by all other modules. If a module defines > a variable as a procedure (FUNC), it must be referenced as a procedure > by all other modules. > > When a procedure is referenced as data, the following informational > message is displayed: > > %ILINK-I-DIFTYPE, symbol symbol-name of type FUNC cannot be > referenced as type OBJECT > > Type checking is performed by the linker on OpenVMS I64 because the > linker must create function descriptors. The equivalent procedure > descriptor was created by the compiler on OpenVMS Alpha, so this > informational message is new for the linker on OpenVMS I64. > John Sauter (John_Sauter@systemeyescomputerstore.com) We got a zillion of these messages as well. The correct thing to do seems to be to ignore them (after checking to make sure the complaint is in fact about passing a function as data in a context where that is really what you intend to do...) The resulting programs always seem to work okay :-) The real cure would be for BASIC to implement a FUNC datatype and to change SDL to generate function prototypes using it when appropriate when creating BASIC$STARLET.TLB and friends (and for customers to do the same when writing their own code.) -- John Santos Evans Griffiths & Hart, Inc. 781-861-0670 ext 539 ------------------------------ Date: Fri, 18 Jul 2008 16:55:43 -0700 (PDT) From: Banjara.Hills@gmail.com Subject: HPFMS025 Message-ID: <206c3e85-5d6e-4c34-a691-ab47d89872c4@z72g2000hsb.googlegroups.com> Where can I download the subject kit for an Alpha, both Dev and RT? ------------------------------ Date: Fri, 18 Jul 2008 20:12:52 -0500 From: David J Dachtera Subject: Re: HPFMS025 Message-ID: <48813F94.3B133999@spam.comcast.net> Banjara.Hills@gmail.com wrote: > > Where can I download the subject kit for an Alpha, both Dev and RT? I believe you have to be a DSPP(?) member. That is, an ISV. Then, I think it's available as a download. D.J.D. ------------------------------ Date: Fri, 18 Jul 2008 21:52:44 -0400 From: Stephen Hoffman Subject: Re: HPFMS025 Message-ID: Banjara.Hills@gmail.com wrote: > Where can I download the subject kit for an Alpha, both Dev and RT? It appears you're at United Health Group, right? Given there are likely current licenses and software support through your sponsor, the kits can generally be downloaded directly from HP via access details that are provided with the contract paperwork, or you can ring up the support center and ask for a kit or for a pointer and an access password for the kit FTP site. (I wouldn't think that your sponsor would want you installing random downloads acquired from random sites around the network onto the OpenVMS servers, either. That can be a recipe for getting hacked regardless of the platform, and I'd expect most employers would be rather sensitive to that sort of thing on what are usually business-critical servers and on servers often filled with confidential information.) The HP server farms or HP distribution kits are the best source for products such as FMS, whether on physical media or downloaded from a trusted server. And in this case, the old VMSINSTAL kits used by FMS are not cryptographically signed. Check with HP directly here, in other words. -- www.HoffmanLabs.com Services for OpenVMS ------------------------------ Date: Sat, 19 Jul 2008 00:22:40 -0400 From: JF Mezei Subject: Re: HPFMS025 Message-ID: <48816c3a$0$18578$c3e8da3@news.astraweb.com> Banjara.Hills@gmail.com wrote: > Where can I download the subject kit for an Alpha, both Dev and RT? Are you talking about Digital Equipment Corp FMS , the forms management system ? If you fail to find a good source, contact me via EMAIL, and could accidentally make it available to you under the table. ------------------------------ Date: Sat, 19 Jul 2008 13:51:57 +0800 From: "Richard Maher" Subject: Re: HPFMS025 Message-ID: 2.*5*? Wow, new functionality release? :-) Cheers Richard Maher wrote in message news:206c3e85-5d6e-4c34-a691-ab47d89872c4@z72g2000hsb.googlegroups.com... > Where can I download the subject kit for an Alpha, both Dev and RT? ------------------------------ Date: Fri, 18 Jul 2008 19:08:49 +0000 (UTC) From: Michael Moroney Subject: Non-CDE DECwindows on Itanium? Message-ID: Can you use the old style (like what's still used on a VAX) DECwindows environment on an Itanic running VMS V8.3? ------------------------------ Date: Fri, 18 Jul 2008 21:01:39 -0400 From: Stephen Hoffman Subject: Re: Non-CDE DECwindows on Itanium? Message-ID: Michael Moroney wrote: > Can you use the old style (like what's still used on a VAX) DECwindows > environment on an Itanic running VMS V8.3? What the SPD refers to as the DECwindows Motif or traditional desktop? Yes. (Been there, done that.) Same basic traditional sequence to select or to configure it, too. If you want to use DECwindows on the console as the boot console, you'll best want to use OpenVMS I64 V8.3-1H1. As for the official SPD statement: http://docs.hp.com/en/12705/SPDDW16.pdf -- www.HoffmanLabs.com Services for OpenVMS ------------------------------ Date: Fri, 18 Jul 2008 20:11:12 -0500 From: David J Dachtera Subject: Re: Non-CDE DECwindows on Itanium? Message-ID: <48813F30.C15B31B1@spam.comcast.net> Michael Moroney wrote: > > Can you use the old style (like what's still used on a VAX) DECwindows > environment on an Itanic running VMS V8.3? If it's not an install-time option, it's a good bet that the "old" DECwindows was not ported. D.J.D. ------------------------------ Date: Fri, 18 Jul 2008 20:10:07 -0500 From: David J Dachtera Subject: Re: Question about quoting inside a string Message-ID: <48813EEF.4E6DFDAB@spam.comcast.net> Bob Koehler wrote: > > JF Mezei wrote: > > I need to produce the following: > > > > $im_convert temp.gif - > > -crop 240x300+237+1 - > > -font Helvetica-Bold -pointsize 20 - > > -draw "fill black text 300,280 'value' " temp.jpg > > > > I think this will work, assuming value is a string: > > $im_convert temp.gif - > -crop 240x300+237+1 - > -font Helvetica-Bold -pointsize 20 - > -draw "fill black text 300,280 " + value + " " temp.jpg > > But if it doesn't, then this: > > $temp = "fill black text 300,280 " + value + " " > $im_convert temp.gif - > -crop 240x300+237+1 - > -font Helvetica-Bold -pointsize 20 - > -draw 'temp temp.jpg Almost there. One last refinement: $temp = "fill black text 300,280 '" + value + "'" $im_convert temp.gif - -crop 240x300+237+1 - -font Helvetica-Bold -pointsize 20 - -draw "''temp'" temp.jpg ...ought to do it. D.J.D. ------------------------------ End of INFO-VAX 2008.400 ************************