[an error occurred while processing this directive]

HP OpenVMS Systems

ask the wizard
Content starts here

TCP/IP FTP file attribute or record changes?

» close window

The Question is:

 
Hello -
 
I have been trying to reconstruct the system accounting
file - sys$manager:accountng.dat. I just got done
creating a new system accounting file thru the
$ set accounting/new_file command in order to
save space. I ftp'd the old accountng.dat file
to my pc using ms's ftp and ftping the file as
a binary. When I brought it back however, the
organization of the file changed from variable
length 215 byte recs to fixed length 512 byte
records. I tried to first run accounting on this
file without success; next I ran analyze/rms/fdl,
create/fdl, and convert to try to copy it back
into the 215 var length format. The 512 length
records were too long and generated informatory
messages causing no records to be written and
converted. Do you have any ideas on what I might
do to resolve this problem?
 
Thank you -
 
Steve
 
 


The Answer is :

 
  Without specific information on the products and versions involved,
  and without information on the specific corruptions involved, this
  question is difficult to answer.
 
  You will need to determine what IP package is in use and if there
  is any update that might be of interest here.  If this is the TCP/IP
  Services for OpenVMS (UCX) package, you will want to determine the
  version and look for applicable ECOs.  You will also want to look
  for any ECOs to FTP support on the PC system, as well.
 
  The resolution might be as simple as a SET FILE/ATTRIBUTES command
  with the correct file attribute settings, or it might involve using
  tools to unload and reload the data in the file.
 
  Also please see the previous discussions of "FTP file transfers and
  file formats?" and "BACKUP savesets corrupted via TCP/IP (UCX) FTP?",
  available via the search engine.
 
  And all this assumes that you cannot restore the file from BACKUP.
  Given this entire discussion, it would appear that the local BACKUP
  schedule needs reevaluation.

answer written or last revised on ( 26-OCT-1998 )

» close window