mats_thunholm
Active Member
Dear JDElist,
I have run into a 'strange' problem and I wonder if someone else out there
have had a similar
problem.
We are running OW B7332, SP11.3, ES AS400
I have put a RUNUBE cmd into a CL program that is launched from the IBM
AS400 scheduler
(WRKJOBSCDE). This CL program is then running the RUNUBE statement every 15
minutes to
extract waiting records from F986113 ...............
I have had some problems with that job in the past but after a 'full
package build' and deployment
(PRODB733FA) the RUNUBE worked fine......
but suddenly one morning (about two weeks after the package build )when I
came to my office
it didn't work any longer (just like that, when nobody
is awake during the night, everybody is sleeping, the program stops.......)
I got the following error in the log:
The OW log,
8307 Mon Jul 2 14:03:20 2001 JDEKRNL_O/C/JDB_RST2263
JDB9900318 - Failed to find table information in TAM using RDB
8307 Mon Jul 2 14:03:20 2001 JDEKRNL_O/C/JDB_RST329
JDB9900299 - Failed to create global table specs for F90005
8307 Mon Jul 2 14:03:20 2001 JDEKRNL_O/C/JDB_RST1073
JDB9900307 - Failed to find table specifications
8307 Mon Jul 2 14:03:20 2001 JDEKRNL_O/C/JDB_RQ11431
JDB3100007 - Failed to get valid table specifications
8307 Mon Jul 2 14:03:21 2001 JDBDRV_O/C/DBDRVSQL963
OS40002001 - Error Type: SQL sqlcode: -113õ++!·¤
Actually I don't know what table F90005 is doing, I can't find it anywhere.
---------------------------------------------------------------------------------------------------------------------------------------------------------
The AS400 log:
40 03/07/01 14:03:06 DBDR B7332SYS *STMT DBDR
From module . . . . . . . . : DBDRV
From procedure . . . . . . : DBFetch
Statement . . . . . . . . . : 9
To module . . . . . . . . . : DBDRV
To procedure . . . . . . . : DBFetch
Statement . . . . . . . . . : 9
Message . . . . : Pointer not set for location referenced.
Cause . . . . . : A pointer was used, either directly or as a basing
pointer, that has not been set to an address.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
I tried to replace the specs(I did a save of the specs after the pack
PRODB733FA, just in case....), but it didn't work,
I redeployed package PRODB733FA, but it didn't work (why did it work after
the build and deploy of PRODB733FA
and not after only the deploy of PRODB733FA, is the build doing something
more that is not included in a deploy) ??
So, it seems that the this specific RUNUBE decided by it self to stop
working........
If somebody else have had a similar case, please can you share your
experience.
Best regards
Mats Thunholm
---------------------------------------------------------------------------------------------------------
Mats Thunholm
APBiotech
Uppsala, Sweden
+46 18 612 0646 (w), +46 70 666 5819 (m)
[email protected]
---------------------------------------------------------------------------------------------------------
B7332 SP11.3, AS400 V4R5
Mats Thunholm
APBiotech
Uppsala, Sweden
I have run into a 'strange' problem and I wonder if someone else out there
have had a similar
problem.
We are running OW B7332, SP11.3, ES AS400
I have put a RUNUBE cmd into a CL program that is launched from the IBM
AS400 scheduler
(WRKJOBSCDE). This CL program is then running the RUNUBE statement every 15
minutes to
extract waiting records from F986113 ...............
I have had some problems with that job in the past but after a 'full
package build' and deployment
(PRODB733FA) the RUNUBE worked fine......
but suddenly one morning (about two weeks after the package build )when I
came to my office
it didn't work any longer (just like that, when nobody
is awake during the night, everybody is sleeping, the program stops.......)
I got the following error in the log:
The OW log,
8307 Mon Jul 2 14:03:20 2001 JDEKRNL_O/C/JDB_RST2263
JDB9900318 - Failed to find table information in TAM using RDB
8307 Mon Jul 2 14:03:20 2001 JDEKRNL_O/C/JDB_RST329
JDB9900299 - Failed to create global table specs for F90005
8307 Mon Jul 2 14:03:20 2001 JDEKRNL_O/C/JDB_RST1073
JDB9900307 - Failed to find table specifications
8307 Mon Jul 2 14:03:20 2001 JDEKRNL_O/C/JDB_RQ11431
JDB3100007 - Failed to get valid table specifications
8307 Mon Jul 2 14:03:21 2001 JDBDRV_O/C/DBDRVSQL963
OS40002001 - Error Type: SQL sqlcode: -113õ++!·¤
Actually I don't know what table F90005 is doing, I can't find it anywhere.
---------------------------------------------------------------------------------------------------------------------------------------------------------
The AS400 log:
40 03/07/01 14:03:06 DBDR B7332SYS *STMT DBDR
From module . . . . . . . . : DBDRV
From procedure . . . . . . : DBFetch
Statement . . . . . . . . . : 9
To module . . . . . . . . . : DBDRV
To procedure . . . . . . . : DBFetch
Statement . . . . . . . . . : 9
Message . . . . : Pointer not set for location referenced.
Cause . . . . . : A pointer was used, either directly or as a basing
pointer, that has not been set to an address.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
I tried to replace the specs(I did a save of the specs after the pack
PRODB733FA, just in case....), but it didn't work,
I redeployed package PRODB733FA, but it didn't work (why did it work after
the build and deploy of PRODB733FA
and not after only the deploy of PRODB733FA, is the build doing something
more that is not included in a deploy) ??
So, it seems that the this specific RUNUBE decided by it self to stop
working........
If somebody else have had a similar case, please can you share your
experience.
Best regards
Mats Thunholm
---------------------------------------------------------------------------------------------------------
Mats Thunholm
APBiotech
Uppsala, Sweden
+46 18 612 0646 (w), +46 70 666 5819 (m)
[email protected]
---------------------------------------------------------------------------------------------------------
B7332 SP11.3, AS400 V4R5
Mats Thunholm
APBiotech
Uppsala, Sweden