Operating System - OpenVMS
1748183 Members
3463 Online
108759 Solutions
New Discussion юеВ

Error when appending files on VMS

 
SOLVED
Go to solution
RobCox
Advisor

Error when appending files on VMS

I have encountered an issue when appending some files as follows:

$ append/log/new apps:*gsm3*.dat t.t

This works fine. But if I add dates such as

$ append/log/new apps:*gsm3*.dat/sin="02-jul-2010" t.t


I get the following error:

%APPEND-W-NOTCMPLT, APPS:*GSM3*.DAT; not completely copied

I don't understand why adding a date range would cause an issue with the file 'not completely copied'
Any ideas would be appreciated.

Thanks.
24 REPLIES 24
RBrown_1
Trusted Contributor

Re: Error when appending files on VMS


I don't see this behaviour with VMS 7.1 on Alpha, but here is a guess.

Does the /SINCE exclude any files of GSM3*.DAT? Do you still get the same message if the /SINCE *DOES NOT* exclude any files?
Hein van den Heuvel
Honored Contributor

Re: Error when appending files on VMS

Rob,

Are you not getting much more error messages?
Perhaps the specific file, and for example an RMS-F-RSZ message?

By using the /NEW you are trusting the FIRST file selected to define the characteristics for the output. That causes uncontrolled, random behaviour.

The first, old file may have say 80 byte records.
The next, more recent file file might have a small maximum record size, say 50.
And the next also recent file might have records of 60 bytes.

Without the /SINCE, the MRS for the output will be 80 (or more) and all other files will happily play along.

With the /SINCE the MRS might be that 50 bytes, and the 3rd file would fail to deliver its longed records: Partially copied.

My preferred solution would be to control the randomness by using

$ CREATE t.t
$ append/log/NOnew/since apps:*gsm3*.dat t.t

Cheers,
Hein


$ copy tmp.exe tmp.tmp
$ app/log %.tmp tmp.tmp
%APPEND-W-INCOMPAT, C.TMP;1 (input) and TMP.TMP;1 (output) have in
compatible attributes
%APPEND-E-WRITEERR, error writing TMP.TMP;1
-RMS-F-RSZ, invalid record size
%APPEND-W-NOTCMPLT, C.TMP;1 not completely copied
%APPEND-W-NOTCMPLT, %.TMP; not completely copied
RobCox
Advisor

Re: Error when appending files on VMS

RBrown,
you are correct. The problem does not manifest itself on the Alpha and we have V 8.3 I have just confirmed that.
However we have just commissioned some new Integrity servers and this is where the problem is occurring. I can't see why the same script will error out on one server but not the other, when processing the same files.

I believe the files may have different attributes but are all sequential text files.

Hein,
this is the only error message displayed - no further information. I just tried your suggestion of $create t.t and got the same error.
Hein van den Heuvel
Honored Contributor

Re: Error when appending files on VMS

It is difficult to see you would get only the final message.
What about the /LOG data lines?

It this a typed command, or a spawn or scripts?

What about the resulting file?
Did it copy all records or partial as warned?
What's missing?

What files are selected, which not? (again /LOG)
If you change the /SINCE to /SINCE=1-jan-1900, that is to include all files, then does it work again?

I'd be tempted to grab CMKRNL privs and add a SET WATCH FILE/CLASS=MAJOR just before the APPEND. Check the read and write stats per file. IF you decide to share that output, then please append as a text file, and toss in some $ DIRECTORY /DATE=(CRE, MOD) output for the relevant files.

( to stop SET WATC FILE/CLASS=NONE )

btw, my example failure was produced on OpenVMS Alpha 8.3.

hth,
Hein.
RobCox
Advisor

Re: Error when appending files on VMS

Ok please find the full text below:

Node MNID03 is an Integrity server
MNID03 >set ver
MNID03 >@t
$ set def traf_anal_extract:[000000]
$ append/log/new application_traf_anal_data:*gsm3*.dat/sin="02-jul-2010" -
/before="03-jul-2010" t.t
%APPEND-W-NOTCMPLT, APP_TRAF_DAT:[TRAF_ANAL_DATA1]*GSM3*.DAT; not completely copied
$ exit
MNID03 >




Here's the same script, executed on the Alpha
MNID01
MNID01 >@t
$ set def traf_anal_extract:[000000]
$ append/log/new application_traf_anal_data:*gsm3*.dat/sin="02-jul-2010" -
/before="03-jul-2010" t.t
%APPEND-W-INCOMPAT, APP_TRAF_DAT:[TRAF_ANAL_DATA1]MST_TRAF_ANAL_GSM3_00123089.DAT;1 (input) and TRAF_ANAL_EXTRACT:[000000]T.T;3 (out
put) have incompatible attributes
%APPEND-S-APPENDED, APP_TRAF_DAT:[TRAF_ANAL_DATA1]MST_TRAF_ANAL_GSM3_00123089.DAT;1 appended to TRAF_ANAL_EXTRACT:[000000]T.T;3 (615
records)
%APPEND-S-APPENDED, APP_TRAF_DAT:[TRAF_ANAL_DATA1]MST_TRAF_ANAL_GSM3_00123090.DAT;1 appended to TRAF_ANAL_EXTRACT:[000000]T.T;3 (661
records)
%APPEND-S-APPENDED, APP_TRAF_DAT:[TRAF_ANAL_DATA1]MST_TRAF_ANAL_GSM3_00123091.DAT;1 appended to TRAF_ANAL_EXTRACT:[000000]T.T;3 (714
records)
%APPEND-S-APPENDED, APP_TRAF_DAT:[TRAF_ANAL_DATA1]MST_TRAF_ANAL_GSM3_00123092.DAT;1 appended to TRAF_ANAL_EXTRACT:[000000]T.T;3 (732
records)
%APPEND-S-APPENDED, APP_TRAF_DAT:[TRAF_ANAL_DATA1]MST_TRAF_ANAL_GSM3_00123093.DAT;1 appended to TRAF_ANAL_EXTRACT:[000000]T.T;3 (627
records)
%APPEND-S-APPENDED, APP_TRAF_DAT:[TRAF_ANAL_DATA1]MST_TRAF_ANAL_GSM3_00123094.DAT;1 appended to TRAF_ANAL_EXTRACT:[000000]T.T;3 (519
records)
%APPEND-S-APPENDED, APP_TRAF_DAT:[TRAF_ANAL_DATA1]MST_TRAF_ANAL_GSM3_00123095.DAT;1 appended to TRAF_ANAL_EXTRACT:[000000]T.T;3 (412
records)
%APPEND-S-APPENDED, APP_TRAF_DAT:[TRAF_ANAL_DATA1]MST_TRAF_ANAL_GSM3_00123096.DAT;1 appended to TRAF_ANAL_EXTRACT:[000000]T.T;3 (60
records)
$ exit
MNID01 >

My issue is, why does it work on the Alpha, but not the Integrity?

Hein van den Heuvel
Honored Contributor

Re: Error when appending files on VMS

And that's a cluster, so you are looking at the very same files huh?

I'm reluctantly starting to think this may be an interesting problem after all. I'll give it a second whirl in my copious spare time (later, ,much later)

You may want to move forward with SET WATCH FILE.
In you place I would also want to know what the reported attribute mismatch is.
Maybe the Itanium code reacts differently (wrongly) to that.
Check with DIR/FULL on T.T; and on the first file to report a mismatch.
Also, remove T.T and copy that first file as T.T to see whether that changes anything.

Later,
Hein
NEL - URU : 3 - 2. Oranje Boven!



RobCox
Advisor

Re: Error when appending files on VMS

Ok I have done a couple things here:

1) here's what a dir/full of t.t looks like
MNID01 >dir/full t.t;3

Directory TRAF_ANAL_EXTRACT:[000000]

T.T;3 File ID: (269149,2489,0)
Size: 4001/4356 Owner: [COX_R]
Created: 6-JUL-2010 13:31:02.23
Revised: 6-JUL-2010 16:45:11.40 (3)
Expires:
Backup:
Effective:
Recording:
Accessed:
Attributes:
Modified:
Linkcount: 1
File organization: Sequential
Shelved state: Online
Caching attribute: Writethrough
File attributes: Allocation: 4356, Extend: 0, Global buffer count: 0, No version limit
Record format: Variable length, maximum 0 bytes, longest 233 bytes
Record attributes: Carriage return carriage control
RMS attributes: None
Journaling enabled: None
File protection: System:RWED, Owner:RWED, Group:RE, World:
Access Cntrl List: None
Client attributes: None

Total of 1 file, 4001/4356 blocks.
MNID01 >

Secondly, I did as you suggested and copied the first file as t.t. When run on the Alpha, no warnings about compatible attributes were displayed. However on the Integrity, I get the same error as before. Nothing changed there.

Thirdly, yes these machines are in a cluster. The Alpha will be phased out shortly.

Can you explain the 'set watch file' command. I've never used that.
Hein van den Heuvel
Honored Contributor

Re: Error when appending files on VMS

>> Can you explain the 'set watch file' command. I've never used that.

See my earlier reply, or GOOGLE: +"set watch" +openvms

Looks like the incompatible attributes are benin in your case. So they can be ignored. For yourwon sake I;d check the attributes on the new t.t, but is is probably stream-lf or VFC versus VAR. No biggie

Hein
Hoff
Honored Contributor

Re: Error when appending files on VMS

"OpenVMS Tips: Troubleshooting File System Access Errors"

http://labs.hoffmanlabs.com/node/217

Includes information on SET WATCH, as well as using security mechanisms.

And Google can be a good friend here, too. You'll find a variety of discussions of this topic and related topics with the search string /OpenVMS set watch/ or analogous.