|
Replication and RI rules
#33651137
Ссылка:
Ссылка на сообщение:
Ссылка с названием темы:
Ссылка на профиль пользователя:
|
|
|
|
и joblog:
(пробовал кстати и push и pull репликацию - всё одно и тоже)
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.
46.
47.
48.
49.
50.
51.
52.
53.
54.
55.
56.
57.
58.
59.
60.
61.
62.
63.
64.
65.
66.
67.
68.
69.
70.
71.
72.
73.
74.
75.
76.
77.
78.
79.
80.
81.
82.
83.
84.
85.
86.
87.
88.
89.
90.
91.
92.
93.
94.
95.
96.
97.
98.
99.
100.
101.
102.
103.
104.
105.
106.
107.
108.
109.
110.
111.
112.
113.
114.
115.
116.
117.
118.
119.
120.
121.
122.
123.
124.
125.
126.
127.
128.
129.
130.
131.
132.
133.
134.
135.
136.
137.
138.
139.
140.
141.
142.
143.
144.
145.
146.
147.
148.
149.
150.
151.
152.
153.
154.
155.
156.
157.
158.
159.
160.
161.
162.
163.
164.
165.
166.
167.
168.
169.
170.
171.
172.
173.
174.
175.
176.
177.
178.
179.
180.
181.
182.
183.
184.
185.
186.
187.
188.
189.
190.
191.
192.
193.
194.
195.
196.
197.
198.
199.
200.
201.
202.
203.
204.
205.
206.
207.
208.
209.
210.
211.
212.
213.
214.
215.
216.
217.
218.
219.
220.
221.
222.
223.
224.
225.
226.
227.
228.
229.
230.
231.
232.
233.
234.
235.
236.
237.
238.
239.
240.
241.
242.
243.
244.
245.
246.
247.
248.
249.
250.
251.
252.
253.
254.
255.
256.
257.
258.
259.
260.
261.
262.
263.
264.
265.
266.
267.
268.
269.
270.
271.
272.
273.
274.
275.
276.
277.
278.
279.
280.
281.
282.
283.
284.
285.
286.
287.
288.
289.
290.
291.
292.
293.
294.
295.
296.
297.
298.
299.
300.
301.
302.
303.
304.
305.
306.
307.
308.
309.
310.
311.
312.
313.
314.
315.
316.
317.
318.
319.
320.
321.
322.
323.
324.
325.
326.
327.
328.
329.
330.
331.
332.
333.
334.
335.
336.
337.
338.
339.
340.
341.
342.
343.
344.
345.
346.
347.
348.
349.
350.
351.
352.
353.
354.
355.
356.
357.
358.
359.
360.
361.
362.
363.
364.
365.
366.
367.
368.
369.
370.
371.
372.
373.
374.
375.
376.
377.
378.
379.
380.
381.
382.
383.
384.
385.
386.
387.
388.
389.
390.
391.
392.
393.
394.
395.
396.
397.
398.
399.
400.
401.
402.
403.
404.
405.
406.
407.
408.
409.
410.
411.
412.
413.
414.
415.
416.
417.
418.
419.
420.
421.
422.
423.
424.
425.
426.
427.
428.
429.
430.
431.
432.
433.
434.
435.
436.
437.
438.
439.
440.
441.
442.
443.
444.
445.
446.
447.
448.
449.
450.
451.
452.
453.
454.
455.
456.
457.
458.
459.
460.
461.
462.
463.
464.
5722SS1 V5R2M0 020719 Job Log AS400A 06 . 04 . 06 15 : 38 : 20 Page 1
Job name . . . . . . . . . . : TESTAPPL1 User . . . . . . : testuser Number . . . . . . . . . . . : 083557
Job description . . . . . . : QZSNDPR Library . . . . . : QDP4
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
CPF1124 Information 00 06 . 04 . 06 15 : 33 : 12 . 950096 QWTPIIPP QSYS 05D4 *EXT *N
Message . . . . : Job 083557 /testuser/TESTAPPL1 started on 06 . 04 . 06 at
15 : 33 : 12 in subsystem QZSNDPR in QDP4. Job entered system on 06 . 04 . 06 at
15 : 33 : 12 .
CPI1125 Information 00 06 . 04 . 06 15 : 33 : 12 . 951240 QWTPCRJA QSYS 0108 *EXT *N
Message . . . . : Job 083557 /testuser/TESTAPPL1 submitted.
Cause . . . . . : Job 083557 /testuser/TESTAPPL1 submitted to job queue
QZSNDPR in QDP4 from job 083535 /testuser/QPADEV0007. Job
083557 /testuser/TESTAPPL1 was started using the Submit Job (SBMJOB) command
with the following job attributes: JOBPTY( 5 ) OUTPTY( 5 ) PRTTXT()
RTGDTA(QCMDB) SYSLIBL(QSYS QSYS2 QHLPSYS QUSRSYS)
CURLIB(*CRTDFT) INLLIBL(QTEMP ASN QDP4 QGPL) LOG( 4 00
*SECLVL) LOGCLPGM(*NO) INQMSGRPY(*RQD) OUTQ(/*DEV) PRTDEV(PRT01) HOLD(*NO)
DATE(*SYSVAL) SWS( 00000000 ) MSGQ(QUSRSYS/testuser) CCSID( 1025 )
SRTSEQ(*N/*HEX) LANGID(ENU) CNTRYID(US) JOBMSGQMX( 16 ) JOBMSGQFL(*WRAP)
ALWMLTTHD(*NO) INLASPGRP(*NONE) SPLFACN(*KEEP).
*NONE Request 06 . 04 . 06 15 : 33 : 12 . 952064 QWTSCSBJ *N QCMD QSYS 0178
Message . . . . : -CALL PGM(QDP4/QZSNAPV2) PARM('TESTAPPL1 ' '*LOCAL
' 'A' '*NONE ' '*NONE ' 'Y' 'Y' ' '
'00000300' 'N' 'N' 'N')
ASN1044 Information 00 06 . 04 . 06 15 : 33 : 13 . 492792 QZSNAPV2 QDP4 *STMT QZSNAPV2 QDP4 *STMT
From module . . . . . . . . : QZSNAPV2
From procedure . . . . . . : inform_message
Statement . . . . . . . . . : 16
To module . . . . . . . . . : QZSNAPV2
To procedure . . . . . . . : _C_pep
Statement . . . . . . . . . : *N
Message . . . . : Apply will be inactive for 5 minutes and 0 seconds.
CPI9160 Information 00 06 . 04 . 06 15 : 38 : 14 . 143616 QCNSINIT QSYS 0A90 QTSMGAFT QSYS 0620
Message . . . . : Database connection started over TCP/IP or a local socket.
Cause . . . . . : The database server job 075406 /QUSER/QRWTSRVR has been
allocated on system AS400B for handling a new TCP/IP or local socket
connection using DDM protocols. The connection uses IP address
192 . 168 . 56 . 231 , port 446 , and user ID testuser at the server. (If the IP
address is 0 . 0 . 0 . 0 , it indicates that the connection uses a local socket.)
The connection has a scope of *ACTGRP level in activation group *N with an
activation group number of 198 .
CPC7301 Completion 00 06 . 04 . 06 15 : 38 : 18 . 173856 QDDCPF QSYS 0546 QZSNAPV2 QDP4 *STMT
To module . . . . . . . . . : QZSNAPV2
To procedure . . . . . . . : create_spill_file
Statement . . . . . . . . . : 3
Message . . . . : File ASNAS000 created in library QTEMP.
CPC7305 Completion 00 06 . 04 . 06 15 : 38 : 18 . 212072 QDDCPFM QSYS 005B QZSNAPV2 QDP4 *STMT
To module . . . . . . . . . : QZSNAPV2
To procedure . . . . . . . : create_spill_file
Statement . . . . . . . . . : 3
Message . . . . : Member ASNAS000 added to file ASNAS000 in QTEMP.
CPC7301 Completion 00 06 . 04 . 06 15 : 38 : 18 . 695192 QDDCPF QSYS 0546 QZSNAPV2 QDP4 *STMT
To module . . . . . . . . . : QZSNAPV2
To procedure . . . . . . . : create_spill_file
Statement . . . . . . . . . : 3
Message . . . . : File ASNAS001 created in library QTEMP.
5722SS1 V5R2M0 020719 Job Log AS400A 06 . 04 . 06 15 : 38 : 20 Page 2
Job name . . . . . . . . . . : TESTAPPL1 User . . . . . . : testuser Number . . . . . . . . . . . : 083557
Job description . . . . . . : QZSNDPR Library . . . . . : QDP4
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
CPC7305 Completion 00 06 . 04 . 06 15 : 38 : 18 . 740696 QDDCPFM QSYS 005B QZSNAPV2 QDP4 *STMT
To module . . . . . . . . . : QZSNAPV2
To procedure . . . . . . . : create_spill_file
Statement . . . . . . . . . : 3
Message . . . . : Member ASNAS001 added to file ASNAS001 in QTEMP.
CPC7301 Completion 00 06 . 04 . 06 15 : 38 : 19 . 219656 QDDCPF QSYS 0546 QZSNAPV2 QDP4 *STMT
To module . . . . . . . . . : QZSNAPV2
To procedure . . . . . . . : create_spill_file
Statement . . . . . . . . . : 3
Message . . . . : File ASNAS002 created in library QTEMP.
CPC7305 Completion 00 06 . 04 . 06 15 : 38 : 19 . 257192 QDDCPFM QSYS 005B QZSNAPV2 QDP4 *STMT
To module . . . . . . . . . : QZSNAPV2
To procedure . . . . . . . : create_spill_file
Statement . . . . . . . . . : 3
Message . . . . : Member ASNAS002 added to file ASNAS002 in QTEMP.
CPC7301 Completion 00 06 . 04 . 06 15 : 38 : 19 . 745280 QDDCPF QSYS 0546 QZSNAPV2 QDP4 *STMT
To module . . . . . . . . . : QZSNAPV2
To procedure . . . . . . . : create_spill_file
Statement . . . . . . . . . : 3
Message . . . . : File ASNAS003 created in library QTEMP.
CPC7305 Completion 00 06 . 04 . 06 15 : 38 : 19 . 781392 QDDCPFM QSYS 005B QZSNAPV2 QDP4 *STMT
To module . . . . . . . . . : QZSNAPV2
To procedure . . . . . . . : create_spill_file
Statement . . . . . . . . . : 3
Message . . . . : Member ASNAS003 added to file ASNAS003 in QTEMP.
CPC7301 Completion 00 06 . 04 . 06 15 : 38 : 19 . 790784 QDDCPF QSYS 0546 QZSNAPV2 QDP4 *STMT
To module . . . . . . . . . : QZSNAPV2
To procedure . . . . . . . : create_spill_file
Statement . . . . . . . . . : 3
Message . . . . : File ASNAS004 created in library QTEMP.
CPC7305 Completion 00 06 . 04 . 06 15 : 38 : 19 . 827088 QDDCPFM QSYS 005B QZSNAPV2 QDP4 *STMT
To module . . . . . . . . . : QZSNAPV2
To procedure . . . . . . . : create_spill_file
Statement . . . . . . . . . : 3
Message . . . . : Member ASNAS004 added to file ASNAS004 in QTEMP.
CPC7301 Completion 00 06 . 04 . 06 15 : 38 : 19 . 835968 QDDCPF QSYS 0546 QZSNAPV2 QDP4 *STMT
To module . . . . . . . . . : QZSNAPV2
To procedure . . . . . . . : create_spill_file
Statement . . . . . . . . . : 3
Message . . . . : File ASNAS005 created in library QTEMP.
CPC7305 Completion 00 06 . 04 . 06 15 : 38 : 19 . 873376 QDDCPFM QSYS 005B QZSNAPV2 QDP4 *STMT
To module . . . . . . . . . : QZSNAPV2
To procedure . . . . . . . : create_spill_file
Statement . . . . . . . . . : 3
Message . . . . : Member ASNAS005 added to file ASNAS005 in QTEMP.
CPF502D Sender copy 30 06 . 04 . 06 15 : 38 : 19 . 924000 QDBSIGEX QSYS 01D5 QDBSIGEX QSYS 01D5
Message . . . . : Referential constraint violation on member TEST3.
Cause . . . . . : The operation being performed on member TEST3 file TEST3
in library myscheme failed. Constraint TESTCSTR2 prevents record number 0 from
being inserted or updated in member TEST3 of dependent file TEST3 in library
myscheme because a matching key value was not found in member TEST2 of parent
file TEST2 in library myscheme. If the record number is zero, then the error
5722SS1 V5R2M0 020719 Job Log AS400A 06 . 04 . 06 15 : 38 : 20 Page 3
Job name . . . . . . . . . . : TESTAPPL1 User . . . . . . : testuser Number . . . . . . . . . . . : 083557
Job description . . . . . . : QZSNDPR Library . . . . . : QDP4
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
occurred on an insert operation. The constraint rule is 2 . The constraint
rules are: 1 -- *RESTRICT 2 -- *NOACTION Recovery . . . : Either specify
a different file, change the file, or change the program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF502D Notify 30 06 . 04 . 06 15 : 38 : 19 . 924032 QDBSIGEX QSYS 01D5 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 9129
Message . . . . : Referential constraint violation on member TEST3.
Cause . . . . . : The operation being performed on member TEST3 file TEST3
in library myscheme failed. Constraint TESTCSTR2 prevents record number 0 from
being inserted or updated in member TEST3 of dependent file TEST3 in library
myscheme because a matching key value was not found in member TEST2 of parent
file TEST2 in library myscheme. If the record number is zero, then the error
occurred on an insert operation. The constraint rule is 2 . The constraint
rules are: 1 -- *RESTRICT 2 -- *NOACTION Recovery . . . : Either specify
a different file, change the file, or change the program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0530 Diagnostic 30 06 . 04 . 06 15 : 38 : 19 . 930256 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 20329
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 20329
Message . . . . : Operation not allowed by referential constraint TESTCSTR2
in myscheme.
Cause . . . . . : If this is an INSERT or UPDATE statement, the value is not
valid for the foreign key because it does not have a matching value in the
parent key. If this is a DELETE statement affected by a SET DEFAULT delete
rule, the default value is not valid for the same reason. If this is an
ALTER TABLE statement, the result of the operation would violate the
constraint TESTCSTR2. Constraint TESTCSTR2 in myscheme for table TEST3 in myscheme
requires that any non-null value of the foreign key have a matching value in
the parent key. Recovery . . . : To conform to the constraint rule, you
must either: -- change the INSERT or UPDATE value to match a value in the
parent key, -- insert a row in the parent file that matches the foreign key
values being inserted or updated. -- insert a row in the parent file that
matches the foreign key default values of the dependent rows. Otherwise, you
must drop the referential constraint.
CPF502D Sender copy 30 06 . 04 . 06 15 : 38 : 19 . 961208 QDBSIGEX QSYS 01D5 QDBSIGEX QSYS 01D5
Message . . . . : Referential constraint violation on member TEST2.
Cause . . . . . : The operation being performed on member TEST2 file TEST2
in library myscheme failed. Constraint TESTCSTR prevents record number 0 from
being inserted or updated in member TEST2 of dependent file TEST2 in library
myscheme because a matching key value was not found in member TEST1 of parent
file TEST1 in library myscheme. If the record number is zero, then the error
occurred on an insert operation. The constraint rule is 2 . The constraint
rules are: 1 -- *RESTRICT 2 -- *NOACTION Recovery . . . : Either specify
a different file, change the file, or change the program. Then try your
5722SS1 V5R2M0 020719 Job Log AS400A 06 . 04 . 06 15 : 38 : 20 Page 4
Job name . . . . . . . . . . : TESTAPPL1 User . . . . . . : testuser Number . . . . . . . . . . . : 083557
Job description . . . . . . : QZSNDPR Library . . . . . : QDP4
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF502D Notify 30 06 . 04 . 06 15 : 38 : 19 . 961240 QDBSIGEX QSYS 01D5 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 9129
Message . . . . : Referential constraint violation on member TEST2.
Cause . . . . . : The operation being performed on member TEST2 file TEST2
in library myscheme failed. Constraint TESTCSTR prevents record number 0 from
being inserted or updated in member TEST2 of dependent file TEST2 in library
myscheme because a matching key value was not found in member TEST1 of parent
file TEST1 in library myscheme. If the record number is zero, then the error
occurred on an insert operation. The constraint rule is 2 . The constraint
rules are: 1 -- *RESTRICT 2 -- *NOACTION Recovery . . . : Either specify
a different file, change the file, or change the program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0530 Diagnostic 30 06 . 04 . 06 15 : 38 : 19 . 965928 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 20329
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 20329
Message . . . . : Operation not allowed by referential constraint TESTCSTR
in myscheme.
Cause . . . . . : If this is an INSERT or UPDATE statement, the value is not
valid for the foreign key because it does not have a matching value in the
parent key. If this is a DELETE statement affected by a SET DEFAULT delete
rule, the default value is not valid for the same reason. If this is an
ALTER TABLE statement, the result of the operation would violate the
constraint TESTCSTR. Constraint TESTCSTR in myscheme for table TEST2 in myscheme
requires that any non-null value of the foreign key have a matching value in
the parent key. Recovery . . . : To conform to the constraint rule, you
must either: -- change the INSERT or UPDATE value to match a value in the
parent key, -- insert a row in the parent file that matches the foreign key
values being inserted or updated. -- insert a row in the parent file that
matches the foreign key default values of the dependent rows. Otherwise, you
must drop the referential constraint.
CPF502D Sender copy 30 06 . 04 . 06 15 : 38 : 20 . 041624 QDBSIGEX QSYS 01D5 QDBSIGEX QSYS 01D5
Message . . . . : Referential constraint violation on member TEST3.
Cause . . . . . : The operation being performed on member TEST3 file TEST3
in library myscheme failed. Constraint TESTCSTR2 prevents record number 0 from
being inserted or updated in member TEST3 of dependent file TEST3 in library
myscheme because a matching key value was not found in member TEST2 of parent
file TEST2 in library myscheme. If the record number is zero, then the error
occurred on an insert operation. The constraint rule is 2 . The constraint
rules are: 1 -- *RESTRICT 2 -- *NOACTION Recovery . . . : Either specify
a different file, change the file, or change the program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF502D Notify 30 06 . 04 . 06 15 : 38 : 20 . 041648 QDBSIGEX QSYS 01D5 QSQRUN3 QSYS *STMT
5722SS1 V5R2M0 020719 Job Log AS400A 06 . 04 . 06 15 : 38 : 20 Page 5
Job name . . . . . . . . . . : TESTAPPL1 User . . . . . . : testuser Number . . . . . . . . . . . : 083557
Job description . . . . . . : QZSNDPR Library . . . . . : QDP4
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 9129
Message . . . . : Referential constraint violation on member TEST3.
Cause . . . . . : The operation being performed on member TEST3 file TEST3
in library myscheme failed. Constraint TESTCSTR2 prevents record number 0 from
being inserted or updated in member TEST3 of dependent file TEST3 in library
myscheme because a matching key value was not found in member TEST2 of parent
file TEST2 in library myscheme. If the record number is zero, then the error
occurred on an insert operation. The constraint rule is 2 . The constraint
rules are: 1 -- *RESTRICT 2 -- *NOACTION Recovery . . . : Either specify
a different file, change the file, or change the program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0530 Diagnostic 30 06 . 04 . 06 15 : 38 : 20 . 041928 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 20329
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 20329
Message . . . . : Operation not allowed by referential constraint TESTCSTR2
in myscheme.
Cause . . . . . : If this is an INSERT or UPDATE statement, the value is not
valid for the foreign key because it does not have a matching value in the
parent key. If this is a DELETE statement affected by a SET DEFAULT delete
rule, the default value is not valid for the same reason. If this is an
ALTER TABLE statement, the result of the operation would violate the
constraint TESTCSTR2. Constraint TESTCSTR2 in myscheme for table TEST3 in myscheme
requires that any non-null value of the foreign key have a matching value in
the parent key. Recovery . . . : To conform to the constraint rule, you
must either: -- change the INSERT or UPDATE value to match a value in the
parent key, -- insert a row in the parent file that matches the foreign key
values being inserted or updated. -- insert a row in the parent file that
matches the foreign key default values of the dependent rows. Otherwise, you
must drop the referential constraint.
CPF502D Sender copy 30 06 . 04 . 06 15 : 38 : 20 . 055320 QDBSIGEX QSYS 01D5 QDBSIGEX QSYS 01D5
Message . . . . : Referential constraint violation on member TEST3.
Cause . . . . . : The operation being performed on member TEST3 file TEST3
in library myscheme failed. Constraint TESTCSTR2 prevents record number 0 from
being inserted or updated in member TEST3 of dependent file TEST3 in library
myscheme because a matching key value was not found in member TEST2 of parent
file TEST2 in library myscheme. If the record number is zero, then the error
occurred on an insert operation. The constraint rule is 2 . The constraint
rules are: 1 -- *RESTRICT 2 -- *NOACTION Recovery . . . : Either specify
a different file, change the file, or change the program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF502D Notify 30 06 . 04 . 06 15 : 38 : 20 . 056568 QDBSIGEX QSYS 01D5 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 9129
5722SS1 V5R2M0 020719 Job Log AS400A 06 . 04 . 06 15 : 38 : 20 Page 6
Job name . . . . . . . . . . : TESTAPPL1 User . . . . . . : testuser Number . . . . . . . . . . . : 083557
Job description . . . . . . : QZSNDPR Library . . . . . : QDP4
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
Message . . . . : Referential constraint violation on member TEST3.
Cause . . . . . : The operation being performed on member TEST3 file TEST3
in library myscheme failed. Constraint TESTCSTR2 prevents record number 0 from
being inserted or updated in member TEST3 of dependent file TEST3 in library
myscheme because a matching key value was not found in member TEST2 of parent
file TEST2 in library myscheme. If the record number is zero, then the error
occurred on an insert operation. The constraint rule is 2 . The constraint
rules are: 1 -- *RESTRICT 2 -- *NOACTION Recovery . . . : Either specify
a different file, change the file, or change the program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0530 Diagnostic 30 06 . 04 . 06 15 : 38 : 20 . 056840 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 20329
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 20329
Message . . . . : Operation not allowed by referential constraint TESTCSTR2
in myscheme.
Cause . . . . . : If this is an INSERT or UPDATE statement, the value is not
valid for the foreign key because it does not have a matching value in the
parent key. If this is a DELETE statement affected by a SET DEFAULT delete
rule, the default value is not valid for the same reason. If this is an
ALTER TABLE statement, the result of the operation would violate the
constraint TESTCSTR2. Constraint TESTCSTR2 in myscheme for table TEST3 in myscheme
requires that any non-null value of the foreign key have a matching value in
the parent key. Recovery . . . : To conform to the constraint rule, you
must either: -- change the INSERT or UPDATE value to match a value in the
parent key, -- insert a row in the parent file that matches the foreign key
values being inserted or updated. -- insert a row in the parent file that
matches the foreign key default values of the dependent rows. Otherwise, you
must drop the referential constraint.
CPF502D Sender copy 30 06 . 04 . 06 15 : 38 : 20 . 063184 QDBSIGEX QSYS 01D5 QDBSIGEX QSYS 01D5
Message . . . . : Referential constraint violation on member TEST3.
Cause . . . . . : The operation being performed on member TEST3 file TEST3
in library myscheme failed. Constraint TESTCSTR2 prevents record number 0 from
being inserted or updated in member TEST3 of dependent file TEST3 in library
myscheme because a matching key value was not found in member TEST2 of parent
file TEST2 in library myscheme. If the record number is zero, then the error
occurred on an insert operation. The constraint rule is 2 . The constraint
rules are: 1 -- *RESTRICT 2 -- *NOACTION Recovery . . . : Either specify
a different file, change the file, or change the program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF502D Notify 30 06 . 04 . 06 15 : 38 : 20 . 063208 QDBSIGEX QSYS 01D5 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 9129
Message . . . . : Referential constraint violation on member TEST3.
Cause . . . . . : The operation being performed on member TEST3 file TEST3
in library myscheme failed. Constraint TESTCSTR2 prevents record number 0 from
5722SS1 V5R2M0 020719 Job Log AS400A 06 . 04 . 06 15 : 38 : 20 Page 7
Job name . . . . . . . . . . : TESTAPPL1 User . . . . . . : testuser Number . . . . . . . . . . . : 083557
Job description . . . . . . : QZSNDPR Library . . . . . : QDP4
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
being inserted or updated in member TEST3 of dependent file TEST3 in library
myscheme because a matching key value was not found in member TEST2 of parent
file TEST2 in library myscheme. If the record number is zero, then the error
occurred on an insert operation. The constraint rule is 2 . The constraint
rules are: 1 -- *RESTRICT 2 -- *NOACTION Recovery . . . : Either specify
a different file, change the file, or change the program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0530 Diagnostic 30 06 . 04 . 06 15 : 38 : 20 . 063400 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 20329
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 20329
Message . . . . : Operation not allowed by referential constraint TESTCSTR2
in myscheme.
Cause . . . . . : If this is an INSERT or UPDATE statement, the value is not
valid for the foreign key because it does not have a matching value in the
parent key. If this is a DELETE statement affected by a SET DEFAULT delete
rule, the default value is not valid for the same reason. If this is an
ALTER TABLE statement, the result of the operation would violate the
constraint TESTCSTR2. Constraint TESTCSTR2 in myscheme for table TEST3 in myscheme
requires that any non-null value of the foreign key have a matching value in
the parent key. Recovery . . . : To conform to the constraint rule, you
must either: -- change the INSERT or UPDATE value to match a value in the
parent key, -- insert a row in the parent file that matches the foreign key
values being inserted or updated. -- insert a row in the parent file that
matches the foreign key default values of the dependent rows. Otherwise, you
must drop the referential constraint.
CPF502D Sender copy 30 06 . 04 . 06 15 : 38 : 20 . 071768 QDBSIGEX QSYS 01D5 QDBSIGEX QSYS 01D5
Message . . . . : Referential constraint violation on member TEST3.
Cause . . . . . : The operation being performed on member TEST3 file TEST3
in library myscheme failed. Constraint TESTCSTR2 prevents record number 0 from
being inserted or updated in member TEST3 of dependent file TEST3 in library
myscheme because a matching key value was not found in member TEST2 of parent
file TEST2 in library myscheme. If the record number is zero, then the error
occurred on an insert operation. The constraint rule is 2 . The constraint
rules are: 1 -- *RESTRICT 2 -- *NOACTION Recovery . . . : Either specify
a different file, change the file, or change the program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF502D Notify 30 06 . 04 . 06 15 : 38 : 20 . 071784 QDBSIGEX QSYS 01D5 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 9129
Message . . . . : Referential constraint violation on member TEST3.
Cause . . . . . : The operation being performed on member TEST3 file TEST3
in library myscheme failed. Constraint TESTCSTR2 prevents record number 0 from
being inserted or updated in member TEST3 of dependent file TEST3 in library
myscheme because a matching key value was not found in member TEST2 of parent
file TEST2 in library myscheme. If the record number is zero, then the error
5722SS1 V5R2M0 020719 Job Log AS400A 06 . 04 . 06 15 : 38 : 20 Page 8
Job name . . . . . . . . . . : TESTAPPL1 User . . . . . . : testuser Number . . . . . . . . . . . : 083557
Job description . . . . . . : QZSNDPR Library . . . . . : QDP4
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
occurred on an insert operation. The constraint rule is 2 . The constraint
rules are: 1 -- *RESTRICT 2 -- *NOACTION Recovery . . . : Either specify
a different file, change the file, or change the program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0530 Diagnostic 30 06 . 04 . 06 15 : 38 : 20 . 072000 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 20329
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 20329
Message . . . . : Operation not allowed by referential constraint TESTCSTR2
in myscheme.
Cause . . . . . : If this is an INSERT or UPDATE statement, the value is not
valid for the foreign key because it does not have a matching value in the
parent key. If this is a DELETE statement affected by a SET DEFAULT delete
rule, the default value is not valid for the same reason. If this is an
ALTER TABLE statement, the result of the operation would violate the
constraint TESTCSTR2. Constraint TESTCSTR2 in myscheme for table TEST3 in myscheme
requires that any non-null value of the foreign key have a matching value in
the parent key. Recovery . . . : To conform to the constraint rule, you
must either: -- change the INSERT or UPDATE value to match a value in the
parent key, -- insert a row in the parent file that matches the foreign key
values being inserted or updated. -- insert a row in the parent file that
matches the foreign key default values of the dependent rows. Otherwise, you
must drop the referential constraint.
CPI9161 Information 00 06 . 04 . 06 15 : 38 : 20 . 200960 QCNSTERM QSYS 0222 QDMRCLSE QSYS 006E
Message . . . . : Database TCP/IP or local socket connection ended.
Cause . . . . . : Use of server job 075406 /QUSER/QRWTSRVR has ended on
system AS400B for a remote database connection using TCP/IP or a local
socket connection. The job was handling DDM protocol database requests for
the server using IP address 192 . 168 . 56 . 231 , remote port 446 , and user ID
testuser. (If the IP address is 0 . 0 . 0 . 0 , it indicates that the connection
used a local socket.) The connection had a scope of *ACTGRP level in
activation group *N with an activation group number of 198 .
CPC2191 Completion 00 06 . 04 . 06 15 : 38 : 20 . 312312 QLIDLFIL QSYS 0070 QLICLLIB QSYS 051D
Message . . . . : Object ASNAS000 in QTEMP type *FILE deleted.
CPC2191 Completion 00 06 . 04 . 06 15 : 38 : 20 . 312368 QLIDLFIL QSYS 0070 QLICLLIB QSYS 051D
Message . . . . : Object ASNAS001 in QTEMP type *FILE deleted.
CPC2191 Completion 00 06 . 04 . 06 15 : 38 : 20 . 312416 QLIDLFIL QSYS 0070 QLICLLIB QSYS 051D
Message . . . . : Object ASNAS002 in QTEMP type *FILE deleted.
CPC2191 Completion 00 06 . 04 . 06 15 : 38 : 20 . 312480 QLIDLFIL QSYS 0070 QLICLLIB QSYS 051D
Message . . . . : Object ASNAS003 in QTEMP type *FILE deleted.
CPC2191 Completion 00 06 . 04 . 06 15 : 38 : 20 . 312520 QLIDLFIL QSYS 0070 QLICLLIB QSYS 051D
Message . . . . : Object ASNAS004 in QTEMP type *FILE deleted.
CPC2191 Completion 00 06 . 04 . 06 15 : 38 : 20 . 312576 QLIDLFIL QSYS 0070 QLICLLIB QSYS 051D
Message . . . . : Object ASNAS005 in QTEMP type *FILE deleted.
CPF1164 Completion 00 06 . 04 . 06 15 : 38 : 20 . 318320 QWTMCEOJ QSYS 00BD *EXT *N
Message . . . . : Job 083557 /testuser/TESTAPPL1 ended on 06 . 04 . 06 at
15 : 38 : 20 ; 1 seconds used; end code 0 .
Cause . . . . . : Job 083557 /testuser/TESTAPPL1 completed on 06 . 04 . 06 at
5722SS1 V5R2M0 020719 Job Log AS400A 06 . 04 . 06 15 : 38 : 20 Page 9
Job name . . . . . . . . . . : TESTAPPL1 User . . . . . . : testuser Number . . . . . . . . . . . : 083557
Job description . . . . . . : QZSNDPR Library . . . . . : QDP4
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
15 : 38 : 20 after it used 1 seconds processing unit time. The job had ending
code 0 . The job ended after 1 routing steps with a secondary ending code of
0 . The job ending codes and their meanings are as follows: 0 - The job
completed normally. 10 - The job completed normally during controlled ending
or controlled subsystem ending. 20 - The job exceeded end severity (ENDSEV
job attribute). 30 - The job ended abnormally. 40 - The job ended before
becoming active. 50 - The job ended while the job was active. 60 - The
subsystem ended abnormally while the job was active. 70 - The system ended
abnormally while the job was active. 80 - The job ended (ENDJOBABN command).
90 - The job was forced to end after the time limit ended (ENDJOBABN
command). Recovery . . . : For more information, see the Work Management
topic in the Information Center, http://www.iseries.ibm.com/infocenter.
|
|
|
