1829404 Members
2224 Online
109991 Solutions
New Discussion

Re: EDIT/TPU error

 
SOLVED
Go to solution
Noor Ahmed_1
Advisor

EDIT/TPU error

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
8 REPLIES 8
David B Sneddon
Honored Contributor
Solution

Re: EDIT/TPU error

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
comarow
Trusted Contributor

Re: EDIT/TPU error

Does edit give you edt or tpu?

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

Bob
Lawrence Czlapinski
Trusted Contributor

Re: EDIT/TPU error

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
Jan van den Ende
Honored Contributor

Re: EDIT/TPU error

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
Don't rust yours pelled jacker to fine doll missed aches.
John Gillings
Honored Contributor

Re: EDIT/TPU error

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!""!"

A crucible of informative mistakes
Willem Grooters
Honored Contributor

Re: EDIT/TPU error

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

No you didn't:

$ EDITTT

Willem Grooters
OpenVMS Developer & System Manager
Jan van den Ende
Honored Contributor

Re: EDIT/TPU error

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

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.
Lawrence Czlapinski
Trusted Contributor

Re: EDIT/TPU error

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