- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Strange behaviour from DCL PIPE
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
Forums
Discussions
Discussions
Discussions
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
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
03-20-2007 02:43 AM
03-20-2007 02:43 AM
Can anyone explain the following behaviour to me.
1. Create the following command procedure:
$ create a.com
$ write sys$output "This works : _TNA366:" ! use your terminal process name
$ write sys$output "This doesn't work : ''f$getjpi("","TT_PHYDEVNAM")'"
2. Execute it:
$ @a.com
This works : _TNA366:
This doesn't work : _TNA366:
3. Now, try the following PIPE command
$ pipe @a.com | search sys$input TNA366
This works : _TNA366:
Why couldn't it find the second string?
JamesP
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2007 03:03 AM
03-20-2007 03:03 AM
Re: Strange behaviour from DCL PIPE
Answer : because the process has no terminal.
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2007 03:12 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2007 03:13 AM
03-20-2007 03:13 AM
Re: Strange behaviour from DCL PIPE
pipe write sys$output f$tr("tt") | type sys$input
FTA14:
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2007 03:31 AM
03-20-2007 03:31 AM
Re: Strange behaviour from DCL PIPE
Why didn't I think of that?
Cheers guys
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2007 08:46 PM
03-20-2007 08:46 PM
Re: Strange behaviour from DCL PIPE
first,
WELCOME to the VMS forum!
please review
http://forums1.itrc.hp.com/service/forums/helptips.do?#33
to thank those that helped
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2007 09:40 PM
03-20-2007 09:40 PM
Re: Strange behaviour from DCL PIPE
$ write sys$output "This works : _TNA366:" ! use your terminal process name
$ pid = F$Getjpi("","MASTER_PID")
$ write sys$output "This doesn't work : ''f$getjpi(PID,"TT_PHYDEVNAM")'"
regards Kalle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2007 11:38 PM
03-20-2007 11:38 PM
Re: Strange behaviour from DCL PIPE
Thanks