Добро пожаловать в форум, Guest  >>   Войти | Регистрация | Поиск | Правила | В избранное | Подписаться
Все форумы / IBM DB2, WebSphere, IMS, U2, etc Новый топик    Ответить
 Replication and RI rules  [new]
riman
Member

Откуда:
Сообщений: 2234
Привет всем.
Есть проблема. У нас имеется OS/400 V5R2M0 и DataPropagator v8.1.
При попытке реплицировать таблицы, связанные реляционной целостностью - эпплай вываливает ругань на её нарушение при вставке записей. Затем эпплай завершается с "Apply program could not read from file" в APPLYTRAIL table.

Все таблицы связанные реляционной целостностью объединены в один subscription set with transaction mode allowed and commit_count=1. Data blocking factor=10 minutes.
Вообще, реляционная целостность и пр. пр. при такой схеме соблюдаются, НО, только если при вставке записей в родительскую и дочернюю таблицы, каждая вставка коммитится отдельно. Если делать блочный коммит, т.е.
autocommit=false;
insert into parenttable;
insert into childtable;
commit;
autocommit=true;

то APPLY пытается выполнить вставку сначала в дочернюю таблицу, а затем уже в родительскую. Ну и естесственно ругается, а затем завершается с "Apply blablabla" (см. выше).

С чем это связано?
И по ходу вопрос к NewYear'y: когда то ты говорил, что тебе приходилось переписывать APPLY для AS/400. Не мог бы ты привести что то вроде guide о том как это сделать? Что то типа: какие сигналы в signal table нужно записывать, чтобы capture начала захватывать изменения и пр. пр. Спасибо.
7 апр 06, 10:32    [2534978]     Ответить | Цитировать Сообщить модератору
 Re: Replication and RI rules  [new]
riman
Member

Откуда:
Сообщений: 2234
если кому то поможет, вот trace file for apply job:

Apply qualifier is TESTAPPL1.
Error Wait is 300 seconds
Issue Sleep msg.
Will not invoke ASNLOAD.
Will not invoke ASNDONE.
NOLOGREUSE is in use
NOLOGSTDOUT is in use
NOTRLREUSE is in use
SQLERRCONTINUE is not in use
COMMIT(n) is not specified
 MIMPC: serverIsolationUR is 1.
 MIMPC: local_srvr is s66666ff!
 MIMPC: Userid is testuser
 MIMPC: cntl server is 8
--- Process next subscription (1) ---
CEXPC: connect to s66666ff
CPGCST: Control server timestamp is 2006-04-06-15.27.22.958005
 R1NES: No eligible named event subscription at this moment
 R1RTS: No eligible relative timer driven subscription at this moment
CS: Stop command has not been issued
 CS: Stop command has not been issued
TTOS: slpDay is 0; slpHour is 0, slpMin is 0, slpSec is 0, slpMSec is 0
TTOS3: sleep_time = 300
TTOS: delay_seconds = 300
Delay_seconds = 300 seconds
 REST: Sleep time = 300 seconds.
  SLP: Sleep for 300 seconds.
   CS: Stop command has not been issued
CS: Stop command has not been issued
--- Process next subscription (2) ---
CEXPC: connect to s66666ff
CPGCST: Control server timestamp is 2006-04-06-15.32.23.278279
 R1NES: No eligible named event subscription at this moment
CS: Stop command has not been issued
Compiled(P) at 19:20:06 on Aug 22 2002 (Level 80116w)
  CPGCI: numKeys is 1
  CPGCI: numKeys is 1
  CPGCI: numKeys is 1
 GMI: set type is READ_ONLY
 -------------------
     set_info
 -------------------
 ACTIVATE      = 1
 APPLY_QUAL    = TESTAPPL1
 SET_NAME      = TESTSET1
 SET_TYPE      = R
 WHOS_ON_FIRST = S
 SOURCE_SERVER = s55555ff
 SOURCE_ALIAS  = s55555ff
 TARGET_SERVER = s66666ff
 TARGET_ALIAS  = s66666ff
 STATUS        = -1
 LASTRUN       = 2006-04-06-15.23.49.959590
 REFRESH_TYPE = R
 SLEEP_MINUTES = 5
 EVENT_NAME    = null
 LASTSUCCESS   = 2006-04-06-15.09.23.296967
 SYNCPOINT     = 8b3c339c0dc817e60001
 SYNCHTIME     = 2006-04-06-15.04.08.417616
 MAX_SYNCH_MINUTES = 10
 CAPTURE_SCHEMA    = ASN
 TGT_CAPTURE_SCHEMA is null
 FEDERATED_SRC_SRVR  is null
 FEDERATED_TGT_SRVR  is null
 JRN_LIB         = myscheme
 JRN_NAME        = QSQJRN
 OPTION_FLAGS = d5d5d5d5
 COMMIT_CNT    = 1
 AUX_STMTS     = 0
 ARCH_LEVEL    = 0801
 -------------------------
    mem_info i = 0
 -------------------------
 SOURCE_OWNER    = myscheme
 SOURCE_TABLE    = TEST1
 SOURCE_VIEW_QUAL = 0
 TARGET_OWNER    = myscheme
 TARGET_TABLE    = TEST1
 TARGET_CONDENSED = Y
 TARGET_COMPLETE = Y
 TARGET_STRUCTURE = 8
 PREDICATES      = null
 MEMBER_STATE = S
 TARGET_KEY_CHG = N
 JOIN_UOW_CD is null
 UOW_CD_PREDICATES  = null
 LOADX_TYPE  is NULL
 -------------------------
    col_info i = 0
 -------------------------
 COL_TYPE        = A
 TARGET_NAME     = ID
 IS_KEY          = Y
 COLNO           = 1
 EXPRESSION      = ID
 -------------------------
    col_info i = 1
 -------------------------
 COL_TYPE        = A
 TARGET_NAME     = NAME
 IS_KEY          = N
 COLNO           = 2
 EXPRESSION      = NAME
 -------------------------
    mem_info i = 1
 -------------------------
 SOURCE_OWNER    = myscheme
 SOURCE_TABLE    = TEST2
 SOURCE_VIEW_QUAL = 0
 TARGET_OWNER    = myscheme
 TARGET_TABLE    = TEST2
 TARGET_CONDENSED = Y
 TARGET_COMPLETE = Y
 TARGET_STRUCTURE = 8
 PREDICATES      = null
 MEMBER_STATE = S
 TARGET_KEY_CHG = N
 JOIN_UOW_CD is null
 UOW_CD_PREDICATES  = null
 LOADX_TYPE  is NULL
 -------------------------
    col_info i = 0
 -------------------------
 COL_TYPE        = A
 TARGET_NAME     = ID
 IS_KEY          = Y
 COLNO           = 1
 EXPRESSION      = ID
 -------------------------
    col_info i = 1
 -------------------------
 COL_TYPE        = A
 TARGET_NAME     = NAME
 IS_KEY          = N
 COLNO           = 2
 EXPRESSION      = NAME
 -------------------------
    col_info i = 2
 -------------------------
 COL_TYPE        = A
 TARGET_NAME     = TEST1ID
 IS_KEY          = N
 COLNO           = 3
 EXPRESSION      = TEST1ID
 -------------------------
    mem_info i = 2
 -------------------------
 SOURCE_OWNER    = myscheme
 SOURCE_TABLE    = TEST3
 SOURCE_VIEW_QUAL = 0
 TARGET_OWNER    = myscheme
 TARGET_TABLE    = TEST3
 TARGET_CONDENSED = Y
 TARGET_COMPLETE = Y
 TARGET_STRUCTURE = 8
 PREDICATES      = null
 MEMBER_STATE = S
 TARGET_KEY_CHG = N
 JOIN_UOW_CD is null
 UOW_CD_PREDICATES  = null
 LOADX_TYPE  is NULL
 -------------------------
    col_info i = 0
 -------------------------
 COL_TYPE        = A
 TARGET_NAME     = ID
 IS_KEY          = Y
 COLNO           = 1
 EXPRESSION      = ID
 -------------------------
    col_info i = 1
 -------------------------
 COL_TYPE        = A
 TARGET_NAME     = NAME
 IS_KEY          = N
 COLNO           = 2
 EXPRESSION      = NAME
 -------------------------
    col_info i = 2
 -------------------------
 COL_TYPE        = A
 TARGET_NAME     = TEST2ID
 IS_KEY          = N
 COLNO           = 3
 EXPRESSION      = TEST2ID
 -------------------------
PSET: Commit1 ok
 CEXPC: connect to s55555ff
 CEXPC: serverIsolationUR is 1. isMvsServer is 0.
 CEXPC: (C)
 GSST: Source server timestamp is 2006-04-06-15.33.32.188157
 GSST: srcArchLvl is 8
 LCKTB:1 cntinue=1; pLockNotFound=0
 LCKTB:2 cntinue=1
 RGRS: GLB.SP = 8b3c35b9236ba6360001
 RGRS: GLB.ST = 2006-04-06-15.13.40.539296!
 RGRS: MSM.SP = 8b3c35b9236ba6360001
 RGRS: MSM.ST = 2006-04-06-15.13.40.539296!
 --------------------------------
    src reg info for mem (0)
 --------------------------------
 GLOBAL_RECORD  = N
 SOURCE_OWNER   = myscheme
 SOURCE_TABLE   = TEST1
 SOURCE_VIEW_QUAL= 0
 SOURCE_STRUCTURE= 1
 SOURCE_CONDENSED= Y
 SOURCE_COMPLETE = Y
 CD_OWNER       = myscheme
 CD_TABLE       = CDTEST1
 PHYS_CHANGE_OWNER = myscheme
 PHYS_CHANGE_TABLE = CDTEST1
 CD_OLD_SYNCHPOINT IS is 8b39cb9a701c00000000
 CD_NEW_SYNCHPOINT IS is 8b3c35b9236ba6360001
 DISABLE_REFRESH = 1
 CCD_OWNER      =
 CCD_TABLE      =
 CCD_OLD_SYNCHPOINT is null
 SYNCHPOINT is null
 SYNCHTIME is null
 CCD_CONDENSED is null
 CCD_COMPLETE is null
 ARCH_LEVEL    = 0801
 DESCRIPTION is null
 BEFORE_IMG_PREFIX is X
 CONFLICT_LEVEL is 0
 CHG_UPD_TO_DEL_INS is N
 STATE is A
 ------------------------------------------
   pc info
 ------------------------------------------
 TARGET_SERVER  = s66666ff
 TARGET_OWNER   = myscheme
 TARGET_TABLE   = TEST1
 SYNCHTIME      = 2006-04-06-15.04.08.076832
 SYNCHPOINT IS 8b3c338816a000000000
 SOURCE_OWNER   = myscheme
 SOURCE_TABLE   = TEST1
 SOURCE_VIEW_QUAL = 0
 APPLY_QUAL      = TESTAPPL1
 SET_NAME        = TESTSET1
 CONTROL_SERVER  = s66666ff
 TARGET_STRUCTURE = 8
 --------------------------------
    src reg info for mem (1)
 --------------------------------
 GLOBAL_RECORD  = N
 SOURCE_OWNER   = myscheme
 SOURCE_TABLE   = TEST2
 SOURCE_VIEW_QUAL= 0
 SOURCE_STRUCTURE= 1
 SOURCE_CONDENSED= Y
 SOURCE_COMPLETE = Y
 CD_OWNER       = myscheme
 CD_TABLE       = CDTEST2
 PHYS_CHANGE_OWNER = myscheme
 PHYS_CHANGE_TABLE = CDTEST2
 CD_OLD_SYNCHPOINT IS is 8b39cb9a701c00000000
 CD_NEW_SYNCHPOINT IS is 8b3c35b9236ba6360001
 DISABLE_REFRESH = 1
 CCD_OWNER      =
 CCD_TABLE      =
 CCD_OLD_SYNCHPOINT is null
 SYNCHPOINT is null
 SYNCHTIME is null
 CCD_CONDENSED is null
 CCD_COMPLETE is null
 ARCH_LEVEL    = 0801
 DESCRIPTION is null
 BEFORE_IMG_PREFIX is X
 CONFLICT_LEVEL is 0
 CHG_UPD_TO_DEL_INS is N
 STATE is A
 ------------------------------------------
   pc info
 ------------------------------------------
 TARGET_SERVER  = s66666ff
 TARGET_OWNER   = myscheme
 TARGET_TABLE   = TEST2
 SYNCHTIME      = 2006-04-06-15.04.08.076832
 SYNCHPOINT IS 8b3c338816a000000000
 SOURCE_OWNER   = myscheme
 SOURCE_TABLE   = TEST2
 SOURCE_VIEW_QUAL = 0
 APPLY_QUAL      = TESTAPPL1
 SET_NAME        = TESTSET1
 CONTROL_SERVER  = s66666ff
 TARGET_STRUCTURE = 8
 --------------------------------
    src reg info for mem (2)
 --------------------------------
 GLOBAL_RECORD  = N
 SOURCE_OWNER   = myscheme
 SOURCE_TABLE   = TEST3
 SOURCE_VIEW_QUAL= 0
 SOURCE_STRUCTURE= 1
 SOURCE_CONDENSED= Y
 SOURCE_COMPLETE = Y
 CD_OWNER       = myscheme
 CD_TABLE       = CDTEST3
 PHYS_CHANGE_OWNER = myscheme
 PHYS_CHANGE_TABLE = CDTEST3
 CD_OLD_SYNCHPOINT IS is 8b39cb9a701c00000000
 CD_NEW_SYNCHPOINT IS is 8b3c35b9236ba6360001
 DISABLE_REFRESH = 1
 CCD_OWNER      =
 CCD_TABLE      =
 CCD_OLD_SYNCHPOINT is null
 SYNCHPOINT is null
 SYNCHTIME is null
 CCD_CONDENSED is null
 CCD_COMPLETE is null
 ARCH_LEVEL    = 0801
 DESCRIPTION is null
 BEFORE_IMG_PREFIX is X
 CONFLICT_LEVEL is 0
 CHG_UPD_TO_DEL_INS is N
 STATE is A
 ------------------------------------------
   pc info
 ------------------------------------------
 TARGET_SERVER  = s66666ff
 TARGET_OWNER   = myscheme
 TARGET_TABLE   = TEST3
 SYNCHTIME      = 2006-04-06-15.04.08.076832
 SYNCHPOINT IS 8b3c338816a000000000
 SOURCE_OWNER   = myscheme
 SOURCE_TABLE   = TEST3
 SOURCE_VIEW_QUAL = 0
 APPLY_QUAL      = TESTAPPL1
 SET_NAME        = TESTSET1
 CONTROL_SERVER  = s66666ff
 TARGET_STRUCTURE = 8
 ------------------------------------------
 Compiled(B) at 19:20:06 on Aug 22 2002 (Level 80116w)
  WPNUSR: target_structure is pit/user copy.
   GPTST: path is Qbfgh
  WPNUSR: target_structure is pit/user copy.
   GPTST: path is Qbfgh
  WPNUSR: target_structure is pit/user copy.
   GPTST: path is Qbfgh
 CPWPLAN: INFO: useSpill_ind is set to Yes
 Compiled(I) at 19:20:06 on Aug 22 2002 (Level 80116w)
 DSYL:2 foundLimit=yes
 DSYL: upperLimit is 8b3c35b9236ba6360001
 DSYL: upperLimit SYNCHTIME is 2006-04-06-15.13.40.539296!
 WPLAN work data:
       +00000000  00000000 00000000 00000000 00000000
       +00000010  00000000 8b3c35b9 236ba636 00012000
       +00000020  80000000 00000000
 --------------------------
    Set Level Workplan
 --------------------------
 skip = 0
 fullrefresh = 0
 Other plan data:
       +00000000  01000003 00000104 f040f0f0
 --------------------------
    Member (0) Workplan
 --------------------------
 skip is 0
 fullrefresh is 0
 doNotCopy is 0
 lowerLimit is 8b3c339c0dc817e60001
 upperLimit is 8b3c35b9236ba6360001
 Other plan data:
       +00000000  01080104 01010000 00000000 00000000
       +00000010  00000000 00000000 00000248 bc001640
 --------------------------
    Member (1) Workplan
 --------------------------
 skip is 0
 fullrefresh is 0
 doNotCopy is 0
 lowerLimit is 8b3c339c0dc817e60001
 upperLimit is 8b3c35b9236ba6360001
 Other plan data:
       +00000000  01080104 01010000 00000000 00000000
       +00000010  00000000 00000000 00000248 bc001640
 --------------------------
    Member (2) Workplan
 --------------------------
 skip is 0
 fullrefresh is 0
 doNotCopy is 0
 lowerLimit is 8b3c339c0dc817e60001
 upperLimit is 8b3c35b9236ba6360001
 Other plan data:
       +00000000  01080104 01010000 00000000 00000000
       +00000010  00000000 00000000 00000248 bc001640
 --------------------------
PSET: RBA translation for member 0
PSET: RBA translation for member 1
PSET: RBA translation for member 2
PSET: Fetch answer set for member 0
 Compiled(F) at 19:20:03 on Aug 22 2002 (Level 80116w)
  CDSET: spill_file(0) = ASNAS000
 FETSET: The number of rows fetched is 1.
PSET: Fetch answer set for member 1
 Compiled(F) at 19:20:03 on Aug 22 2002 (Level 80116w)
  CDSET: spill_file(1) = ASNAS001
 FETSET: The number of rows fetched is 5.
PSET: Fetch answer set for member 2
 Compiled(F) at 19:20:03 on Aug 22 2002 (Level 80116w)
  CDSET: spill_file(2) = ASNAS002
 FETSET: The number of rows fetched is 25.
PSET: Commit3 ok
 CEXPC: connect to s66666ff
 CEXPC: serverIsolationUR is 1. isMvsServer is 0.
 CEXPC: (C)
-------------------------
 Compiled(A) at 19:20:06 on Aug 22 2002 (Level 80116w)
    fopen filename ASNAS003
    fopen filename ASNAS004
    fopen filename ASNAS005
    error_sqlstate: tracing the sqlerrmc
    SQLCA is
          +00000000  e2d8d3c3 c1404040 00000088 fffffdee  !SQLCA      h  ЩЬ!
          +00000010  001e0009 e3c5e2e3 c3e2e3d9 f20004c5  !    TESTCSTR2  E!
          +00000020  c1c9e200 05e3c5e2 e3f30004 c5c1c9e2  !AIS  TEST3  myscheme!
          +00000030  00000000 00000000 00000000 00000000  !                !
          +00000040  00000000 00000000 00000000 00000000  !                !
          +00000050  00000000 00000000 d8e2d8c9 d5e24040  !        QSQINS  !
          +00000060  f5f0f2c4 00000000 00000000 00000000  !502D            !
          +00000070  00000000 00000000 40404040 40404040  !                !
          +00000080  404040f2 f3f5f0f3                    !   23503        !
    APRW: insert_string is INSERT INTO  "myscheme"."TEST3" ("ID", "NAME", "TEST2ID") VALUES(?, ?, ?)
    ------------ Sqlda for INSERT (APRW:2) -----------
    sqldaid:
          +00000000  e2d8d3c4 c1400040                    !SQLDA           !
    sqldabc: 3536
    sqln: 44
    sqld: 3
    SQLVARБ0Ц.sqltype:   496
    SQLVARБ0Ц.sqlind: 0,
    SQLVARБ0Ц.sqllen:     4,
    sqlvarБ0Ц.sqldata:
          +00000000  000000c8                             !   H            !
    SQLVARБ0Ц.sqlname.length:     2
    sqlvarБ0Ц.sqlname.data:
          +00000000  c9c4                                 !ID              !
    SQLVARБ1Ц.sqltype:   449
    SQLVARБ1Ц.sqlind: 0,
    SQLVARБ1Ц.sqllen:   200,
    sqlvarБ1Ц.sqldata:
          +00000000  00069581 9485f1f0 40404040 40404040  !  name10        !
          +00000010  40404040 40404040 40404040 40404040  !                !
          +00000020  40404040 40404040 40404040 40404040  !                !
          +00000030  40404040 40404040 40404040 40404040  !                !
          +00000040  40404040 40404040 40404040 40404040  !                !
          +00000050  40404040 40404040 40404040 40404040  !                !
          +00000060  40404040 40404040 40404040 40404040  !                !
          +00000070  40404040 40404040 40404040 40404040  !                !
          +00000080  40404040 40404040 40404040 40404040  !                !
          +00000090  40404040 40404040 40404040 40404040  !                !
          +000000a0  40404040 40404040 40404040 40404040  !                !
          +000000b0  40404040 40404040 40404040 40404040  !                !
          +000000c0  40404040 40404040                    !                !
    SQLVARБ1Ц.sqlname.length:     4
    sqlvarБ1Ц.sqlname.data:
          +00000000  d5c1d4c5                             !NAME            !
    SQLVARБ2Ц.sqltype:   497
    SQLVARБ2Ц.sqlind: 0,
    SQLVARБ2Ц.sqllen:     4,
    sqlvarБ2Ц.sqldata:
          +00000000  000000c8                             !   H            !
    SQLVARБ2Ц.sqlname.length:     7
    sqlvarБ2Ц.sqlname.data:
          +00000000  e3c5e2e3 f2c9c4                      !TEST2ID         !
    error_sqlstate: tracing the sqlerrmc
    SQLCA is
          +00000000  e2d8d3c3 c1404040 00000088 fffffdee  !SQLCA      h  ЩЬ!
          +00000010  001d0008 e3c5e2e3 c3e2e3d9 0004c5c1  !    TESTCSTR  EA!
          +00000020  c9e20005 e3c5e2e3 f20004c5 c1c9e200  !IS  TEST2  myscheme !
          +00000030  00000000 00000000 00000000 00000000  !                !
          +00000040  00000000 00000000 00000000 00000000  !                !
          +00000050  00000000 00000000 d8e2d8c9 d5e24040  !        QSQINS  !
          +00000060  f5f0f2c4 00000000 00000000 00000000  !502D            !
          +00000070  00000000 00000000 40404040 40404040  !                !
          +00000080  404040f2 f3f5f0f3                    !   23503        !
    APRW: insert_string is INSERT INTO  "myscheme"."TEST2" ("ID", "NAME", "TEST1ID") VALUES(?, ?, ?)
    ------------ Sqlda for INSERT (APRW:2) -----------
    sqldaid:
          +00000000  e2d8d3c4 c1400040                    !SQLDA           !
    sqldabc: 3536
    sqln: 44
    sqld: 3
    SQLVARБ0Ц.sqltype:   496
    SQLVARБ0Ц.sqlind: 0,
    SQLVARБ0Ц.sqllen:     4,
    sqlvarБ0Ц.sqldata:
          +00000000  000000c8                             !   H            !
    SQLVARБ0Ц.sqlname.length:     2
    sqlvarБ0Ц.sqlname.data:
          +00000000  c9c4                                 !ID              !
    SQLVARБ1Ц.sqltype:   449
    SQLVARБ1Ц.sqlind: 0,
    SQLVARБ1Ц.sqllen:   200,
    sqlvarБ1Ц.sqldata:
          +00000000  00069581 9485f1f0 40404040 40404040  !  name10        !
          +00000010  40404040 40404040 40404040 40404040  !                !
          +00000020  40404040 40404040 40404040 40404040  !                !
          +00000030  40404040 40404040 40404040 40404040  !                !
          +00000040  40404040 40404040 40404040 40404040  !                !
          +00000050  40404040 40404040 40404040 40404040  !                !
          +00000060  40404040 40404040 40404040 40404040  !                !
          +00000070  40404040 40404040 40404040 40404040  !                !
          +00000080  40404040 40404040 40404040 40404040  !                !
          +00000090  40404040 40404040 40404040 40404040  !                !
          +000000a0  40404040 40404040 40404040 40404040  !                !
          +000000b0  40404040 40404040 40404040 40404040  !                !
          +000000c0  40404040 40404040                    !                !
    SQLVARБ1Ц.sqlname.length:     4
    sqlvarБ1Ц.sqlname.data:
          +00000000  d5c1d4c5                             !NAME            !
    SQLVARБ2Ц.sqltype:   497
    SQLVARБ2Ц.sqlind: 0,
    SQLVARБ2Ц.sqllen:     4,
    sqlvarБ2Ц.sqldata:
          +00000000  00000005                             !                !
    SQLVARБ2Ц.sqlname.length:     7
    sqlvarБ2Ц.sqlname.data:
          +00000000  e3c5e2e3 f1c9c4                      !TEST1ID         !
    error_sqlstate: tracing the sqlerrmc
    SQLCA is
          +00000000  e2d8d3c3 c1404040 00000088 fffffdee  !SQLCA      h  ЩЬ!
          +00000010  001e0009 e3c5e2e3 c3e2e3d9 f20004c5  !    TESTCSTR2  E!
          +00000020  c1c9e200 05e3c5e2 e3f30004 c5c1c9e2  !AIS  TEST3  myscheme!
          +00000030  00000000 00000000 00000000 00000000  !                !
          +00000040  00000000 00000000 00000000 00000000  !                !
          +00000050  00000000 00000000 d8e2d8c9 d5e24040  !        QSQINS  !
          +00000060  f5f0f2c4 00000000 00000000 00000000  !502D            !
          +00000070  00000000 00000000 40404040 40404040  !                !
          +00000080  404040f2 f3f5f0f3                    !   23503        !
    APRW: insert_string is INSERT INTO  "myscheme"."TEST3" ("ID", "NAME", "TEST2ID") VALUES(?, ?, ?)
    ------------ Sqlda for INSERT (APRW:2) -----------
    sqldaid:
          +00000000  e2d8d3c4 c1400040                    !SQLDA           !
    sqldabc: 3536
    sqln: 44
    sqld: 3
    SQLVARБ0Ц.sqltype:   496
    SQLVARБ0Ц.sqlind: 0,
    SQLVARБ0Ц.sqllen:     4,
    sqlvarБ0Ц.sqldata:
          +00000000  000000c9                             !   I            !
    SQLVARБ0Ц.sqlname.length:     2
    sqlvarБ0Ц.sqlname.data:
          +00000000  c9c4                                 !ID              !
    SQLVARБ1Ц.sqltype:   449
    SQLVARБ1Ц.sqlind: 0,
    SQLVARБ1Ц.sqllen:   200,
    sqlvarБ1Ц.sqldata:
          +00000000  00069581 9485f1f1 40404040 40404040  !  name11        !
          +00000010  40404040 40404040 40404040 40404040  !                !
          +00000020  40404040 40404040 40404040 40404040  !                !
          +00000030  40404040 40404040 40404040 40404040  !                !
          +00000040  40404040 40404040 40404040 40404040  !                !
          +00000050  40404040 40404040 40404040 40404040  !                !
          +00000060  40404040 40404040 40404040 40404040  !                !
          +00000070  40404040 40404040 40404040 40404040  !                !
          +00000080  40404040 40404040 40404040 40404040  !                !
          +00000090  40404040 40404040 40404040 40404040  !                !
          +000000a0  40404040 40404040 40404040 40404040  !                !
          +000000b0  40404040 40404040 40404040 40404040  !                !
          +000000c0  40404040 40404040                    !                !
    SQLVARБ1Ц.sqlname.length:     4
    sqlvarБ1Ц.sqlname.data:
          +00000000  d5c1d4c5                             !NAME            !
    SQLVARБ2Ц.sqltype:   497
    SQLVARБ2Ц.sqlind: 0,
    SQLVARБ2Ц.sqllen:     4,
    sqlvarБ2Ц.sqldata:
          +00000000  000000c8                             !   H            !
    SQLVARБ2Ц.sqlname.length:     7
    sqlvarБ2Ц.sqlname.data:
          +00000000  e3c5e2e3 f2c9c4                      !TEST2ID         !
    error_sqlstate: tracing the sqlerrmc
    SQLCA is
          +00000000  e2d8d3c3 c1404040 00000088 fffffdee  !SQLCA      h  ЩЬ!
          +00000010  001e0009 e3c5e2e3 c3e2e3d9 f20004c5  !    TESTCSTR2  E!
          +00000020  c1c9e200 05e3c5e2 e3f30004 c5c1c9e2  !AIS  TEST3  myscheme!
          +00000030  00000000 00000000 00000000 00000000  !                !
          +00000040  00000000 00000000 00000000 00000000  !                !
          +00000050  00000000 00000000 d8e2d8c9 d5e24040  !        QSQINS  !
          +00000060  f5f0f2c4 00000000 00000000 00000000  !502D            !
          +00000070  00000000 00000000 40404040 40404040  !                !
          +00000080  404040f2 f3f5f0f3                    !   23503        !
    APRW: insert_string is INSERT INTO  "myscheme"."TEST3" ("ID", "NAME", "TEST2ID") VALUES(?, ?, ?)
    ------------ Sqlda for INSERT (APRW:2) -----------
    sqldaid:
          +00000000  e2d8d3c4 c1400040                    !SQLDA           !
    sqldabc: 3536
    sqln: 44
    sqld: 3
    SQLVARБ0Ц.sqltype:   496
    SQLVARБ0Ц.sqlind: 0,
    SQLVARБ0Ц.sqllen:     4,
    sqlvarБ0Ц.sqldata:
          +00000000  000000ca                             !   Х            !
    SQLVARБ0Ц.sqlname.length:     2
    sqlvarБ0Ц.sqlname.data:
          +00000000  c9c4                                 !ID              !
    SQLVARБ1Ц.sqltype:   449
    SQLVARБ1Ц.sqlind: 0,
    SQLVARБ1Ц.sqllen:   200,
    sqlvarБ1Ц.sqldata:
          +00000000  00069581 9485f1f2 40404040 40404040  !  name12        !
          +00000010  40404040 40404040 40404040 40404040  !                !
          +00000020  40404040 40404040 40404040 40404040  !                !
          +00000030  40404040 40404040 40404040 40404040  !                !
          +00000040  40404040 40404040 40404040 40404040  !                !
          +00000050  40404040 40404040 40404040 40404040  !                !
          +00000060  40404040 40404040 40404040 40404040  !                !
          +00000070  40404040 40404040 40404040 40404040  !                !
          +00000080  40404040 40404040 40404040 40404040  !                !
          +00000090  40404040 40404040 40404040 40404040  !                !
          +000000a0  40404040 40404040 40404040 40404040  !                !
          +000000b0  40404040 40404040 40404040 40404040  !                !
          +000000c0  40404040 40404040                    !                !
    SQLVARБ1Ц.sqlname.length:     4
    sqlvarБ1Ц.sqlname.data:
          +00000000  d5c1d4c5                             !NAME            !
    SQLVARБ2Ц.sqltype:   497
    SQLVARБ2Ц.sqlind: 0,
    SQLVARБ2Ц.sqllen:     4,
    sqlvarБ2Ц.sqldata:
          +00000000  000000c8                             !   H            !
    SQLVARБ2Ц.sqlname.length:     7
    sqlvarБ2Ц.sqlname.data:
          +00000000  e3c5e2e3 f2c9c4                      !TEST2ID         !
    error_sqlstate: tracing the sqlerrmc
    SQLCA is
          +00000000  e2d8d3c3 c1404040 00000088 fffffdee  !SQLCA      h  ЩЬ!
          +00000010  001e0009 e3c5e2e3 c3e2e3d9 f20004c5  !    TESTCSTR2  E!
          +00000020  c1c9e200 05e3c5e2 e3f30004 c5c1c9e2  !AIS  TEST3  myscheme!
          +00000030  00000000 00000000 00000000 00000000  !                !
          +00000040  00000000 00000000 00000000 00000000  !                !
          +00000050  00000000 00000000 d8e2d8c9 d5e24040  !        QSQINS  !
          +00000060  f5f0f2c4 00000000 00000000 00000000  !502D            !
          +00000070  00000000 00000000 40404040 40404040  !                !
          +00000080  404040f2 f3f5f0f3                    !   23503        !
    APRW: insert_string is INSERT INTO  "myscheme"."TEST3" ("ID", "NAME", "TEST2ID") VALUES(?, ?, ?)
    ------------ Sqlda for INSERT (APRW:2) -----------
    sqldaid:
          +00000000  e2d8d3c4 c1400040                    !SQLDA           !
    sqldabc: 3536
    sqln: 44
    sqld: 3
    SQLVARБ0Ц.sqltype:   496
    SQLVARБ0Ц.sqlind: 0,
    SQLVARБ0Ц.sqllen:     4,
    sqlvarБ0Ц.sqldata:
          +00000000  000000cb                             !   И            !
    SQLVARБ0Ц.sqlname.length:     2
    sqlvarБ0Ц.sqlname.data:
          +00000000  c9c4                                 !ID              !
    SQLVARБ1Ц.sqltype:   449
    SQLVARБ1Ц.sqlind: 0,
    SQLVARБ1Ц.sqllen:   200,
    sqlvarБ1Ц.sqldata:
          +00000000  00069581 9485f1f3 40404040 40404040  !  name13        !
          +00000010  40404040 40404040 40404040 40404040  !                !
          +00000020  40404040 40404040 40404040 40404040  !                !
          +00000030  40404040 40404040 40404040 40404040  !                !
          +00000040  40404040 40404040 40404040 40404040  !                !
          +00000050  40404040 40404040 40404040 40404040  !                !
          +00000060  40404040 40404040 40404040 40404040  !                !
          +00000070  40404040 40404040 40404040 40404040  !                !
          +00000080  40404040 40404040 40404040 40404040  !                !
          +00000090  40404040 40404040 40404040 40404040  !                !
          +000000a0  40404040 40404040 40404040 40404040  !                !
          +000000b0  40404040 40404040 40404040 40404040  !                !
          +000000c0  40404040 40404040                    !                !
    SQLVARБ1Ц.sqlname.length:     4
    sqlvarБ1Ц.sqlname.data:
          +00000000  d5c1d4c5                             !NAME            !
    SQLVARБ2Ц.sqltype:   497
    SQLVARБ2Ц.sqlind: 0,
    SQLVARБ2Ц.sqllen:     4,
    sqlvarБ2Ц.sqldata:
          +00000000  000000c8                             !   H            !
    SQLVARБ2Ц.sqlname.length:     7
    sqlvarБ2Ц.sqlname.data:
          +00000000  e3c5e2e3 f2c9c4                      !TEST2ID         !
    error_sqlstate: tracing the sqlerrmc
    SQLCA is
          +00000000  e2d8d3c3 c1404040 00000088 fffffdee  !SQLCA      h  ЩЬ!
          +00000010  001e0009 e3c5e2e3 c3e2e3d9 f20004c5  !    TESTCSTR2  E!
          +00000020  c1c9e200 05e3c5e2 e3f30004 c5c1c9e2  !AIS  TEST3  myscheme!
          +00000030  00000000 00000000 00000000 00000000  !                !
          +00000040  00000000 00000000 00000000 00000000  !                !
          +00000050  00000000 00000000 d8e2d8c9 d5e24040  !        QSQINS  !
          +00000060  f5f0f2c4 00000000 00000000 00000000  !502D            !
          +00000070  00000000 00000000 40404040 40404040  !                !
          +00000080  404040f2 f3f5f0f3                    !   23503        !
    APRW: insert_string is INSERT INTO  "myscheme"."TEST3" ("ID", "NAME", "TEST2ID") VALUES(?, ?, ?)
    ------------ Sqlda for INSERT (APRW:2) -----------
    sqldaid:
          +00000000  e2d8d3c4 c1400040                    !SQLDA           !
    sqldabc: 3536
    sqln: 44
    sqld: 3
    SQLVARБ0Ц.sqltype:   496
    SQLVARБ0Ц.sqlind: 0,
    SQLVARБ0Ц.sqllen:     4,
    sqlvarБ0Ц.sqldata:
          +00000000  000000cc                             !   Й            !
    SQLVARБ0Ц.sqlname.length:     2
    sqlvarБ0Ц.sqlname.data:
          +00000000  c9c4                                 !ID              !
    SQLVARБ1Ц.sqltype:   449
    SQLVARБ1Ц.sqlind: 0,
    SQLVARБ1Ц.sqllen:   200,
    sqlvarБ1Ц.sqldata:
          +00000000  00069581 9485f1f4 40404040 40404040  !  name14        !
          +00000010  40404040 40404040 40404040 40404040  !                !
          +00000020  40404040 40404040 40404040 40404040  !                !
          +00000030  40404040 40404040 40404040 40404040  !                !
          +00000040  40404040 40404040 40404040 40404040  !                !
          +00000050  40404040 40404040 40404040 40404040  !                !
          +00000060  40404040 40404040 40404040 40404040  !                !
          +00000070  40404040 40404040 40404040 40404040  !                !
          +00000080  40404040 40404040 40404040 40404040  !                !
          +00000090  40404040 40404040 40404040 40404040  !                !
          +000000a0  40404040 40404040 40404040 40404040  !                !
          +000000b0  40404040 40404040 40404040 40404040  !                !
          +000000c0  40404040 40404040                    !                !
    SQLVARБ1Ц.sqlname.length:     4
    sqlvarБ1Ц.sqlname.data:
          +00000000  d5c1d4c5                             !NAME            !
    SQLVARБ2Ц.sqltype:   497
    SQLVARБ2Ц.sqlind: 0,
    SQLVARБ2Ц.sqllen:     4,
    sqlvarБ2Ц.sqldata:
          +00000000  000000c8                             !   H            !
    SQLVARБ2Ц.sqlname.length:     7
    sqlvarБ2Ц.sqlname.data:
          +00000000  e3c5e2e3 f2c9c4                      !TEST2ID         !
   RDIN: fread failed for mi = 2
   CPGDRL: read intentseq failed. errcode is 81112102.
PSET: ROLLBACK
PSET: success is 0
 CEXPC: connect to s66666ff
 CLOS: setRepeatCopy is 0
 CPCLOS: success is 0. retcode is 15.
 CLOS: activate = 1
 CLOS: status   = -1
 CLOS: lastrun = 2006-04-06-15.32.23.278279
 CLOS: lastsuccess = 2006-04-06-15.09.23.296967
 CLOS: Synchpoint is  8b3c339c0dc817e60001
 CLOS: synchtime = 2006-04-06-15.04.08.417616
 CLOS: apply_qual = TESTAPPL1
 CLOS: set_name = TESTSET1
 CLOS: sWhosOnFirst = S
 SAT: ASNLOAD is null
 SAT: FULL_REFRESH is null
 SAT: SET_INSERTED = 25
 SAT: SET_DELETED = 0
 SAT: SET_UPDATED = 0
 SAT: SET_REWORKED = 0
 SAT: SET_REJECTED_TRXS = 0
 SAT: STATUS = -1
 SAT: LASTRUN = 2006-04-06-15.32.23.278279
 SAT: LASTSUCCESS = 2006-04-06-15.09.23.296967
 SAT: SYNCHPOINT is 8b3c339c0dc817e60001
 SAT: SYNCHTIME is 2006-04-06-15.04.08.417616
 SAT: SOURCE_ALIAS is s55555ff
 SAT: SOURCE_SERVER is s55555ff
 SAT: SOURCE_OWNER is myscheme
 SAT: SOURCE_TABLE is TEST3
 SAT: TARGET_ALIAS is s66666ff
 SAT: TARGET_SERVER is s66666ff
 SAT: TARGET_OWNER is myscheme
 SAT: TARGET_TABLE is TEST3
 SAT: SQLSTATE is null
 SAT: SQLERRM is null
 SAT: SQLCODE is null
 SAT: SQLERRP is null
 SAT: APPERRM is Apply program could not read from work file.
CS: Stop command has not been issued
CPAPPLY: files_allocated is 5; lf_allocated is -1;            dlf_allocated is -1
DOWN: retcode is 0
CPAPPLY: totalrc is 1. totalcf is 0

7 апр 06, 10:38    [2535019]     Ответить | Цитировать Сообщить модератору
 Re: Replication and RI rules  [new]
riman
Member

Откуда:
Сообщений: 2234
и joblog:

(пробовал кстати и push и pull репликацию - всё одно и тоже)
 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.
7 апр 06, 10:41    [2535036]     Ответить | Цитировать Сообщить модератору
 Re: Replication and RI rules  [new]
ggv
Member

Откуда:
Сообщений: 1810
я вопрос запостил куда следует.
Будем надеяться.
7 апр 06, 11:22    [2535327]     Ответить | Цитировать Сообщить модератору
 Re: Replication and RI rules  [new]
riman
Member

Откуда:
Сообщений: 2234
ggv
я вопрос запостил куда следует.
Будем надеяться.

ggv, спасибо!
7 апр 06, 11:49    [2535569]     Ответить | Цитировать Сообщить модератору
 Re: Replication and RI rules  [new]
vladlogv
Member

Откуда:
Сообщений: 5
riman, у тебя совсем неправильный подход к поиску решений этих проблем. Очевидно куда идет первая вставка и соотв. инсерт не проходит и не может пройти. Если ты считаешь, что это ошибка, нужно обращаться в саппорт. В России это работает, поверь мне. В Штатах работает тоже. Это не SQL Server и не Oracle, самостоятельно искать решения и мучаться не надо - этим занимаются специально обученные люди :)
7 апр 06, 16:33    [2537547]     Ответить | Цитировать Сообщить модератору
 Re: Replication and RI rules  [new]
riman
Member

Откуда:
Сообщений: 2234
vladlogv
riman, у тебя совсем неправильный подход к поиску решений этих проблем. Очевидно куда идет первая вставка и соотв. инсерт не проходит и не может пройти. Если ты считаешь, что это ошибка, нужно обращаться в саппорт. В России это работает, поверь мне. В Штатах работает тоже. Это не SQL Server и не Oracle, самостоятельно искать решения и мучаться не надо - этим занимаются специально обученные люди :)

привет! ещё одним айбиэмером на форуме больше!
:) надо у ильдара проконсультироваться насчет того какая из машин у нас на саппорте, а потом будем к вам звонить :).
7 апр 06, 16:40    [2537592]     Ответить | Цитировать Сообщить модератору
 Re: Replication and RI rules  [new]
vladlogv
Member

Откуда:
Сообщений: 5
скока знакомого народу :)
7 апр 06, 20:36    [2538434]     Ответить | Цитировать Сообщить модератору
 Re: Replication and RI rules  [new]
riman
Member

Откуда:
Сообщений: 2234
Привет всем. В общем с помощью IBM в лице Павла Моисеева нашли обходной путь решения проблемы. Конкретнее:
Каждая таблица выделяется в отдельный subscription set и каждая дочерняя таблица содержит предикат выборки следующего содержания:

id in 
    (select id 
    from <cdtable> 
    where ibmsnap_commitseq>=
        (select synchpoint
        from asn.ibmsnap_pruncntl
        where source_owner=<parenttable_owner>
             and source_table=<parenttable>
        )
     )
т.е. каждый child будет обработан только после того как обработается его parent.

Ну чтож, работает - и ладно! :)
19 апр 06, 10:39    [2578357]     Ответить | Цитировать Сообщить модератору
 Re: Replication and RI rules  [new]
рымынь
Guest
мда. Это уже не смешно:
Вставляем строки в таблицу с nullable FK - OK. Смотрим в cdtable и проверяем значение FK, в которые были вставлены NULL. Некоторые строки действительно NULL, некоторые просто пустые. ЧТО ЗА ФИГНЯ? Никаких преобразований при регистрации таблиц и создании subscription set'ов не делается.
OS/400 V5R2M0.
DPropr v8.1.
25 апр 06, 17:09    [2601563]     Ответить | Цитировать Сообщить модератору
 Re: Replication and RI rules  [new]
riman
Member

Откуда:
Сообщений: 2234
create trigger null_checker
no cascade before insert on <cdtable>
referencing new as n
for each row mode db2sql
when(n.fk='')
set n.fk=null
истерический смех .

А вообще, спасибо member'у kdima71.
26 апр 06, 11:53    [2603877]     Ответить | Цитировать Сообщить модератору
Все форумы / IBM DB2, WebSphere, IMS, U2, etc Ответить