HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Submit in batch fails
Operating System - OpenVMS
1827897
Members
1705
Online
109970
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
Forums
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
07-10-2009 11:24 AM
07-10-2009 11:24 AM
Re: Submit in batch fails
The question author wrote:
> Got it:
> somewhere in the login sequence, the definition of SYS$OUTPUT is reversed - which, of course, causes a loop:
>
> > sho log sys$output
> "SYS$OUTPUT" = "_NODE11$TNA972:" (LNM$PROCESS_TABLE)
> > show log _NODE1$TNA972
> "_NODE1$TNA972" = "SYS$OUTPUT" (LNM$PROCESS_TABLE)
> 1 "SYS$OUTPUT" = "_NODE1$TNA972:" (LNM$PROCESS_TABLE)
How can this be a loop as the equvialence name for SYS$OUTPUT is a terminal one?
$ show logical/full sys$output
"SYS$OUTPUT" [super,confine] = "_NODEX$NTA3:" [concealed,terminal] (LNM$PROCE
SS_TABLE)
(Terminal equivalence names are not translated.)
> In batch, this leads to:
>
> > sho log sys$output
> "SYS$OUTPUT" = "_DSA7:" (LNM$PROCESS_TABLE)
> > show log _DSA7
> "_DSA7" = "SYS$OUTPUT" (LNM$PROCESS_TABLE)
Still a terminal equivalence name, though not a concealed one:
$ SET NOVERIFY
Running FELDMAN's LOGIN.COM at 2009-07-10 19:19:46.99
$ show logical/full sys$output
"SYS$OUTPUT" [super,confine] = "_DSA1:" [terminal] (LNM$PROCESS_TABLE)
FELDMAN job terminated at 10-JUL-2009 19:19:47.08
So how can you get a loop from this?
>
> Quite possible that SUBMIT doesn't like the circular reference (though SYS$INPUT and SY$OUTPUT refer to this device as well).
>
> We're still investigating where this definition comes from. In the mean time, the workaround is:
>
> $ oops=F$parse(";",me,,,"NO_CONCEAL") - ";"
What is "me"?
> $ if oops .nes. ""
> $ then
> $ oopsdev="_"+f$element(0,":",oops)
> $ deass/process 'oopsdev'
> ...
>
> Now submit succeeds.
AEFAEF
> Got it:
> somewhere in the login sequence, the definition of SYS$OUTPUT is reversed - which, of course, causes a loop:
>
> > sho log sys$output
> "SYS$OUTPUT" = "_NODE11$TNA972:" (LNM$PROCESS_TABLE)
> > show log _NODE1$TNA972
> "_NODE1$TNA972" = "SYS$OUTPUT" (LNM$PROCESS_TABLE)
> 1 "SYS$OUTPUT" = "_NODE1$TNA972:" (LNM$PROCESS_TABLE)
How can this be a loop as the equvialence name for SYS$OUTPUT is a terminal one?
$ show logical/full sys$output
"SYS$OUTPUT" [super,confine] = "_NODEX$NTA3:" [concealed,terminal] (LNM$PROCE
SS_TABLE)
(Terminal equivalence names are not translated.)
> In batch, this leads to:
>
> > sho log sys$output
> "SYS$OUTPUT" = "_DSA7:" (LNM$PROCESS_TABLE)
> > show log _DSA7
> "_DSA7" = "SYS$OUTPUT" (LNM$PROCESS_TABLE)
Still a terminal equivalence name, though not a concealed one:
$ SET NOVERIFY
Running FELDMAN's LOGIN.COM at 2009-07-10 19:19:46.99
$ show logical/full sys$output
"SYS$OUTPUT" [super,confine] = "_DSA1:" [terminal] (LNM$PROCESS_TABLE)
FELDMAN job terminated at 10-JUL-2009 19:19:47.08
So how can you get a loop from this?
>
> Quite possible that SUBMIT doesn't like the circular reference (though SYS$INPUT and SY$OUTPUT refer to this device as well).
>
> We're still investigating where this definition comes from. In the mean time, the workaround is:
>
> $ oops=F$parse(";",me,,,"NO_CONCEAL") - ";"
What is "me"?
> $ if oops .nes. ""
> $ then
> $ oopsdev="_"+f$element(0,":",oops)
> $ deass/process 'oopsdev'
> ...
>
> Now submit succeeds.
AEFAEF
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-10-2009 01:13 PM
07-10-2009 01:13 PM
Re: Submit in batch fails
I wrote:
"
[...]
Still a terminal equivalence name, though not a concealed one:
$ SET NOVERIFY
Running FELDMAN's LOGIN.COM at 2009-07-10 19:19:46.99
$ show logical/full sys$output
"SYS$OUTPUT" [super,confine] = "_DSA1:" [terminal] (LNM$PROCESS_TABLE)
FELDMAN job terminated at 10-JUL-2009 19:19:47.08
So how can you get a loop from this?
[...]
"
Never mind. I was still thinking of the interactive case, I guess. I was thinking of SYS$OUTPUT going to DSA1 and stopping. Of course, one can use DSA1 and get into a loop. OK. Silly me. Need more sleep! Sorry to bother you.
AEFAEF
"
[...]
Still a terminal equivalence name, though not a concealed one:
$ SET NOVERIFY
Running FELDMAN's LOGIN.COM at 2009-07-10 19:19:46.99
$ show logical/full sys$output
"SYS$OUTPUT" [super,confine] = "_DSA1:" [terminal] (LNM$PROCESS_TABLE)
FELDMAN job terminated at 10-JUL-2009 19:19:47.08
So how can you get a loop from this?
[...]
"
Never mind. I was still thinking of the interactive case, I guess. I was thinking of SYS$OUTPUT going to DSA1 and stopping. Of course, one can use DSA1 and get into a loop. OK. Silly me. Need more sleep! Sorry to bother you.
AEFAEF
- « 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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP