DASD Storage Requirements - 2.1

Ironstream libraries can reside on all supported DASD types. The table given below lists the total amount space initially allocated for each type of library.

Notes:

• The installation jobs follow the IBM recommendation of using system-determined block sizes for efficient DASD utilization for all non-RECFM U data sets. For RECFM U data sets, IBM recommends a block size of 27998 (half track blocking on a 3390 type device), which is the most efficient from a performance and DASD utilization perspective.

• Some NMC SMP/E managed data sets may be empty after the SMP/E process is complete. This is because Ironstream does not exploit all their available features in Ironstream v2.1.
• All target and distribution libraries listed have the following attributes:

  • The default name of the data set may be changed.
  • The default block size of the data set may be changed.
  • The data set may be merged with another data set that has equivalent characteristics.
  • The data set may be either a PDS or a PDSE.
• All target libraries listed have the following attributes:

  • The data set may be SMS-managed.
  • It is not required for the data set to be SMS-managed.
  • It is not required for the data set to reside on the IPL volume.
• SSDFAUTH must be APF-authorized. Do not add SSDFAUTH to the LPA or the LINKLIST. Always use JOBLIB or STEPLIB in all started tasks or batch jobs that access SSDFAUTH.

The following tables describe the distribution and target libraries, and ZFS paths required to install Ironstream v2.1 The storage requirements of Ironstream must be added to the storage required by other programs having data in the same library or path.

The table given below shows the distribution data set attributes and sizes. Note that the libraries are assumed to be PDS/E.

The table given below shows the target data set attributes and sizes. Note that the libraries are assumed to be PDS/E.