INFO-VAX Fri, 01 Feb 2008 Volume 2008 : Issue 64 Contents: Re: "file locked by another user" mystery compilation error while porting Alpha application to Itanium decnet IV on VMS 8.3 Re: Looking for a DECserver 200/MC/ or 300 Question on DEFINE/FORM Re: Restricting Access to TCP/IP and DECnet VMS Audio Update - Episode #15 Re: VT100 standards Re: VT100 standards Re: VT100 standards Re: VT100 standards Re: VT100 standards Re: VT100 standards Re: VT100 standards Re: Yet another hobbyist software kit request. Re: Yet another hobbyist software kit request. ---------------------------------------------------------------------- Date: Fri, 1 Feb 2008 07:53:07 -0800 (PST) From: AEF Subject: Re: "file locked by another user" mystery Message-ID: On Jan 31, 11:58 pm, Fred Bach wrote: > Comments interspersed. You fellows are sure coming up with > some cool ideas. > > AEF wrote: > > On Jan 29, 6:14 pm, Fred Bach wrote: > >> Mr Briggs, > [...] > > >>>> If you specified an error condition as the condition parameter, > >>>> the action is taken when errors equal to or greater than the > >>>> specified level of error occur. > > > While this doesn't explicitly explain it, it does strongly hint that > > you can't have separate commands for the 3 different error levels. > > (Note the "equal to or greater than" phrase.) > > I agree that is a hint. But the help says an ERROR condition. > Notice that the help does NOT say what would happen if the > $SEVERITY were lower and the ON WARNING were previously > specified. I agree that if one were to apply parallelism > from the ON ERROR structure to the ON WARNING structure, then > one could say that it is all explained in the help. However, > as it stands, the help wouldn't make it past any lawyers, that's > for sure. Just to be explicit about it(!): I agree that the HELP should explain it better. > > > The User's Manual is the > > appropriate reference here. > > No fair. :-) :-) It's just that the DCL help is so much easier > to get to. I know I read most, if not all, of the User's Manual > probably over 20 years ago back when it was paper and when I took > the bus a lot. Can't seem to hold it all in my head, though. I > know this stuff is all online at HP, but who has time to actually > read it 'cover to cover', so to speak, at work? But a paper manual > is much easier to read on the bus. > > To search the DCL Help, I used to extract ALL the DCL HELP to a > single file from time to time and then search that for keywords. > Was very useful. And then the DCL HELP file got bigger and bigger. > Maybe I should get back to doing that now that our SYS$SCRATCH > space is bigger too. I do that sometimes, too. > > > I admit it's certainly not clear here in > > the HELP reference -- especially as the CONTROL_Y condition, which > > _is_ independent of ON W|E|S, is commingled with W, E, and S!, but the > > hint is there. > [...] > > >> Typically, to handle all possible conditions that might happen to > >> the user, I feel that I need to specify different actions for > >> the various ON conditions. Such as "ON WARNING THEN CONTINUE" > >> and "ON ERROR THEN GOTO EXIT" and "ON SEVERE THEN STOP" which > >> would be the typical set of ON commands I would use. They > >> all seemed to function just fine together in the same DCL routine. > >> Over all these years they did not appear to interfere with each > >> other. Things worked very well and the desired action seemed > >> to be taken. > > > Well, I wouldn't want to STOP on severe errors as I'd probably want to > > do some cleanup. Also, it's somewhat arbitrary what constitutes a > > warning vs. an error vs. a "severe error". Why should editing ADSF: be > > fatal while TYPEing it only a warning?: > > > $ TYPE ASDF:[ASDF]ASDF > > %TYPE-W-SEARCHFAIL, error searching for ASDF:[ASDF]ASDF.LIS; > > -RMS-F-DEV, error in device name or inappropriate device type for > > operation > > $ SH SYM $SEVERITY > > $SEVERITY == "0" > > $ > > $ EDIT/EDT ASDF:[ASDF]ASDF > > %EDT-F-OPENIN, error opening ASDF:[ASDF]ASDF.; as input > > -RMS-F-DEV, error in device name or inappropriate device type for > > operation > > $ SH SYM $SEVERITY > > $SEVERITY == "4" > > $ > > Yes, that's a really great question! Why *does* TYPE give a > Warning whereas EDIT gives a SEVERE? Beats me. > > As far as "STOP" on severe_error goes, well, I guess the > idea was to get the operators to call for help. Now and then > I would throw in my phone number at a point like that. The BACKUP command assigns, IMO, severity levels appropriately to its various possible errors. For DCL I usually just use ON WARNING THEN GOTO _ERROR at the beginning of the command procedure with an occasional SET NOON, SET ON, and checks of $SEVERITY or $STATUS where needed. > > > If you want to take different actions based on different values of > > $SEVERITY, you need to use SET NOON and check the $STATUS and/or > > $SEVERITY symbols after each command. Alternatively, here's a trick > > that might do what you want. It will branch to different parts of the > > code based on a single ON command. And it uses the ampersand!!! (What > > more could you want??? ;-) (See below for info about the RETURN > > trick.) > > > $ ON WARNING THEN GOTO &$SEVERITY > > . > > Now there's another trick I might not have thought of! > I seem to recall, perhaps incorrectly, from somewhere > that it was bad form to start symbols with numbers, so > I never did it. And I guess I applied that subconsciously > to DCL labels as well. I know that in some of our private > graphic routines (not DCL) I cannot read lines of data into > symbols (based on field locations) that begin with numerals. > I'd bet that spilled over to my DCL coding. You're right that you can't start a symbol with a numeral, and I did recall that labels are sort of symbols, too. [Looking it up now I found this in the User's Manual: 3.2.1 Labels in Local Symbol Tables As the command interpreter encounters labels, it enters them in a special section of the local symbol table. ] So you're rightly concerned, but I said to myself, "Damn the torpedoes", and tried it anyway and it worked! Maybe there's a way to embed the &$SEVERITY in a label that starts with a letter, but I can't think of one right now. You need the ampersand to delay symbol substitution to the time where the ON condition happens and the command part of the ON command is actually executed. [...] > > Well, I use the following trick (only works if you are NOT in a local > > subroutine) > > > Use the return command and specify 0 for warning, 2 for error, and 4 > > for severe error. > > > Example: > > > $ TYPE TEST-ERROR.COM > > $ SET VERIFY > > $ SET NOON > > $ RETURN 4 > > $ SHOW SYMBOL $STATUS > > $ SHOW SYMBOL $SEVERITY > > $ ON WARNING THEN SHOW TIME > > $ RETURN 0 > > $ SET NOVERIFY > > $ EXIT > > What a novel use of the RETURN command right inside > a single script itself! And I would have guessed that > this was illegal because you are not actually returning > from any subroutine. And for sure this example is not > in the DCL Help either. I looked under HELP RETURN. > Nice thinking! Thanks! I thought of this when I was working on TO.COM. I needed something like this and I also wondered what would happen if you had a RETURN command without having run GOSUB first. Then I put them together! [...] AEF ------------------------------ Date: Fri, 1 Feb 2008 10:27:41 -0800 (PST) From: vineet Subject: compilation error while porting Alpha application to Itanium Message-ID: <232adf59-2804-4d55-90b8-4224e5277c9c@v29g2000hsf.googlegroups.com> Hi, I am getting following error while compiling Alpha application at itanium server. class type_info ......^ %CXX-E-BADSCPDEF, class "type_info" cannot be defined in the current scope at line number 81 in module TYPEINFO. of text library SYS$COMMON: [SYSLIB]CXXL$ANSI_DEF.TLB;1 _RWSTD_EXPORT virtual ~type_info (); ..........................^ %CXX-E-BADDTORDECL, invalid destructor declaration at line number 88 in module TYPEINFO. of text library SYS$COMMON: [SYSLIB]CXXL$ANSI_DEF.TLB;1 explicit type_info (const char*); ........................^ %CXX-W-TYPQUALIGN, type qualifier ignored at line number 120 in module TYPEINFO. of text library SYS$COMMON: [SYSLIB]CXXL$ANSI_DEF.TLB;1 explicit type_info (const char*); ..............................^ %CXX-E-EXPID, expected an identifier at line number 120 in module TYPEINFO. of text library SYS$COMMON: [SYSLIB]CXXL$ANSI_DEF.TLB;1 explicit type_info (const char*); ....^ %CXX-E-EXPL, "explicit" is not allowed at line number 120 in module TYPEINFO. of text library SYS$COMMON: [SYSLIB]CXXL$ANSI_DEF.TLB;1 type_info (const type_info&); // undefined ...............^ Can one please give me a clue what wrong here in my application. TiA, Vineet ------------------------------ Date: Fri, 1 Feb 2008 13:20:01 -0500 From: "Hank Vander Waal" Subject: decnet IV on VMS 8.3 Message-ID: <005f01c864ff$161ee260$6500a8c0@dellxp30> I have an Itantium system with VMS 8.3 that I am trying to get DECNET IV up and running on. TCP/IP works fine on it but when I run NETCONFIG it bombs trying to configure the line with: %SYSTEM-W-NOSUCHDEV, no such device available I do a show device E on it and the system shows device EIA0 online but I can not get NCP to take it when I enter set line EIA-0 Any ideas ?? ------------------------------ Date: Fri, 1 Feb 2008 13:14:51 +0000 (UTC) From: david20@alpha2.mdx.ac.uk Subject: Re: Looking for a DECserver 200/MC/ or 300 Message-ID: In article <13q3okgn0g95hc9@news.supernews.com>, "David Turner, Island Computers" writes: >If you could use a DSRVZ-MC 32port Decserver 900 I have a few > > >-- >David B Turner >Island Computers US Corp >1207 East Highway 80 >Suite D >Tybee GA 31328 > >Toll Free: 877-6364332 x201 >Intl: 912 786 8502 x201 >Fax: 912 786 8505 >E: dturner@islandco.com >F: 912 201 0402 >W: http://www.islandco.com > > > >The information transmitted is intended only for the person or entity to >which it is addressed and may contain confidential, proprietary, and/or >privileged material. Any review, retransmission, dissemination or other use >of, or taking of any action in reliance upon this information by persons or >entities other than the intended recipient is prohibited. If you received >this in error, please contact the sender and delete the material from all >computers. > Sorry I think I'll have trouble deleting this from Google's computers :) David Webb Security team leader CCSS Middlesex University ------------------------------ Date: Fri, 1 Feb 2008 12:35:16 -0500 From: norm.raphael@metso.com Subject: Question on DEFINE/FORM Message-ID: This is a multipart message in MIME format. --=_alternative 00609EE7852573E2_= Content-Type: text/plain; charset="US-ASCII" Here is help for DEFINE /FORM DEFINE /FORM Assigns a numeric value and attributes to a print form name. The /FORM qualifier is required. To modify a form's name or number, you must delete and redefine the form. Values for any DEFINE/FORM qualifier can be modified by reentering the DEFINE/FORM command with different values, as long as the form name and number remain the same. As I read it, there is a subtile trap in it. If I had $ DEFINE/FORM FORM1 /STOCK=SPECIAL /LENGTH=60 /NOSETUP and I redefined it with $ DEFINE/FORM FORM1 /LENGTH=66 /NOSETUP there would still be a "STOCK=SPECIAL" setting because a "different value" would not have been entered. That is, if redefining a form with the same name and number, you must needs reenter all values to be sure they are what is required. Is that correct? --=_alternative 00609EE7852573E2_= Content-Type: text/html; charset="US-ASCII"
Here is help for DEFINE /FORM

    DEFINE /FORM

       Assigns a numeric value and attributes to a print form name. The
       /FORM qualifier is required. To modify a form's name or number,
       you must delete and redefine the form. Values for any DEFINE/FORM
       qualifier can be modified by reentering the DEFINE/FORM command
       with different values, as long as the form name and number remain
       the same.

As I read it, there is a subtile trap in it.

If I had
$ DEFINE/FORM FORM1 /STOCK=SPECIAL /LENGTH=60 /NOSETUP
and I redefined it with
$ DEFINE/FORM FORM1 /LENGTH=66 /NOSETUP
there would still be a "STOCK=SPECIAL" setting because
a "different value" would not have been entered.

That is, if redefining a form with the same name and number,
you must needs reenter all values to be sure they are what is required.
Is that correct? --=_alternative 00609EE7852573E2_=-- ------------------------------ Date: 1 Feb 2008 07:48:37 -0600 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: Restricting Access to TCP/IP and DECnet Message-ID: In article , "Robert Jarratt" writes: > > Yes I know that, but I am prepared to accept that risk. That said, what > alternatives do you suggest? Why not SSH? ------------------------------ Date: Fri, 1 Feb 2008 10:50:57 -0800 (PST) From: IanMiller Subject: VMS Audio Update - Episode #15 Message-ID: <1adbd1f4-4b2e-422e-94fd-e76b5369bae9@d4g2000prg.googlegroups.com> In this episode, we'll cover some of the news highlights since the last update, play an interview from Seagull Software regarding upgrading terminal apps, and check in with Sue and Hoff. http://www.openvms.org/stories.php?story=08/02/01/1564701 We always want to hear from people willing to contribute. Feedback always welcome via http://www.openvms.org/feedback ------------------------------ Date: 1 Feb 2008 07:53:04 -0600 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: VT100 standards Message-ID: In article , "Richard Maher" writes: > Hi, > > Is anyone willing to discuss at length the escape sequences for lighting up > my VT100 LEDs? If we could incorporate that with some form of ^G pitch > control then I really think we can show off VMS's core strengths :-( > I have a little Fortran program I wrote to cycle through a variety of VT100 features, including cycling the LEDs. I generally use it to check out each new VT emulator to see how well it does. But not since having an actual VT100 have I seen anything emulating the LEDs (VT200 and later just seem to ignore these sequences). ------------------------------ Date: Fri, 01 Feb 2008 15:12:44 GMT From: "John E. Malmberg" Subject: Re: VT100 standards Message-ID: Bob Koehler wrote: > In article , "Richard Maher" writes: >> Hi, >> >> Is anyone willing to discuss at length the escape sequences for lighting up >> my VT100 LEDs? If we could incorporate that with some form of ^G pitch >> control then I really think we can show off VMS's core strengths :-( >> > > I have a little Fortran program I wrote to cycle through a variety > of VT100 features, including cycling the LEDs. > > I generally use it to check out each new VT emulator to see how well > it does. But not since having an actual VT100 have I seen anything > emulating the LEDs (VT200 and later just seem to ignore these > sequences). IIRC: VT200 seems to use those sequences or a number close to them to manipulate the caps lock and scroll lock lights. Have fun playing. I do not suppose there is a single site that has all the ANSI and Private escape sequences that exist in the wild? -John wb8tyw@qsl.network Personal Opinion Only ------------------------------ Date: Fri, 1 Feb 2008 09:28:10 -0600 (CST) From: sms@antinode.org (Steven M. Schweda) Subject: Re: VT100 standards Message-ID: <08020109281044_2062A39A@antinode.org> From: "John E. Malmberg" > Bob Koehler wrote: > > > I have a little Fortran program I wrote to cycle through a variety > > of VT100 features, including cycling the LEDs. > > > > I generally use it to check out each new VT emulator to see how well > > it does. But not since having an actual VT100 have I seen anything > > emulating the LEDs (VT200 and later just seem to ignore these > > sequences). > > IIRC: VT200 seems to use those sequences or a number close to them to > manipulate the caps lock and scroll lock lights. My LK201 has Hold Screen, Lock, Compose, and Wait. My LK411-AA has only the ones for Hold Screen and Lock. I haven't had a VT1xx for a long time, but as I recall, it had four LEDs, like an LK201. When one of my Alphas goes into screen-saver mode, the two LEDs in the LK411-xx seem to be saying, Hold - Lock - - - [...], so I always assumed that it was still trying to operate all four lights (as on a VAXstation with the LK201), even though the keyboard has only two of them. Of course, talking directly to a keyboard and talking to a terminal with a keyboard wre two different things. ------------------------------------------------------------------------ Steven M. Schweda sms@antinode-org 382 South Warwick Street (+1) 651-699-9818 Saint Paul MN 55105-2547 ------------------------------ Date: 01 Feb 2008 15:54:00 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: VT100 standards Message-ID: <47a34098$0$6344$607ed4bc@cv.net> In article , koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: >In article , "Richard Maher" writes: >> Hi, >> >> Is anyone willing to discuss at length the escape sequences for lighting up >> my VT100 LEDs? If we could incorporate that with some form of ^G pitch >> control then I really think we can show off VMS's core strengths :-( >> > > I have a little Fortran program I wrote to cycle through a variety > of VT100 features, including cycling the LEDs. > > I generally use it to check out each new VT emulator to see how well > it does. But not since having an actual VT100 have I seen anything > emulating the LEDs (VT200 and later just seem to ignore these > sequences). VTTEST (appears on the OpenVMS Freeware) has been a great tool for testing terminal emulation. I have written a utility I call VT400RT which tests a number of VT400 sequences (protected editing and rectangular functions). What would be the equivalent of a VT100's keyboard LEDs on a Weendoze box? -- 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: Fri, 1 Feb 2008 17:46:47 +0000 (UTC) From: moroney@world.std.spaamtrap.com (Michael Moroney) Subject: Re: VT100 standards Message-ID: VAXman- @SendSpamHere.ORG writes: >What would be the equivalent of a VT100's keyboard LEDs on a Weendoze box? Most PC keyboards have some sort of Num Lock, Caps Lock and/or Scroll Lock lights. I work with a sort of terminal emulator that manipulates one of them. ------------------------------ Date: 1 Feb 2008 12:29:48 -0600 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: VT100 standards Message-ID: In article <08020109281044_2062A39A@antinode.org>, sms@antinode.org (Steven M. Schweda) writes: > > My LK201 has Hold Screen, Lock, Compose, and Wait. My LK411-AA has > only the ones for Hold Screen and Lock. The LEDs on a VT100 were for the soul use of the user. My program does not manipulate the hld screen or caps lock LEDs on my LK401. ------------------------------ Date: 1 Feb 2008 12:31:17 -0600 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: VT100 standards Message-ID: In article <47a34098$0$6344$607ed4bc@cv.net>, VAXman- @SendSpamHere.ORG writes: > > What would be the equivalent of a VT100's keyboard LEDs on a Weendoze box? On any GUI interface, the LEDs could be emulated on screen by the emulator. Since DECterm doesn't bother and I never saw anyone put the VT100 LEDs to real use, I suspect there's little cause to do so. ------------------------------ Date: Fri, 1 Feb 2008 03:17:25 -0800 (PST) From: IanMiller Subject: Re: Yet another hobbyist software kit request. Message-ID: <859c5858-5ec9-4693-90f8-fa566b6f63fa@h11g2000prf.googlegroups.com> I think the new hobbyist CD includes DECset ------------------------------ Date: Fri, 1 Feb 2008 07:27:49 -0600 (CST) From: sms@antinode.org (Steven M. Schweda) Subject: Re: Yet another hobbyist software kit request. Message-ID: <08020107274962_2062A39A@antinode.org> From: Cluster-Karl > You can find the alpha kit here: > > ftp://ftp.itrc.hp.com/openvms_patches/layered_products/alpha/ And the IA64 kit under "i64", too. That was much too easy (other than running out of global sections on the first try at installing the stuff on the ZX2000). Thanks for the pointer. (And thanks to the others for their kind offers, too.) MMS V3.8-2 seems to work better on an ODS5 disk than V3.5 or V3.7, too. (What will I do when there's nothing left about which to complain?) From: IanMiller > I think the new hobbyist CD includes DECset I'm ready when it is, even if I may not need much of what's on it these days (what with the secret FTP server, and all). Anyone know of any plans for an IA64 DVD, too? (I see only two "Media Kits" forums at "http://www.openvmshobbyist.com/phpbb2/index.php", and they're both CD.) I wonder how many of these things are sold. Anyone know? ------------------------------------------------------------------------ Steven M. Schweda sms@antinode-org 382 South Warwick Street (+1) 651-699-9818 Saint Paul MN 55105-2547 ------------------------------ End of INFO-VAX 2008.064 ************************