- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Problems Running a TCPIP Service
Operating System - OpenVMS
1753265
Members
5405
Online
108792
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
09-08-2009 06:38 PM
09-08-2009 06:38 PM
Re: Problems Running a TCPIP Service
> %SET-W-NOTSET, error modifying $1$DGA481:
> -SET-E-INVDEV, device is invalid for requested operation
This looks like a [SY]LOGIN.COM trying to do
a SET TERMINAL command in a non-interactive
job, where the "terminal" is a disk (file).
As "HELP SET TERMINAL Parameter" says:
device-name[:]
Specifies the device name of the terminal. The default is
SYS$COMMAND if that device is a terminal. If the device is not
a terminal, an error message is displayed.
In a non-interactive job (often a batch job),
you get an error like this. The usual cure
is some conditionality on the SET TERMINAL
command, like, say:
[...]
$ IF (F$MODE() .EQS. "INTERACTIVE")
$ THEN
$ IF (F$GETDVI( "TT:", "DEVCLASS") .EQ. 66)
$ THEN
$ SET TERMINAL /INQUIRE /INSERT
[...]
To see the details, stick in some kind of
"SHOW LOGICAL SYS$COMMAND" where you can see
its output.
> -SET-E-INVDEV, device is invalid for requested operation
This looks like a [SY]LOGIN.COM trying to do
a SET TERMINAL command in a non-interactive
job, where the "terminal" is a disk (file).
As "HELP SET TERMINAL Parameter" says:
device-name[:]
Specifies the device name of the terminal. The default is
SYS$COMMAND if that device is a terminal. If the device is not
a terminal, an error message is displayed.
In a non-interactive job (often a batch job),
you get an error like this. The usual cure
is some conditionality on the SET TERMINAL
command, like, say:
[...]
$ IF (F$MODE() .EQS. "INTERACTIVE")
$ THEN
$ IF (F$GETDVI( "TT:", "DEVCLASS") .EQ. 66)
$ THEN
$ SET TERMINAL /INQUIRE /INSERT
[...]
To see the details, stick in some kind of
"SHOW LOGICAL SYS$COMMAND" where you can see
its output.
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP