II08224: JES3 AND DATA SET INTEGRITY

APAR status

• Closed as canceled.

Error description

• The only way to provide data set integrity across multiple MVS
  systems in a JES3 complex is through managing the SYSDSN
  enqueue by GRS or an equivalent product.
  There are two exposures in using JES3 to provide data set
  integrity throughout the JES3 complex.  They are:
      New Generations of Generation Data Groups
      -----------------------------------------
      One job creates a new generation; JES3 only knows about the
      relative name (for example BASENAME (+1)); another job
      later allocates the same data set by specifying its fully
      qualified data set name (for example BASENAME.GxxxxVyy).
      To maintain integrity, it would be necessary to ensure that
      the two jobs do not access the data set concurrently.
      New Non-Specific Non-Private DASD Requests for Non-SMS
      ------------------------------------------------------
      Managed Data Sets
      -----------------
      JES3 does not provide data set integrity for new
      non-specific non-private requests for non-SMS managed
      DASD data sets.  These requests either omit the VOLUME
      parameter, or have a VOLUME parameter which does not
      contain the SER, REF, or PRIVATE subparameter.
  Although there has been some code added to DEFRAG and to DFHSM
  PARTIAL RELEASE (see APAR OW07976) to not manage any data set
  less than one day old in a JES3 environment, you are still
  exposed if the step that creates the data set runs longer than
  one day.  Furthermore, any other products that depend upon
  allocation of a data set to insure exclusive control of the
  data will not be protected from these two exposures.  An
  example of this would be DFDSS volume dumping or potentially
  any OEM products that move or manage data sets.
  However, managing data set integrity by GRS or an equivalent
  product does not necessarily mean that you do not want JES3 to
  manage the data set resources of batch jobs.  Benefits of JES3
  data set management are still potentially required to prevent
  scheduling of workload that would interlock while on the MVS
  initiators.
  Also, note that there are combinations of JES3 initialization
  stream parameters and JCL parameters that specifically request
  JES3 not to do data set integrity processing.  Examples of
  these are SETUP=NONE on the STANDARDS JES3 initialization
  statement, SMSSETUP=NO on the SETPARAM JES3 initialization
  statement, specifying a non-JES3 managed unit name (explicitly
  in the job's JCL, or implicitly through information obtained
  from the catalog), etc.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• info apar
  

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