Required/Optional Statement |
Optional |
Statement Default |
None |
Placement in Initialization Stream |
DYNALLOC statements, if used, must be placed
first in the JES3 initialization stream. |
Coding Considerations |
- The DYNALLOC statement must begin in column 1; it cannot be continued, nor can comments be embedded.
- All parameters pertaining to a DYNALLOC statement must be defined
on one statement; continuation statements are not permitted.
- The maximum number of DYNALLOC initialization statements
is 1635 minus the number of DD statements in the JES3 start procedure.
- If a dynamically allocated data set or device is inaccessible
to a main in the JES3 complex, operator intervention will be required
during JES3 initialization.
- You cannot dynamically allocate dummy data sets or data sets defined
by the ddnames:
- The JES3 global processor will dynamically allocate
all of the DD's specified on the DYNALLOC statement.
Only a subset
of the DD's specified on DYNALLOC statement will be dynamically allocated
by the JES3 local processors. The following is a list of the DD's
that will be dynamically allocated if they appear on a DYNALLOC statement: - DD's for spool data sets
- JES3JCT
- JES3OUT
- JESABEND
- SYSABEND
- SYSUDUMP
The following DD's will not be dynamically allocated
by the local processors if they appear on a DYNALLOC statement. Note
that if a local processor becomes the global processor through a Dynamic
System Interchange (DSI), the DD's will be dynamically allocated: - IATPLBxx
- JES3DRDS
- JES3SNAP
- Any user DD's
- DYNALLOC statements cannot appear in a member specified
using the INCLUDE statement.
|
Security Usage |
None |
Performance Considerations |
None |
Initialization Stream Overrides |
None |
Restart or Command Modification |
Cold start, warm start, or hot start with refresh
for all parameters. |