- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Error when appending files on VMS
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
тАО07-06-2010 02:24 PM
тАО07-06-2010 02:24 PM
Re: Error when appending files on VMS
I have modified the script to include a set priv command and the set watch file command as well. This is attached in the text file Output.txt.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-06-2010 04:00 PM
тАО07-06-2010 04:00 PM
Re: Error when appending files on VMS
It appears that someone broke append in I64. I wonder if it is now broken in 8.4 on the Alpha? (I would expect both to use the same source code)
This test is on Alpha 8.3, and as Rob stated, it works correctly.
Suggestion, create a simple reproducer that does not rely on anything (create the files, modify the creation dates with
$ set file/attribute=(credate=1-jan) a.1 ! etc
If you can provide a simple reproducer that demonstrates the issue, you will be much more likely to get a timely fix.
See attachment for log file.
Jon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2010 07:53 AM
тАО07-08-2010 07:53 AM
Re: Error when appending files on VMS
I have been fiddling with this and I have observations:
The command $ append/log/new application_traf_anal_data:*gsm3*.dat/sin="02-jul-2010"/before="03-jul-2010" t.t
definitely does not work on the original files. I get the "%APPEND-W-NOTCMPLT" error.
If I remove the date parameters from the command, it works fine. But this is NOT what I want since the directory contains thousands of files outside the date range that is required.
Therefore as a work around, I have to copy the required files to the current working directory, append them there and then delete. That works ok but is a bit cumbersome. I can't change the creation dates of the original files because that is critical for selecting the files for the downstream system.
So there seems to be a problem with dates. Jon, I did as you suggested and changed the dates on some other files, and they were appended without a problem. So I'm a little confused. Is it really a problem with the append command or is there a problem with the creation dates on the files? How can I know?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2010 08:06 AM
тАО07-08-2010 08:06 AM
Re: Error when appending files on VMS
$copy *gsm3*.dat/sin="02-jul-2010" t.t temp.dat
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2010 08:28 AM
тАО07-08-2010 08:28 AM
Re: Error when appending files on VMS
the copy command works fine, no problems there. In fact this is what I used as part of my work around to get the required files in the current working directory before appending.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2010 08:33 AM
тАО07-08-2010 08:33 AM
Re: Error when appending files on VMS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2010 08:55 AM
тАО07-08-2010 08:55 AM
Re: Error when appending files on VMS
the copy command is a line extracted from a script which allows the user to insert the date range of the files to be extracted and appended before passing to the downstream system. The user can enter a date like 02-jul-2010 or 02-jul-2010 12:35, hence the quotes are needed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2010 08:57 AM
тАО07-08-2010 08:57 AM
Re: Error when appending files on VMS
>> I have been fiddling with this and I have observations:
Me too, withing limited time available.
1) They did not 'break' append on I64 as suggest earlier. It works in general, and it works (on my itanium ) for a much similar command using my files.
2) Append is actually done by 'copy'. I check the code and the NOTCMPLT is a catch-call error AFTER an other error happened... but that other error should have been signalled, and it is not.
3) You SET WATCH log suggest trouble accessing (opening) the first file. No read are done. It is a mystery why no error was signalled. I suspect it is something very specific in your environment but for now I am at a loss as to what. Maybe the directory file is is odd?
3A) is APPS: some sour of search list or is there a bound volume set in play?
3B) create a fresh directory and rename all files there? then give the new directory the old name?
3C) analyze / disk [ /repair ]
>> Therefore as a work around, I have to copy the required files to the current working directory, append them there and then delete. That works ok but is a bit cumbersome.
So use RENAME to simplify this some, and minimize overhead on the box and minimize failure opportunities.
Use $ RENA/SINCE ... APPS:*GSM3*.DAT *.DAX
Then $ append *.DAX
And put it back $ RENA *.DAX *.DAT
I deliberately suggest to use the same main directory, and DAX as alternative for DAT to avoid/minimize the directory entry movements.
Good luck!
Hein
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2010 09:51 AM
тАО07-08-2010 09:51 AM
Re: Error when appending files on VMS
thanks for your input here. The logical name "APPS" is actually a search list of 4 directories on 4 disks. I don't know if it significant, but all the files identified by the date criteria are actually in the first directory of the search list.
I also like your suggestion of doing a rename rather than copying the files. I tried it and it works fine.
However, I'm still bothered as to why the original script works fine on the Alpha but throws up an error on the Integrity, when both are in the same cluster.
I'm not going to put any further time into this. I have a work around that is satisfactory for my purposes. Thanks to all the experts who contributed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2010 04:30 AM
тАО07-09-2010 04:30 AM
Re: Error when appending files on VMS
Note that RENAME cannot be used when moving files between devices. (You mentioned that your files were on 4 different devices).
If all of your files are on a single device, and that is the same as your work directory, then the RENAME will work (as you seemed to indicate), however if any of the files are on other devices, then that part of the rename will fail.
(Note rename does not move any data, is simply modifies the INDEXF.SYS file (as I understand it))
Dave.