- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Unexpected TPU behaviour.
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
тАО04-19-2006 12:49 AM
тАО04-19-2006 12:49 AM
Unexpected TPU behaviour.
A logical A is defined as a searchlist:
A = disk1[a], disk2[b]
file A:X.X does not exist at all.
Interactively $ edit/tpu a:x.x should create this file as disk1:[A]X.X, since that is the first directory in the list; and it does.
In an interactive program however where TPU$EDIT is called with A:X.X as the file to edit/create, the file is created as disk2:[B}X.X - so on the SECOND directory.
Not exactly what is expected.
I could imagine that TPU$EDIT would search for the file and when not found, create the file in the last directory searched.
Is this a bug, or a feature?
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-19-2006 12:51 AM
тАО04-19-2006 12:51 AM
Re: Unexpected TPU behaviour.
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-19-2006 01:39 AM
тАО04-19-2006 01:39 AM
Re: Unexpected TPU behaviour.
I've used the simple TPU$EDIT example from chapter 8.2 of the utility routines manual and cannot confirm the behaviour described in your post.
TPU$EDIT uses 2 parameters, I've specified them both as A:X.X and defined a logical A as disk1:
When I execute the example program, it writes the A:X.X output file into the first directory pointed to by the A logical.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-19-2006 01:50 AM
тАО04-19-2006 01:50 AM
Re: Unexpected TPU behaviour.
Could you give the exact syntax of the call to TPU$EDIT. TPU$EDIT requires 2 arguments: the input file & the output file.
Regards,
Kris (aka Qkcl)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-19-2006 02:02 AM
тАО04-19-2006 02:02 AM
Re: Unexpected TPU behaviour.
Just tried to write a reproducer ( in C ).
But it doesn't do what you describe.
I've defined ADIR as "HOME$ROOT:[TMP35],HOME$ROOT:[TMP36]", and the input argument to TPU$EDIT is specified as ADIR:X.X, the length output argument is set to 0. The X.X file is created in the [TMP35] directory (as expected).
Regards,
Kris (aka Qkcl)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-19-2006 07:45 AM
тАО04-19-2006 07:45 AM
Re: Unexpected TPU behaviour.
result = tpu$edit(bestand||"/SECTION = EXE:RBS.TPU$SECTION");
I will ask my collegue what's in the section file, since the outputfile (the second parameter) seems empty, I guess the source of the problem is in there.
(kept on hold)
OpenVMS Developer & System Manager