Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DB-DB4 (Application Component) DB2 for AS/400⤷
STU4 (Package) CCMS / AS/400
Basic Data
| Data Element | QQPNAM |
| Short Description | iSeries: Package/Program Name (Database Monitor) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | QQC10 | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| 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 | Pkg/PgmNam |
| Medium | 19 | Pack/Prog Name |
| Long | 20 | Package/Program Name |
| Heading | 55 | Package/Program Name |
Documentation
Definition
QQPNAM is the name of the SQL package which contains the prepared statement that was used to implement a query.
Use
The combination of QQPLIB,QQPNAM and QQSNAM identifies the statement executed.
Note
When an SQL statement is executed from an SAP System for the first time, the optimizer prepares this statement into an SQL package. When the statement is executed again - the host variables can be different in the different statement executions - the optimizer does not need to do all the work again. Instead the access plan that was saved in the SQL package is used.
Depending on the identification assigned to a statement, the prepared statement is stored in a specific type of SQL package.
Examples:
ABAP SQL packages: the package SAPLSTRUGJ contains prepared statements for queries run using ABAP source program SAPLSTRU.
Table packages: the package D010TFC contains prepared statements for queries performed on table D010T.
The type of SQL package determines when a statement has to be prepared again, even if one already exists in a package.
Examples:
ABAP packages: the ABAP has been regenerated after the statement was prepared into the package.
Table packages: the table was regenerated after the last statement preparation). A new package is created if the date (month/day/year) of the regeneration of the object differs from the last generation date. (Packages no longer useful will be deleted during the next start of the main instance).
In this way, one package can contain several prepared statements each for a different statement and/or several prepared statements for one statement.
Types and Naming Conventions for SQL Packages:
The type of the SQL package specifies the object type which was used to identify the statement. Examples of types are:
0: ABAP source; 1: C program source; 2: ABAP Dynpro; 3: SAP table
Depending on the package type, the packages are stored into different libraries.
Package library names follow the pattern: R3<SID><type><year>n
where "SID" is the SAP system ID, "type" is the type of the SQL package, "year" is a 3-digit number where the the century is left out, and "n" indicates if an overflow package exists or not.
SQL package names follow the pattern: <name><month><day>
where name is the name of the object (max. 8 characters) for which statements are prepared into this package, month and day are one-character representations of the timestamp of the object (A = 1, B = 2, .., Z = 26, 0 = 27, 1 = 28, 2 = 29, 3 = 30, 4 = 31)
Example
QQPLIB/QQPNAM: R3C8101960/SAPLALDBAZ
means that the package is for the SAP System C81 and contains all prepared statements identified by ABAP program SAPLALDB since the 26th January 1996 (last generation date of this program).
History
| Last changed by/on | SAP | 20070813 |
| SAP Release Created in |
