VM/XA sites  may experience  data integrity  problems (such  as duplicate
data lines or missing "ID" card) with LISTSERV-Punch files they generate,
depending on the  way the user orders  the file: a file  ordered via mail
(for instance  because the  user does  not have NJE  access) will  not be
affected,  whereas a  BITNET  user  explicitly requesting  LISTSERV-Punch
format  via  the "F=LPUN"  keyword  is  very  likely to  experience  data
corruption.
 
This problem  is fixed  by 16E-007o and  was due to  an old  MACLIB being
erroneously GLOBAL'ed  during the assembly of  the file, back in  may 87.
The  MACLIB,  dating   from  1982,  contained  (among   other  things)  a
quick'n'dirty replacement  for the PUNCHC  macro which IBM had  broken in
some VM/370 Release 6  PUT tape. The code in question  works on VM/SP and
VM/HPO systems,  but fails under VM/XA.  Yet another notch in  your SCIDS
belt ;-)
 
Anyway, 16E-007o contains a properly assembled LSVPUNCH MODULE, and since
there is  no source code  change there  is no associated  16E-007A source
fix.
 
  Eric