Re: Table in use message

The fact that the messages are contradictory makes the problem hart to
solve. The first message is wrong, because I chased out all users, shut
down tcp servers and canceled everything in WRKOBJLCK

Sorry, I misspeled SQL.

CRPence wrote:

On 27-Oct-2011 13:22 , Raul A. Jager W. wrote:

Joblog (I added the message number after the ---->)

3 > ADDPFCST FILE(PFI520/SOLPUB_KSP) TYPE(*REFCST) KEY(CLIENTE)
CST(cliente_en_addres) PRNFILE(B/ADDRES_NCL) PRNKEY(NCLIE)
DLTRULE(*RESTRICT) UPDRULE(*RESTRICT)
CPF3202 Está utilizándose el archivo ADDRES_NCL de la biblioteca B.
CPD32B1 La restricción no puede eliminarse del archivo SOLPUB_KSP.
CPI32B1 Se ha eliminado la restricción.
CPF32B4 Recuperación satisfactoria de restricción de archivo físico.
CPF32B0 La restricción no puede a¦adirse al archivo SOLPUB_KSP.

I am not sure what [¿probable defect?] has the msgCPD32B1 RC05 being
logged, but the outcome contradicts the confusing implication of that
diagnostic condition being logged. That is, the later messages show the
failed add-constraint activity was successfully backed-out, and finally that the constraint was not added.

The first error diagnosing the condition preventing the add activity is the CPF3202 for the parent file B/ADDRESS_NCL. That message is
telling you that the parent file can not be allocated exclusively to
your job, which is required for the requested structural definitional
changes of the two database files; i.e. to establish referential
constraints betwixt. That message diagnoses the condition which needs
to be resolved first, before any additional attempt to add the
constraint can continue; i.e. obtaining all locks across the dbf
networks is what occurs first, before\in establishing the referential
relationships.

I get the same messages if I try to add the constraint from QSL.

I am not sure what QSL is, but again, eliminating the allocation
which leads to the CPF3202 is the key to resolution.

We are at V7.1, and we have a machine at V5.3 and other at V5.2 using
the files via DDM.

Testing the message flow at v5r3 for the parent file allocated to
another job might show by comparison, the [in]consistency of the
add-constraint activity.

I copy the dump below, but it may refer to the next constraint that did
work fine.

5770SS1 V7R1M0 041023 VOLCADO DE IBM i 001991/QSECOFR/QPADEV0002 27/10/11 17:18:35 PAGINA 1
PARÁMETROS DMPSYSOBJ
OBJ- QDBDBDROBJ* CONTEXT- PFI520
TIPO- 19 SUBTIPO-D4
TIPO OBJETO- ESPACIO *DBRCVR
NOMBRE- QDBDBDROBJFPUBL_K_F_PFI520 TIPO- 19 SUBTIPO- D4
BIBLIOTECA- PFI520 TIPO- 04 SUBTIPO- 01
CREACIÓN- 14/09/11 11:20:51 TAMA#O- 0000002000
PROPIETARIO- QDBSHR TIPO- 08 SUBTIPO- 01
ATRIBUTOS- 0800 DIRECCIÓN- 21BAEDD32D 000000
ATRIBUTOS ESPACIO-
000000 00FFF000 00000074 19D4D8C4 C2C4C2C4 D9D6C2D1 C6D7E4C2 D36DD26D C66DD7C6 * 0 È MQDBDBDROBJFPUBL_K_F_PF*
000020 C9F5F2F0 40404040 E0020000 00000000 00001000 00100000 00000000 00000000 *I520 \ *
000040 00000000 00000000 0F804358 33000400 00000000 00000000 00000000 00000000 * äì *
000060 00000000 00000000 00000000 00000000 00FFF000 * 0 *
ESPACIO-
000000 00000000 00000000 12D70BFE 26001900 00000000 00000000 0F804358 33000400 * P Ú äì *
000020 D8C4C2D4 E5D9C6D9 40404700 01000000 00000000 00000000 00000000 00000000 *QDBMVRFR å *
000040 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 * *
LÍNEAS 000060 A 00017F IGUAL QUE ANTERIOR
000180 00000000 00000000 00000000 00000000 00000000 00000000 3A2D0900 E2001900 * S *
0001A0 C6D7E4C2 D36DD26D C66DC6D7 E4C2D36D D26DC640 C6D7E4C2 D36DD26D C640D7C6 *FPUBL_K_F_FPUBL_K_F FPUBL_K_F PF*
0001C0 C9F5F2F0 40404040 40404040 40404040 4040D7C7 D4C1C2C3 40404040 C6858388 *I520 PGMABC Fech*
0001E0 81A24081 4097A482 93898381 994081A5 89A296A2 406040D7 969940D2 A29740A8 *as a publicar avisos - Por Ksp y*
000200 40868583 88814040 40404040 4040D7C6 4040C4F0 F0F0F0F6 F0F0F0F0 F2F0F0F0 * fecha PF D0000600002000*
000220 F0F0F0F0 F0F0F2F6 F0F0F0F0 F0F0F0F0 F0F0F000 00004040 40404040 40404040 *0000002600000000000 *
000240 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 * *
000260 00000000 00000000 00000000 00000000 80000000 00000000 21BAEDD3 2D001290 * [ÒL °*
000280 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 * *
LÍNEAS 0002A0 A 000FFF IGUAL QUE ANTERIOR
.PUNTEROS-
000000 OBJETO DIRECCIONADO DESTRUIDO-
000010 SYP 04 01 PFI520 CONTEXTO MAQUINA 0000 0000 *LIB
000190 OBJETO DIRECCIONADO DESTRUIDO-
000270 SPP 19 D4 QDBDBDROBJFPUBL_K_F_PFI520 04 01 PFI520 00000290 0000
DATOS OIR-
NINGUNO
FIN DE VUELCO

That is logging a failed request to RNMOBJ or MOVOBJ started at
11.20.51 on 2011-0914 against the file FPUBL_K_F_ in library PFI520; I
would guess, "RNMOBJ PFI520/FPUBL_K_F_ *FILE FPUBL_K_F" was the request.
The file that was being tracked under recovery apparently is gone;
there may be a "damage ignored" message for a DLTF that was issued
since, against the file of the new\renamed name. AFaIK the orphan
recovery object can be destroyed by performing the following script:

crtsrcpf pfi520/FPUBL_K_F_
! if above completes with success [may be a long delay], then:
dltf pfi520/FPUBL_K_F_

Regards, Chuck