High Level Assembler 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 High Level AssemblerLibrary Type |
Total Space Required |
---|
Target |
72 Tracks |
Distribution |
76 Tracks |
Table 2 gives an estimate of the storage
requirements for SMP/E work data sets, for High Level Assembler.
Table 2. Storage requirements
for SMP/E work data setsLibrary DDNAME |
T
Y
P
E
|
O
R
G
|
R
E
C
F
M
|
L
R
E
C
L
|
No.
of
3390
Trks
|
No.
of
DIR
Blks
|
---|
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 |
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.
- 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,
refer to Table 4 and Table 5.
Table 3 provides an estimate of the
storage needed in the SMP/E data sets for High Level Assembler. 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 setsLibrary DDNAME |
T Y P E |
O R G |
R E C F M |
L R E C L |
No. of 3390 Trks |
No. of DIR Blks |
---|
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 High Level Assembler. The storage requirements of High
Level Assembler must be added to the storage required by other programs
having data in the same library.
Table 4. Storage requirements
for High Level Assembler target librariesLibrary DDNAME |
Member Type |
Target Volume |
T Y P E |
O R G |
R E C F M |
L R E C L |
No. of 3390 Trks |
No. of DIR Blks |
---|
SASMMOD1 |
LMOD |
ANY |
U |
PDS |
U |
0 |
16 |
3 |
SASMSAM1 |
SAMPLES PROCS |
ANY |
U |
PDS |
FB |
80 |
36 |
2 |
SASMMAC1 |
MACRO |
ANY |
U |
PDS |
FB |
80 |
20 |
1 |
Table 5. Storage requirements
for High Level Assembler distribution librariesLibrary
DDNAME |
T Y P E |
O R G |
R E C F M |
L R E C L |
No. of 3390 Trks |
No. of DIR Blks |
---|
AASMMOD1 |
U |
PDS |
U |
0 |
24 |
14 |
AASMSAM1 |
U |
PDS |
FB |
80 |
32 |
2 |
AASMMAC1 |
U |
PDS |
FB |
80 |
20 |
1 |
You can access the supplied sample JCL after the
SMP/E RECEIVE step in the install process. Alternatively, you can
copy the sample JCL directly from the installation tape into a temporary
library. If you use this method, use the data set requirements shown
in Table 6.
Table 6. Storage requirements
for temporary libraryData Set Name |
T Y P E |
O R G |
R E C F M |
L R E C L |
No. of 3390 Trks |
No. of DIR Blks |
---|
JCL |
U |
SEQ |
FB |
80 |
30 |
4 |