topic Re: SYS$INPUT causing COM error v7.2-1 in Operating System - OpenVMS

SYS$INPUT causing COM error v7.2-1

Mike D'Amico — Mon, 07 Jan 2008 19:17:26 GMT

Hello, We have an Alpha server 8400 running openVMS 7.2-1.

When I run SYS$MANAGER:TCPIP$CONFIG.COM, I get this error:
%TYPE, file not accessible SYS$INPUT:.;
-RMS, file specification syntax error

When I look at the TCPIP$CONFIG.COM file it is failing on the first "TYPE" statement while trying to output to the screen.
$TYPE SYS$INPUT

Infact, sys$input doesn't work in any context on the system.

Is this something related VMS 7.2-1? Is there a workaround in lieu of installing a patch or upgrade?

Re: SYS$INPUT causing COM error v7.2-1

Hein van den Heuvel — Mon, 07 Jan 2008 19:50:04 GMT

Mike, what you describe is 'too big a bug'.

Something is mucking with your environment!
When did this start failing?
Check edits to SYLOGIN.COM and LOGIN.COM.

Out-of-the-box SYS$INPUT works.
It works on all OpenVMS versions from V1.0 on
It works without a patch.

Do a SHOW LOGICAL SYS$INPUT /FULL

In a batch job it should look like:

"SYS$INPUT" [exec] = "_$:" [terminal] (LNM$PROCESS_TABLE)

Interactively it should look like:

"SYS$INPUT" = "_$:" [terminal] (LNM$PROCESS_TABLE)

terminal_name could be something like FTA12, RTA1, TNA5, OPA1, or I suppose even TTA1: for a 'real' terminal.

fyi... The term "[terminal]" does not refer to it being a terminal device, just a terminal (last) translation.

Good luck
Hein.

Re: SYS$INPUT causing COM error v7.2-1

Mike D'Amico — Mon, 07 Jan 2008 20:35:23 GMT

I checked the main login.com and there is an assignment in there as follows:

$ define/nolog sys$input sys$command

If do a $ Sho Log SYS$INPUT/FULL I get:

"SYS$INPUT" [exec] = "_TNA1310:" [concealed,terminal] (LNM$PROCESS_TABLE)

The same result is given for SYS$COMMAND.
So for some reason they are set to be equal. Do you think this could be the problem?

Re: SYS$INPUT causing COM error v7.2-1

Jan van den Ende — Mon, 07 Jan 2008 20:51:45 GMT

Mike,

by default SYS$INPUT is teh procedure that is executing.
Any line following asometing that takes input from the default input stream just reads the nexr lines, until the terminator is encountered.
(by default a "$", there are ways to manipulate that)

Interactively, SYS$COMMAND is by default the terminal you type into.

Now, somewhere in the procedure you try to execute there is a TYPE SYS$INPUT

That would normally just display the next lines in the procedure.

But, SYLOGIN command DEFINE SYS$INPUT SYS$COMMAND tells the command processor to get what it is to display ... FROM the terminal!

$ DEFINE SYS$INPUT SYS$COMMAND
should DEFINITELY NOT be in sys$sylogin!!!

hth

Proost.

Have one on me.

jpe

Re: SYS$INPUT causing COM error v7.2-1

Jan van den Ende — Mon, 07 Jan 2008 20:53:34 GMT

Oops,

Mike, sorry, just now noted you only joined us today.

So

WELCOME to the VMS Forum!!

Proost.

Have one on me.

jpe

Re: SYS$INPUT causing COM error v7.2-1

Mike D'Amico — Mon, 07 Jan 2008 21:06:00 GMT

That worked Thank You !!!

Although, I am not sure if something in one of the applications on this server needed this assignment. I will re-configure IP then put the assignment back until I can figure out what the heck is goin on. Thanks Again for your help!!!

Re: SYS$INPUT causing COM error v7.2-1

Hein van den Heuvel — Mon, 07 Jan 2008 21:32:01 GMT

$DEFINE SYS$INPUT SYS$COMMAND

This is typicall used just before running an image from a command file (cobol program, edit, ...) which needs input from teh terminal.

The appropriate way to use that is as the very last action right before the image and to add /USER to make sure the assignment is gone when the image is done (or explodes).

Cheers,
Hein.