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

Just my $.02 worth - Seems that this is a common situation. No right or
wrong here. There's always a negotiation at the design stage between
disparate systems, as to who's 'in charge'. I was in a situation once to
make the 400 the controlling box in a project that had data uploaded from
an ATT voice reponse box to a customer service app on the 400. I was able
to justify the 400 starting the process (my preference, but I'm an admitted
400 bigot <g>), but this will not always be the case.

At 09:13 AM 3/18/02 -0500, you wrote:
>Tom said:
>
> >Seems unusual that the sending site controls
> >the names, but there always seems to be
> >restrictions whatever we do.
>
>I live with this every day.  Telephone switches do an ftp 'put' to the IFS
>every hour or so, and the switch controls the generation of the file name
>they send.  Not really Syd's situation, but I thought I'd  share a real
>world scenario.
>
>We control 'inadvertent collisions' with security (the ftp user profile is
>authorised to nothing but the specific IFS directory they want) although the
>switch-generated names are very unlikely to clash with QSYS.LIB names.
>   --buck
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.