FCOPY FROM=msgfile;TO=newfile;NEW;SUBSET=,0
will create an empty file with the same structure and copy the user
labels.
Add ;COPYACD to copy the ACDs--this gives a warning if there is no ACD
----- Original Message -----
From: <[log in to unmask]>
To: <[log in to unmask]>
Sent: Wednesday, September 20, 2000 2:51 PM
Subject: Cloning files
> Hi all,
> I wrote :
> >>Would anyone know of a utility/easy-method which will
> >>allow you to build a clone of an existing file (esp message files)
> >>but without touching the data ?
>
> Perhaps I should elaborate on the requirements.
> Let us say the machine has crashed, and you
> have about 2000 message files in about 10 different accounts
> which are in a suspect state,
> and I want to rebuild them all as part of the system recovery process,
> before any applications have a chance to get tied up in knots with a bad
file.
> (today was a bad day :( )
>
> So, I want a job which logs as MANAGER.SYS and starts off with,
>
> main.pub.vesoft "listf @[log in to unmask]@(ismsg),6" > ipcfiles
>
> and then for each file,
> reconstruct the ;REC= , ;DISC=, ;CODE= , ;ULABEL=
> and also possibly an ACD if there is one.
> Then, issue a BUILD command followed by an ALTSEC
> and then change the CREATOR to what it was originally.
>
>
> Now, problems encountered in the past,
>
> 1. COPY, as often as not copies the file with the corruption,
> so that the copied file is just as bad as the original.
>
> 2. Just erasing them with purge;save (is/has been) good, but not always
> successful.
> A file message file corruption is not necessarily cleared.
>
> 3. Testing if the file is damaged is difficult. (We had one file
> which showed eof=30, but an attempted read behaved as if the
> file was empty, without generating an fserror.
> We also had another file with EOF= -1, and a program reading it
> as its stdin lost its way because it cannot distinguish a timeout
> from any other error on stdin via FCHECK(0). )
>
> The above, and many other various symptoms have made it quite clear
> that after a system crash, message files must be purged and re-built.
> I believe the manuals on IPC strongly imply this as well.
>
>
> Regards,
> Tad.
>
>
>
>
>
> ___________________________________________________________
>
> This message and any attachments (the "message") are intended solely for
> the addressees and are confidential. If you receive this message in
error,
> please delete it and immediately notify the sender.
>
> Any use not in accord with its purpose, any dissemination or disclosure,
> either whole or partial, is prohibited except formal approval.
>
> The internet can not guarantee the integrity of this message. BNP PARIBAS
> (and its subsidiaries) shall (will) not therefore be liable for the
message
> if modified.
> --------------------------------------------------
> Ce message et toutes les pieces jointes (ci-apres le "message") sont
> etablis a l'intention exclusive de ses destinataires et sint
confidentiels.
> Si vous recevez ce message par erreur, merci de le detruire et d'en
avertir
> immediatement l'expediteur.
>
> Toute utilisation de ce message non conforme a sa destination, toute
> diffusion ou toute publication, totale ou partielle, est interdite, sauf
> autorisation expresse.
>
> L'internet ne permettant pas d'assurer l'integrite de ce message, BNP
> PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce
> message, dans l'hypothese ou il aurait ete modifie.
> ___________________________________________________________
>
|
