The AFD FAVE protocol has been changed in 1.5m to the following (there is no
change to what is done at 'AFD ADD' time, only at actual AFD distribution):
 
  Before any AFD takes place, the FAVE is called with a reqtype of AFDTIME and
  an originator  of 'SYSTEM'  (as a  placeholder). It may  either Exit  '', in
  which  case no  AFD takes  place at  all  and a  message is  printed on  the
  console, or provide the following return arguments:
 
          (Exit/Return) ckfac callme usedist fn ft fm ignored
 
  * 'ckfac'  is a  boolean indicating  whether the  GET FAC  is to  be checked
    against each  originator before  the AFD  takes place.  The default  is 0,
    which is ok for vanilla files because the FAC is checked when you AFD ADD.
    Well, there are cases where you might wish to set it to 1.
 
  * 'callme' is  a boolean indicating  whether the FAVE  is to be  called with
    GET1/GET2 reqtypes. The default is 0,  which means the FAVE does not alter
    the contents of the file, nor  does it perform additional verifications on
    the originator. Specifying  a 1 causes the AFD to  perform (almost) like a
    GET command from the user, with the  exception that the FAC check might be
    waived if  the previous  flag was set  to 0. See  next paragraph  for more
    details.
 
  * 'usedist' is a boolean indicating whether  DISTRIBUTE can be used when the
    prologtext is set  to '' or not. The  default is 1 when there  is no FAVE,
    and 0 if there is a FAVE. With  'usedist' set to 0, the FAVE can alter the
    contents of  the file and produce  a different file for  each recipient in
    the AFD list, and DISTRIBUTE can therefore not be used. With 'usedist' set
    to 1, the FAVE guarantees that the  file contents will be the same for all
    recipients  (ie it's  only going  to perform  additional checks  to decide
    whether the recipient is allowed to receive a copy or not), and it accepts
    not to receive any reqtype=GET2 call (only the GET1's will be done).
 
  * 'fn  ft fm'  are  optional and,  if  specified, must  be  all there.  They
    indicate the  actual fileid of the  file and are meaningless  if 'usedist'
    has been set to  0, since this info will then have to  be specified on the
    GET1 return parameters for each user.
 
  * 'ignored' is reserved for future use and presently discarded.
 
Who is interested in beta-testing this new protocol and/or commenting on
anything which might still be missing?
 
  Eric