Hierarchy
⤷ BC-DB-DB2 (Application Component) DB2 for z/OS
⤷ STU2 (Package) CCMS for DB2 for OS/390
Basic Data
Data Element | DB2CCTEMP |
Short Description | DSNACCMO: Use template dynamic allocation |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR1 | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Template |
Medium | 20 | Template dyn. alloc. |
Long | 27 | Template dynamic allocation |
Heading | 27 | Template dynamic allocation |
Documentation
Definition
The stored procedure DSNACCMO enables SAP to use the SQL CALL statement to execute a DB2 utility from a DB2 application program on multiple objects in parallel. Internally, DSNACCMO determines an optimal parallel degree for the utility executions and invokes another stored procedure named DSNUTILS for execution of the utility. That way, there's no need for JES anymore, which uses FTP.
SAP passes the parameters for the utility execution in two global temp tables named DSNACC.MO_TBL and DSNACC.MO_TBL2. MO_TBL2 is filled with the utility statement skeletons, MO_TBL is filled with the according variables, which will be replaced in the statement skeleton or are passed as parameters to stored procedure DSNUTILS.
For DSNACCMO, all DSNUTILS utility_name parameters may be used except ANY for template dynamic allocation, bause the utility name must be known to the optimizing scheduler also in the case of template dynamic allocation.
Instead, this value is set to Y, when template dynamic allocation is used in the utility statement. Allowed values are Y or N.
History
Last changed by/on | SAP | 20070813 |
SAP Release Created in | 620 |