PI53324: COUNT OF JES FILES RETURNED BY FTP MAY NOT BE ACCURATE

APAR status

• Closed as fixed if next.

Error description

• .
  An FTP session is connected to the z/OS server with
  FILETYPE=JES.  During periods of high workloads on the system
  (or the JES subsystem), it is possible that the job status
  (returned by a DIR command) will show the status as OUTPUT but
  the count of spool files will be smaller than it should be (due
  to more files being added).  This is especially a problem for
  automated clients that use the returned output to drive later
  processing.
  

Local fix

• .
  Change any automated scripts to add a delay between when the
  job's status changes to OUTPUT and the use of the count of the
  number of associated spool files.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of the IBM Communications Server                   *
  * for z/OS Version 2 Release 1 and Version 2                   *
  * Release 2: FTP JES                                           *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Count of JES files does not list all of the datasets         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * FIN                                                          *
  ****************************************************************
  The problem may be summarized as follows:
  When an FTP session is connected to the z/OS server with
  FILETYPE=JES, LIST/NLST processing to display the status of a
  job counts only the datasets that are accessible for processing
  at that point in time. If a dataset is marked busy for any
  reason (say another application is touching it, or some other
  JES2 operation is taking place against the dataset), that
  dataset will not be counted.
  
  This FIN APAR was taken to fix LIST/NLST processing to count all
  the dataset regardless of their availability to be processed.
  

Problem conclusion

Temporary fix

Comments

• The solution for this APAR is included in CS for zOS Version 2
  Release 3.
  
  This APAR is being closed FIN (Fixed If Next) with concurrence
  
  from the submitting customer. This means that a fix to this
  
  APAR is expected to be delivered from IBM in a release (if any)
  
  to be available within the next 36 months.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R210 PSN

     UP

• R220 PSN

     UP