SAP ABAP Data Element DB2CCSEQNO (DSNACCMO: Sequence number for large statements)
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 DB2CCSEQNO
Short Description DSNACCMO: Sequence number for large statements  
Data Type
Category of Dictionary Type     Direct Type Entry
Type of Object Referenced     No Information
Domain / Name of Reference Type      
Data Type INT4   4-byte integer, integer number with sign 
Length 10    
Decimal Places 0    
Output Length 11    
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 Seq. no. 
Medium 15 Seq. number 
Long 20 Sequence number 
Heading 15 Sequence number 
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.

This value specifies a unique positive identifier for a part of the utility execution statement. If a utility statement exceeds 4000 characters, it can be split up and inserted into DSNACC.MO_TBL2 with the sequence starting at 0 and then being incremented with every insert. For the actual execution, the statement pieces are concatenated without any seperation characters or blanks in between.

History
Last changed by/on SAP  20130604 
SAP Release Created in 620