Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
ALLOCATE z/OS DFSMS Access Method Services Commands SC23-6846-01 |
|
Access method services identifies the verb name ALLOCATE and attaches the terminal monitor program (TMP) that runs Time Sharing Option (TSO) commands in the background. The ALLOCATE command should be used only to allocate new data sets to the job step. If you use ALLOCATE through access method services for anything else (the handling of SYSOUT data sets, for example), you can get unpredictable results. Refer to z/OS TSO/E Programming Guide for additional information on using this command. Table 1 separates the parameters to that you should use under access method services from the parameters that cause unpredictable results. When ALLOCATE is used, the data set is allocated to the job step. If your job contains multiple allocations, you might need to use the DYNAMNBR parameter on the job control language (JCL) EXEC statement. DYNAMNBR establishes a control limit used by TMP when allocating a data set. The control limit is the number of data definition (DD) statements that are coded plus the value coded in DYNAMNBR. If you do not use DYNAMNBR, the system sets it to 0 (the default). If you code DYNAMNBR incorrectly, the system uses the default and issues a JCL warning message. See z/OS MVS JCL User's Guide for a description of how to code the DYNAMNBR parameter. For an example illustrating the use of DYNAMNBR, see Allocate a Data Set Using SMS Class Specifications: Example 1. When you use the ALLOCATE command within access method services,
you must follow the data set naming conventions of TSO when the TMP
is run in batch mode. That is:
You can use the ALLOCATE command to define data set attributes
in several ways:
|
Copyright IBM Corporation 1990, 2014
|