In most instances like this, I would use the #pragma exception handler.
I don't think I have ever had an instance on the native side where the i
has left a file open when an exception exit passed the PEP. Are you
Save files are not physical file file objects. They are device files and
require correct synchronization. Is there a chance that one or more of
the records are being written out of sequence?
> The problem occurs on a client system running V5R4 and it is
> The message does not specify the record in error just that it
> problem. I have come across this in the past, basically I am writing 528
> byte records to the save file, after 32K the OS goes out and does a CRC
> check against the data just written, if it is incorrect then it
> CPF5175 error but does not let the _Rwrite function know about it through
> the fdbk structure (the writes have already been made!) It does however
> cause the program to end abnormally and it was leaving the file open,
> have managed to fix that. All I want to do is be able to capture the
> message and react to it, so I am hoping a #pragma exception Handler
> the best option? The TCP/IP issues keep piling up on the V5R4 boxes
> all works fine on my V6R1 boxes and others?? I am hoping this has
> to do with the rebuilding of the programs when copied to V5R4 as I am
> building them on a V6R1 system back level'd to V5R4???
> Chris Hird
> Shield Advanced Solutions Ltd
> 1(519) 940-1192
> Please consider the environment before printing this email.
> This message, including any attached documents, is intended for the
> addressees only. It may contain information that is confidential,
> and/or exempt from disclosure. No rights to privilege or confidentiality
> have been waived. Any unauthorized use or disclosure is prohibited.
> have received this message in error, please reply to the sender by e-mail
> and delete or destroy all copies of this message.
> Avant d'imprimer ce courriel, pensez à l'environnement.
> Ce message, incluant tous les documents joints, est à l'intention des
> destinataires visés seulement. Il peut contenir des renseignements
> confidentiels, protégés et/ou ne pouvant pas être divulgués. Aucune
> renonciation n'est faite quant à sa nature confidentielle et privilégiée.
> Par conséquent, toute diffusion ou utilisation non autorisée est
> interdite. Si vous avez reçu ce message par erreur, veuillez en aviser
> immédiatement l'expéditeur par retour de courriel et en détruire
> copies existantes.