- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: SYS$INPUT causing COM error v7.2-1
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2008 11:17 AM
тАО01-07-2008 11:17 AM
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?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2008 11:50 AM
тАО01-07-2008 11:50 AM
Re: SYS$INPUT causing COM error v7.2-1
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] = "_
Interactively it should look like:
"SYS$INPUT" = "_
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2008 12:35 PM
тАО01-07-2008 12:35 PM
Re: SYS$INPUT causing COM error v7.2-1
$ 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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2008 12:51 PM
тАО01-07-2008 12:51 PM
Solutionby 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2008 12:53 PM
тАО01-07-2008 12:53 PM
Re: SYS$INPUT causing COM error v7.2-1
Mike, sorry, just now noted you only joined us today.
So
WELCOME to the VMS Forum!!
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2008 01:06 PM
тАО01-07-2008 01:06 PM
Re: SYS$INPUT causing COM error v7.2-1
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!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2008 01:32 PM
тАО01-07-2008 01:32 PM
Re: SYS$INPUT causing COM error v7.2-1
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.