topic Re: EDIT/TPU error in Operating System - OpenVMS

EDIT/TPU error

Noor Ahmed_1 — Thu, 21 Jul 2005 03:47:50 GMT

Hi managers,
I am trying to use EDIT/TPU on OpenVMS VAX V6.2 for VAX4000 105 system. it gives error "Unrecognized qualifier, check validty and spelling"....simple EDIT works. What I have to do for TPU to function...

Rgds

Re: EDIT/TPU error

David B Sneddon — Thu, 21 Jul 2005 03:50:43 GMT

Noor,

What does SHOW SYMBOL EDIT reveal?
Chances are you have a symbol defined and the
/TPU is conflicting with one of the qualifiers
already on the symbol.

Dave

Re: EDIT/TPU error

comarow — Thu, 21 Jul 2005 11:23:49 GMT

Does edit give you edt or tpu?

If not check for logicals or symbols for edit and tpu.

Bob

Re: EDIT/TPU error

Lawrence Czlapinski — Thu, 21 Jul 2005 12:09:49 GMT

Noor: I ran into that when I came to this site. Actually do a
$show sym e*
If you have a symbol for edit it is probably in LOGIN.COM or worse SYLOGIN.COM.
Unfortunately some system managers and/or users do a:
$ e*dit :== - edit/edt/command=sys$manager:edtini.edt
or variation of it. It's not good practice to use a symbol name that will obscure a DCL command. Better would be symbols ed or edt for EDIT/EDT and TPU for EDIT/TPU
Lawrence

Re: EDIT/TPU error

Jan van den Ende — Thu, 21 Jul 2005 12:37:40 GMT

Noor,

_IF_ you meet the situation described above, you will probably NOT want to break existing code.

You can always invoke a command while guaranteeing to NOT use any symbol redefinition by adding an exrta letter to it.
As long as that is NOT the long er form of the symbol, this bypasses the symbol definition.
Also the backslash character ( \ ) will do file.

So,
$ EDIT\
will always get you the plain command.
Of course, after the \ you can add any qualifiers YOU currently require.

hth

Proost.

Have one on me.

jpe

Re: EDIT/TPU error

John Gillings — Thu, 21 Jul 2005 14:30:22 GMT

Noor,

When invoking an editor on an unfamiliar system, I always type it like this:

$ EDITT/TPU

Since DCL only ever looks at the first four characters of a command verb, "EDITT" will be identified as the "EDIT" command, but will bypass any locally defined symbol for "EDIT".

People looking over your shoulder will probably inform you you've made a typo, but you can just say "trust me, I know what I'm doing" ;-)

(of course, one day, some joker will define a symbol:

$ EDITT:=="write sys$output ""ha, ha, got you!""!"

Re: EDIT/TPU error

Willem Grooters — Fri, 22 Jul 2005 00:52:46 GMT

<$ EDITT:=="write sys$output ""ha, ha, got you!""!">

No you didn't:

$ EDITTT

Re: EDIT/TPU error

Jan van den Ende — Fri, 22 Jul 2005 03:21:54 GMT

... and that is where EDIT\/TPU comes in REAL handy!

Proost.

Have one on me.

jpe

Re: EDIT/TPU error

Lawrence Czlapinski — Mon, 25 Jul 2005 14:24:03 GMT

I once worked on a VMS system that had a PRINT symbol defined with a queue name attached. The printer that was selected was on another floor that was locked after a certain time. The adding an extra character trick would have been helpful.
Lawrence