# |
Message |
Message Short Text |
Documentation status |
Authorization check |
1 |
000 |
&1&2&3&4 |
The short text describes the object sufficiently |
|
2 |
001 |
SQL error &1 has occurred |
The short text describes the object sufficiently |
|
3 |
002 |
SQL error &1 when calling stored procedure &2 |
The short text describes the object sufficiently |
|
4 |
003 |
Message &1&2 cannot be written to application log |
The short text describes the object sufficiently |
|
5 |
004 |
&1 &2 &3 &4 |
The short text describes the object sufficiently |
|
6 |
005 |
Folder &1 already exists; moved to new parent &2 |
The short text describes the object sufficiently |
|
7 |
006 |
Folder &1 already exists - nothing done |
The short text describes the object sufficiently |
|
8 |
007 |
Folder &1 added |
The short text describes the object sufficiently |
|
9 |
008 |
Start loading tables for &1 into the accelerator |
The short text describes the object sufficiently |
|
10 |
009 |
Load of table &1 started (&2 records) |
The short text describes the object sufficiently |
|
11 |
010 |
&1 does not need to be uploaded. Data is up to date. |
The short text describes the object sufficiently |
|
12 |
011 |
Folder &1 is not empty and therefore cannot be dropped |
The short text describes the object sufficiently |
|
13 |
012 |
Folder &1 dropped |
The short text describes the object sufficiently |
|
14 |
013 |
Not able to drop folder &1 |
The short text describes the object sufficiently |
|
15 |
014 |
Object does not exist: &1, &2 |
The short text describes the object sufficiently |
|
16 |
015 |
Not able to create object: &1, &2 |
The short text describes the object sufficiently |
|
17 |
016 |
Object &1 already exists, parent folder: &2 |
The short text describes the object sufficiently |
|
18 |
017 |
Add new object &1 to parent folder &2 |
The short text describes the object sufficiently |
|
19 |
018 |
Invalid parent chosen |
The short text describes the object sufficiently |
|
20 |
019 |
No folder added or moved |
The short text describes the object sufficiently |
|
21 |
020 |
Invalid parent chosen; not able to add folder &1 |
The short text describes the object sufficiently |
|
22 |
021 |
Object &1 dropped |
The short text describes the object sufficiently |
|
23 |
022 |
Object &1 cannot be dropped |
The short text describes the object sufficiently |
|
24 |
023 |
SQL error &1 has occurred |
The short text describes the object sufficiently |
|
25 |
024 |
Procedure &1 terminated with error &2 |
The short text describes the object sufficiently |
|
26 |
025 |
Procedure &1 ended with warning &2 |
The short text describes the object sufficiently |
|
27 |
026 |
Procedure &1 completed with message &2 |
The short text describes the object sufficiently |
|
28 |
027 |
DB2 Accelerator not identified |
The short text describes the object sufficiently |
|
29 |
028 |
Cannot instantiate XML scheme &1 |
The short text describes the object sufficiently |
|
30 |
029 |
SQL issued in line &1 of method &2 |
The short text describes the object sufficiently |
|
31 |
030 |
DB2 Accelerator name is ambiguous |
The short text describes the object sufficiently |
|
32 |
031 |
DB2 Accelerator &1 found |
The short text describes the object sufficiently |
|
33 |
032 |
DB2 Accelerator not found |
The short text describes the object sufficiently |
|
34 |
033 |
Executing DB2 command &1 |
The short text describes the object sufficiently |
|
35 |
034 |
Error &1 when executing DB2 command |
The short text describes the object sufficiently |
|
36 |
035 |
Setting parameter &1 to value &2 failed |
The short text describes the object sufficiently |
|
37 |
036 |
Job &1 released |
The short text describes the object sufficiently |
|
38 |
037 |
Job &1 scheduled |
The short text describes the object sufficiently |
|
39 |
038 |
Job started for object &1 type &2 and parallel degree &3 |
The short text describes the object sufficiently |
|
40 |
039 |
Invalid value &1 specified for parameter &2 |
The short text describes the object sufficiently |
|
41 |
040 |
Execution of diagnostics action &1 successful |
The short text describes the object sufficiently |
|
42 |
041 |
Execution of diagnostics action &1 failed |
The short text describes the object sufficiently |
|
43 |
042 |
No item selected |
The short text describes the object sufficiently |
|
44 |
043 |
Update has ended with message type &1 (see application log) |
The short text describes the object sufficiently |
|
45 |
044 |
Update has completed successfully |
The short text describes the object sufficiently |
|
46 |
045 |
Object &1 type &2 does not exist in DB2 Accelerator |
The short text describes the object sufficiently |
|
47 |
046 |
InfoObject &1 not found |
The short text describes the object sufficiently |
|
48 |
047 |
InfoObject &1 is not active -> modified version taken |
The short text describes the object sufficiently |
|
49 |
048 |
Function is supported for DB2 for z/OS only |
The short text describes the object sufficiently |
|
50 |
101 |
Table &1 already in DB2 accelerator - nothing done |
The short text describes the object sufficiently |
|
51 |
102 |
Table &1 will be added to DB2 accelerator |
The short text describes the object sufficiently |
|
52 |
103 |
RUNSTATS successfully run on table &1 |
The short text describes the object sufficiently |
|
53 |
104 |
Table &1 is used by other object - not removed |
The short text describes the object sufficiently |
|
54 |
105 |
Table &1 will be removed from DB2 accelerator |
The short text describes the object sufficiently |
|
55 |
106 |
Unknown object type &1 |
The short text describes the object sufficiently |
|
56 |
107 |
START DATABASE(&1) SPACENAM(&2) failed |
The short text describes the object sufficiently |
|
57 |
108 |
RUNSTATS on table &1 failed |
The short text describes the object sufficiently |
|
58 |
109 |
Cannot start new task, return code &1 |
The short text describes the object sufficiently |
|
59 |
110 |
Error &1 has occurred |
The short text describes the object sufficiently |
|
60 |
111 |
Error &1 occurred at line &2 of &3 |
The short text describes the object sufficiently |
|
61 |
112 |
Access to table &1 failed |
The short text describes the object sufficiently |
|
62 |
113 |
Function module &1 failed with return code &2 |
The short text describes the object sufficiently |
|
63 |
114 |
Real Time Statistics not available for table &1 |
The short text describes the object sufficiently |
|
64 |
115 |
Reference Real Time Statistics not saved for table &1 |
The short text describes the object sufficiently |
|
65 |
116 |
Authorization check failed |
The short text describes the object sufficiently |
|
66 |
117 |
Method &1 terminated with error |
The short text describes the object sufficiently |
|
67 |
118 |
Real Time Statistics repaired for table &1 |
The short text describes the object sufficiently |
|
68 |
119 |
Table &1 not in DB2 Accelerator or contains archived data - not removed |
The short text describes the object sufficiently |
|
69 |
120 |
Deployment set to &1 - nothing done |
The short text describes the object sufficiently |
|
70 |
121 |
Table &1 loaded |
The short text describes the object sufficiently |
|
71 |
122 |
Unable to load table &1 |
The short text describes the object sufficiently |
|
72 |
123 |
Incremental update of table &1 on accelerator &2 not allowed |
The short text describes the object sufficiently |
|
73 |
124 |
Update of rollup status to &2 for infocube &1 failed |
The short text describes the object sufficiently |
|
74 |
125 |
Object &1 of type &2 does not exist in DB2 Accelerator |
The short text describes the object sufficiently |
|
75 |
126 |
Table &1 has an obsolete layout and is being refreshed in DB2 Accelerator |
The short text describes the object sufficiently |
|
76 |
127 |
Table &1 is loaded by concurrent process -> nothing done |
The short text describes the object sufficiently |
|
77 |
128 |
Table &1 has invalid status &2 |
The short text describes the object sufficiently |
|
78 |
200 |
&1 |
The short text describes the object sufficiently |
|
79 |
201 |
Near-line storage &1 connected |
The short text describes the object sufficiently |
|
80 |
202 |
SQL error &1 has occurred |
The short text describes the object sufficiently |
|
81 |
203 |
Database error &1 |
The short text describes the object sufficiently |
|
82 |
204 |
Changing request to &1 not allowed in status &2 |
The short text describes the object sufficiently |
|
83 |
205 |
Loading table &1 partition &2 to the DB2 Accelerator |
The short text describes the object sufficiently |
|
84 |
206 |
Table &1 partition &2 loaded in &3 seconds |
The short text describes the object sufficiently |
|
85 |
207 |
Procedure &1 terminated with error &2 |
The short text describes the object sufficiently |
|
86 |
208 |
Table &1 dropped |
The short text describes the object sufficiently |
|
87 |
209 |
Table &1 removed from DB2 Accelerator |
The short text describes the object sufficiently |
|
88 |
210 |
Table &1 cannot be dropped |
The short text describes the object sufficiently |
|
89 |
211 |
Table &1 added to DB2 Accelerator |
The short text describes the object sufficiently |
|
90 |
212 |
DB2 Accelerator deactivated, &1 not executed |
The short text describes the object sufficiently |
|
91 |
213 |
DB2 Accelerator deactivated, request &1 not replicated |
The short text describes the object sufficiently |
|
92 |
214 |
Table &1 activated |
The short text describes the object sufficiently |
|
93 |
215 |
Activation of table &1 failed |
The short text describes the object sufficiently |
|
94 |
216 |
Table &1 has &2 partitions, creating new version |
The short text describes the object sufficiently |
|
95 |
217 |
Table &1 partition &2 added |
The short text describes the object sufficiently |
|
96 |
218 |
Table &1 partition &2 is full |
The short text describes the object sufficiently |
|
97 |
219 |
Database connection &1 not defined in table DBCON |
The short text describes the object sufficiently |
|
98 |
220 |
SQL issued in line &1 of method &2 |
The short text describes the object sufficiently |
|
99 |
221 |
Table &1 created on connection &2 |
The short text describes the object sufficiently |
|
100 |
222 |
Procedure &1 ended with warning &2 |
The short text describes the object sufficiently |
|
101 |
223 |
Procedure &1 successfully finished with message &2 |
The short text describes the object sufficiently |
|
102 |
224 |
Table &1 dropped on connection &2 |
The short text describes the object sufficiently |
|
103 |
225 |
Table &1 cannot be dropped on connection &2 |
The short text describes the object sufficiently |
|
104 |
226 |
Table &1 contains data and thus cannot be dropped |
The short text describes the object sufficiently |
|
105 |
227 |
Table &1 on connection &2 contains data and thus cannot be dropped |
The short text describes the object sufficiently |
|
106 |
228 |
Creating table version &1 of nearline object &2 |
The short text describes the object sufficiently |
|
107 |
229 |
DB2 Accelerator deactivated, request &1 not archived |
The short text describes the object sufficiently |
|
108 |
230 |
Multiple DB2 Accelerators found, set &1 in table RSADMIN |
The short text describes the object sufficiently |
|
109 |
231 |
Table &1 owned by system &2, but system is &3 - write access denied |
The short text describes the object sufficiently |
|
110 |
232 |
Table &1 owned by system &2, not deleted |
The short text describes the object sufficiently |
|
111 |
233 |
Archiving deactivated, request &1 is being loaded, but not archived |
The short text describes the object sufficiently |
|
112 |
234 |
Authorization check failed |
The short text describes the object sufficiently |
|
113 |
235 |
Archiving table &1 partition &2 to the DB2 Accelerator |
The short text describes the object sufficiently |
|
114 |
236 |
Table &1 partition &2 archived in &3 seconds |
The short text describes the object sufficiently |
|
115 |
237 |
Enqueue on table &1 not available for &2 seconds |
The short text describes the object sufficiently |
|