Re: system event trigger whenever a source file member is updated

[Dr Syd Nicholson <sydnic@xxxxxxxxxx>]

No problem with knowing when update is complete. The last record in the
member will have a specific identifier. When this record is received the
upload is complete.

The exit program will tell me an upload has been requested. I will need
to monitor for completion, or inform the operator that an error has occured.

The 'user' sending the data is another computer program. It cannot be
changed. There will be only one file member for each upload.

Syd Nicholson


rob@dekko.com wrote:

>The problem with the exit point is that it is a before.  It was designed as
>a security measure.  For example if you process the event it will be like
>the following
>Client:  May I send you this file?
>Server:  Yes.  Let me post the data.  Done.  Ok, now start sending.
>Client:  Sending data
>Done.
>
>See you're posting the data prior to receipt.  There are a few tricks
>around this.
>1)  Submit a job from the exit point.  Put a delay in this job sufficient
>enough to wait until the data is received.  Or do other things like a small
>delay and then an existence and lock check.
>2)  Have the user send you two files.  Trigger your process off of the
>second file.
>
>Our partners do the remote command.  Except for one.  He was running AIX
>and claimed that he could not get the QUOTE RCMD to work.  We used the
>dummy second file with them.
>
>Rob Berendt
>