- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Running COM in OpenVMS
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
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
тАО10-27-2010 07:27 AM
тАО10-27-2010 07:27 AM
Running COM in OpenVMS
I just need to know one thing.
If i run a COM , i can redirect the output to some other file.
For example : abc.com /out = abc.log
Here, only after the COM is completely executed, i am able to see the contents in the output file.
Is it possible to get the details into the output file while the COM is running ?
or is it possible to see the output when the COM is running ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2010 07:35 AM
тАО10-27-2010 07:35 AM
Re: Running COM in OpenVMS
an outputfile specified this way is single user, so generally: NO.
If you know in advance in a specific case, you can
$ SET HOST 0 /LOG or
$ SET HOST 0 /LOG=
Now you log in again, and @ the .com; and you 'll see the output immediately.
The /LOG=file is especially usefull in debugging!
Success.
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2010 11:22 AM
тАО10-27-2010 11:22 AM
Re: Running COM in OpenVMS
$ help pipe examples
...
5.$ ! TEE.COM - command procedure to display/log data flowing through
$ ! a pipeline
$ ! Usage: @TEE log-file
...
You could use it like this:
$ pipe @abc | @tee abc.log
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2010 12:20 PM
тАО10-27-2010 12:20 PM
Re: Running COM in OpenVMS
In addition to SET HOST 0, I suggest that you investigate SPAWN/IN=NL:/OUTPUT=
SET HOST will create a complete terminal session. SUBMIT will create a batch job. Likewise, SPAWN will create a subprocess. All have slightly different semantics, one or more may be more suitable for your situation.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2010 01:14 PM
тАО10-27-2010 01:14 PM
Re: Running COM in OpenVMS
Simplest is to execute your procedure as a batch job. You can then use TYPE/TAIL/CONTINUOUS on the log file to see the output as it is generated.
$ SUBMIT ABC
$ TYPE/TAIL/CONTINUOUS ABC.LOG
Remember that output is at the DCL OUTPUT_RATE granularity, by default 30 seconds. You can change it in the executing procedure with:
$ SET OUTPUT_RATE=:0:5 ! Reduce flush interval to 5 seconds
Another option is to send your output to a shared write file. For example:
$ OPEN/WRITE/SHARE=WRITE MYLOG ABC.LOG
$ @ABC/OUTPUT=MYLOG
Now, from another process you can update the EOF mark by opening the file with append intent:
$ OPEN/APPEND/SHARE LOG ABC.LOG
$ CLOSE LOG
You can then TYPE the file up to that point. You need to reexecute the OPEN/APPEND & CLOSE each time you want to update the EOF. Same issue with OUTPUT_RATE.