Hierarchy
⤷ BC-DB-DB2 (Application Component) DB2 for z/OS
⤷ STU2 (Package) CCMS for DB2 for OS/390
Basic Data
Data Element | DB2CCMAXP |
Short Description | DSNACCMO: Maximum number of parallel subtasks |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | INT2 | |
Data Type | INT2 | 2-byte integer, only for length field before LCHR or LRAW |
Length | 5 | |
Decimal Places | 0 | |
Output Length | 5 | |
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 | Max. par. |
Medium | 15 | Max. parallel |
Long | 35 | Maximum number of parallel subtasks |
Heading | 35 | Maximum number of parallel subtasks |
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 indirectly 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.
This value is one of the direct input parameters of DSNACCMO. It specifies the maximum number of parallel subtasks that may be started. The actual number may be lower then the requested number based on the optimizing sort result. You may specifiy 1 to 99.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 620 |