HLASM Toolkit Feature libraries can reside on any currently supported
DASD.
Table 1 lists the total space required
for each type of library. The values are for a 3390 DASD.
Table 1. Total DASD space
required by HLASM Toolkit Feature
Library Type |
Total Space Required |
Target |
303 Tracks |
Distribution |
351 Tracks |
Notes:
- The data set sizes specified contain 15% extra space. You may
wish to revise these numbers based on your plans for adding additional
function or service.
- IBM® recommends use of system
determined blocksizes for efficient DASD utilization for all non-RECFM
U data sets. For RECFM U data sets, IBM recommends
a blocksize of 32760, which is the most efficient from a performance
and DASD utilization perspective.
If
you choose not to use system determined blocksizes, use the blocksizes
and numbers of blocks specified to allocate the data sets. Data sets
can be reblocked to a larger size. The maximum allowable blocksize
depends on the type of DASD on which the dataset will reside; for
example, the blocksize of datasets on a 3350 DASD cannot exceed 19,069.
- Abbreviations used for the data set type are:
- U
- Unique data set used by only the FMIDs listed. In order to determine
the correct storage needed for this data set, this table provides
all required information; no other tables (or program directories)
need to be referenced for the data set size.
- S
- Shared data set used by more than the FMIDs listed. In order
to determine the correct storage needed for this data set, the storage
size given in this table needs to be added to other tables (perhaps
in other program directories). If the data set already exists, it
must have enough free space to accommodate the storage size given
in this table.
If you currently have
a previous release of this product installed in these libraries, the
installation of this release will delete the old one and reclaim the
space used by the old release and any service that had been installed.
You can determine whether these libraries have enough space by deleting
the old release with a dummy function, compressing the libraries,
and comparing the space requirements with the free space in the libraries.
For
more information about the names and sizes of the required data sets,
please refer to
Table 4 and
Table 5.
Table 2. Storage requirements
for SMP/E work data sets
Library DDNAME |
TYPE |
ORG |
RECFM |
LRECL |
No. of 3390 Tracks |
No. of DIR Blocks |
SMPWRK1 |
S |
PDS |
FB |
80 |
30 |
80 |
SMPWRK2 |
S |
PDS |
FB |
80 |
30 |
80 |
SMPWRK3 |
S |
PDS |
FB |
80 |
180 |
80 |
SMPWRK4 |
S |
PDS |
FB |
80 |
30 |
80 |
SMPWRK6 |
S |
PDS |
FB |
80 |
30 |
80 |
SYSUT1 |
U |
SEQ |
-- |
-- |
30 |
0 |
SYSUT2 |
U |
SEQ |
-- |
-- |
30 |
0 |
SYSUT3 |
U |
SEQ |
-- |
-- |
30 |
0 |
SYSUT4 |
U |
SEQ |
-- |
-- |
30 |
0 |
Table 3 provides an estimate of the storage needed
in the SMP/E data sets for HLASM Toolkit Feature. The estimates must
be added to those of any other programs and service being installed
to determine the total additional storage requirements.
Table 3. Storage requirements
for SMP/E data sets
Library DDNAME |
TYPE |
ORG |
RECFM |
LRECL |
No. of 3390 Tracks |
No. of DIR Blocks |
SMPMTS |
S |
PDS |
FB |
80 |
30 |
5 |
SMPPTS |
S |
PDS |
FB |
80 |
30 |
5 |
SMPSCDS |
S |
PDS |
FB |
80 |
30 |
5 |
SMPSTS |
S |
PDS |
FB |
80 |
30 |
5 |
Table 4 and
Table 5 list
the target and distribution libraries and their attributes required
to install HLASM Toolkit Feature. The storage requirements of HLASM
Toolkit Feature must be added to the storage required by other programs
having data in the same library.
Table 4. Storage requirements
for HLASM Toolkit Feature target libraries
Library DDNAME |
Member Type |
Target Volume |
TYPE |
ORG |
RECFM |
LRECL |
No. of 3390 Tracks |
No. of DIR Blocks |
SASMMOD2 |
LMOD |
Any |
U |
PDS |
U |
0 |
49 |
2 |
SASMSAM2 |
EXEC SOURCE SAMPLE DATA PROC |
Any |
U |
PDS |
FB |
80 |
17 |
1 |
SASMMAC2 |
MACRO |
Any |
U |
PDS |
FB |
80 |
6 |
1 |
SASMPUT2 |
DATA |
Any |
U |
PDS |
FB |
80 |
231 |
1 |
Table 5. Storage requirements
for HLASM Toolkit Feature distribution libraries
Library DDNAME |
TYPE |
ORG |
RECFM |
LRECL |
No. of 3390 Tracks |
No. of DIR Blocks |
AASMMOD2 |
U |
PDS |
U |
0 |
97 |
73 |
AASMSAM2 |
U |
PDS |
FB |
80 |
17 |
1 |
AASMMAC2 |
U |
PDS |
FB |
80 |
6 |
1 |
AASMPUT2 |
U |
PDS |
FB |
80 |
231 |
1 |
The
user may gain access to the supplied sample JCL after the SMP/E RECEIVE
step in the install process. Alternatively, the user may copy the
sample JCL directly from the installation tape into a temporary library.
If this latter method is used then the dataset requirement is shown
in the following table.
Table 6. Storage requirements
for temporary library
Data Set Name |
TYPE |
ORG |
RECFM |
LRECL |
No. of 3390 Tracks |
No. of DIR Blocks |
JCL |
U |
SEQ |
FB |
80 |
40 |
4 |