SMPTLIB

ddname

SMPTLIB.

Use

SMPTLIB data sets (TLIBs) are used as temporary storage for relative files that are loaded from SMPPTFIN during RECEIVE processing. They are deleted when the associated SYSMOD is deleted by REJECT, RESTORE, or ACCEPT processing.

You can have SMP/E dynamically allocate the TLIB data sets, or you can allocate them yourself before RECEIVE processing. For information about how SMP/E allocates the TLIBs, see the RECEIVE Command topic in SMP/E for z/OS Commands. (Regardless of how the SMPTLIB data sets are allocated, they do not appear in the File Allocation report.)

Note:

No DD statement or DDDEF entry is required for the SMPTLIB data sets if they are preallocated and cataloged.
If you allocate and catalog the SMPTLIB data sets yourself, make sure they are allocated on the volume specified in the catalog.
If you allocate the SMPTLIB data sets yourself but do not catalog them, make sure they are allocated on the volume specified in the SMPTLIB DD statement or DDDEF entry being used for the command you are processing.
If you need to specify a unit that is not SYSALLDA, and the unit is not set by use of a STORCLAS or an ACS filter routine, then you must use a DDDEF entry instead of a DD statement to allocate SMPTLIB data sets and specify the unit value in the DDDEF entry.
If you are using SMS to manage your data sets, you can set up the unit, volume, and space allocation through a STORCLAS or an ACS filter routine, instead of specifying them on a DD statement or DDDEF entry.
If you are using SMS to manage your data sets, do not specify dummy volumes on a DD statement or in a DDDEF entry for the SMPTLIB allocation. Dummy volumes used as indicators to ACS routines for SMS class selection can cause operator mount messages to be issued for the non-existent dummy volumes. This is because SMP/E first attempts to allocate the SMPTLIB data sets as if they already exist on the volume, which can cause operator mount messages to be issued for the dummy volume.
SMPTLIB data sets should not be allocated as PDSEs, because IEBCOPY does not support copying an unloaded PDS load library from tape to a PDSE load library on DASD.
DDDEFs are not required in target or distribution zones for SMPTLIB data sets, unless you have uncataloged the SMPTLIB data sets from the global zone (this is not recommended). In this case, only the VOLUME and UNIT subentries are accepted as input on UCLIN statements for target or distribution zone SMPTLIB DDDEFs.

Attributes

Partitioned.

Here are two examples of SMPTLIB DD statements:

/SMPTLIB DD UNIT=SYSALLDA,VOL=SER=SMPVOL

//SMPTLIB DD UNIT=SYSALLDA,
//           VOL=SER=(SMPVL1,SMPVL2)

If you use DDDEFs to have SMP/E dynamically allocate the SMPTLIB data sets, you cannot specify the initial or final disposition. SMP/E determines the disposition based on the command it is processing.

Device

Direct access only.