Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DB-DB2 (Application Component) DB2 for z/OS⤷
STU2 (Package) CCMS for DB2 for OS/390
Basic Data
| Data Element | DB2CCUTID |
| Short Description | DSNACCMO: Utility-ID stem |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR8 | |
| Data Type | CHAR | Character String |
| Length | 8 | |
| Decimal Places | 0 | |
| Output Length | 8 | |
| 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 | Utility-ID |
| Medium | 15 | Utility-ID stem |
| Long | 20 | Utility-ID stem |
| Heading | 15 | Utility-ID stem |
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 utility-id stem.
The actual utility-id of a utility-execution in a parallel thread will be dynamically created as utilityidstemTTNNNNN where TT is the zero-padded number of the subtask executing the utility and NNNNN is a consecutive number of utilities executed in a subtask. For example, utilityidstem0200005 would be the fifth utility execution that has been processed by the second subtask.
History
| Last changed by/on | SAP | 20070813 |
| SAP Release Created in | 620 |
