- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- DCL confusion
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
тАО09-13-2004 06:09 PM
тАО09-13-2004 06:09 PM
edit/tpu lat_ports|@ops$proc:x.com
It seemed that x.com was executed in a special way (line per line). Why ?
Wim
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2004 07:01 PM
тАО09-13-2004 07:01 PM
Re: DCL confusion
what were your real intention?
Reading your command line I guess you forgot PIPE command and the output of edit is input of x command file.
Without PIPE, DCL ignore edit and execute x.com.
Antonio Vigliotti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2004 07:03 PM
тАО09-13-2004 07:03 PM
Re: DCL confusion
I tried to edit a file.
But my command was screwed while doing cut/paste.
But why did edit execute the part of the name of the file ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2004 07:26 PM
тАО09-13-2004 07:26 PM
Re: DCL confusion
the @-sign essentially specifies indirection.
Even in
@commandoprocedure.com
you essentially just specify:
I want a number of commands executed, and they are in Commandprocedure.com
In case of your accidental command construct, it is taken to mean: find your actions to be performed on SYS$PIPE in ops$proc:x.com
How this exactly works out in case of edit/tpu appears to be doing something, but I don't dare guess at details.
Although, you did NOT use the PIPE command??
On second thought I would GUESS that it is interpreted more or less similar to
edit/tpu /command=...
fwiw
Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2004 07:30 PM
тАО09-13-2004 07:30 PM
Re: DCL confusion
old problem; @ Symbol is parsed before any other token in line.
If you type
$
the parser execute x.com;
I don't know why but this happens since V6.2.
Antonio Vigliotti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2004 07:38 PM
тАО09-13-2004 07:38 PM
Re: DCL confusion
$$ create a.tmp
sys$login:*.com;
*Exit*
$$ directory @a.tmp
Directory USER_XYZ:[ZESSIN]
LOGIN.COM;1 LOGIN2.COM;1
Total of 2 files.
$$
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2004 08:26 AM
тАО09-14-2004 08:26 AM
Re: DCL confusion
Do I understand correctly : the contents of the file is placed on the command line.
But how to explain that EDIT/TPU executes it as a command file but line per line ?
WIm
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2004 08:27 AM
тАО09-14-2004 08:27 AM
Re: DCL confusion
And where is this documented (or is it undocumented ??) ?
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2004 09:23 AM
тАО09-14-2004 09:23 AM
Re: DCL confusion
Basically what it does DCL extends your EDIT command line with the 1st line from the command procedure which I guess caused an error. The '@' redirected (temporarily) DCL input to your command procedure and DCL executes it line-by-line.
/Guenther
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2004 09:28 AM
тАО09-14-2004 09:28 AM
SolutionFor example, consider LIST.COM:
FILE1.TXT, FILE2.TXT, FILE3.TXT
$ TYPE/PAGE @LIST
will substitute the contents of LIST.COM into the TYPE command. Everything needs to be placed on the first line, or use continuation lines.
What's very strange is that lines following the first are executed after completion of the command. So changing LIST.COM to
FILE1.TXT, FILE2.TXT, FILE3.TXT
$ SHOW TIME
will execute the SHOW TIME command after TYPE completes.
The procedure also takes parameters like any other procedure. Consider:
FILE1.TXT, 'p1'.TXT, 'p2'.TXT
$ SHOW TIME
$ 'p3'
$ TYPE @LIST FILE2 FILE3 "SHOW PROCESS"
This will type the 3 files, then show time then show process.
I've often thought this *looks* useful, but never really found a compelling use for it.
It is documented, see "HELP @" - " or requests the command interpreter to read subsequent command input from a specific file or device"
Also note it's caused MAIL all kinds of trouble!