Re: Weird problem -- JAVA400-L

Wayne,

did you check the properties of the database server jobs? default settings 
don't wrap the joblog, if it reaches its maximum size, then the connection 
will die and you might get the mentioned pointer error.

Dieter

On Thursday 03 April 2003 23:05, you wrote:
> Dieter,
>
> We run the same program from PC by using type 4 driver (Toolbox).  We run
> the program on AS/400 by using native driver (type 2) which runs much fast
> than from PC.  But as I mentioned, the problem was not consistence.  Only
> once a while, it will occur, no matter what type of drivers I use.  It
> sounds like the error was related to the status (activities) on AS/400 at
> the time of the program was running.
>
> Wayne
>
> -----Original Message-----
> From: Dieter.Bender@xxxxxxxxxxx [mailto:Dieter.Bender@xxxxxxxxxxx]
> Sent: Thursday, April 03, 2003 3:47 PM
> To: Java Programming on and around the iSeries / AS400
> Subject: Re: Weird problem
>
>
> Hi,
>
> did you trie the type 4 driver (aka toolbox driver)?
>
> Dieter
>
> On Wednesday 02 April 2003 22:10, you wrote:
> > Hi, all,
> >
> > I have had a weird problem when I run a Java batch program on AS/400
> > (V5R1). I use native JDBC for data connection.  The error occurred
>
> randomly
>
> > at different time and different stage of the batch processes.  Most of
> > time, the batch completed no problems at all, but sometimes, it fails. 
> > It seems to me that it is something to do with the system resources.  But
> > I could not figure out exactly what cause the errors.  I have attached
> > the joblog.  the error start with MSGID: MCH3601,  type: Escape, Message:
> > Pointer not set for location referenced.
> >
> > Does any one have any ideas about this error?
> >
> > Also, I have another question about the message in this joblog (it does
>
> not
>
> > cause any problem yet).  The message is:
> > Message . . . . :   Job 030659/QUSER/QSQSRVR used for SQL server mode
> > processing.
> > Cause . . . . . :   A Structured Query Language (SQL) statement was
> > executed while running in SQL server mode.  SQL statements for this
> > connection or thread will be processed in job
> > 030659/QUSER/QSQSRVR.
> > Technical description . . . . . . . . :   SQL server mode was requested
> > by either setting the SQL server mode job attribute, or by setting the
> > server mode environment
> >                                        attribute via the SQL Call Level
> > Interface.  When running in this mode, SQL statements are processed by a
> > separate job, which runs under the                     user profile
> > specified for the connection. The thread identifier is 2 and the
>
> connection
>
> > is to Relational Database WILM620.  If the Relational
> > Database name is *N, this means that all connections for the thread will
> > use the same job.
> >
> > Is there any problem to run SQL statement in SQL server mode?  My SQL
> > statement does not specify the settings.  Maybe by default, it use SQL
> > server mode?  If not run in SQL server mode, what other options I have
> > and how to set the options, if any?
> >
> > Thanks.
> >
> >
> >  <<QPJOBLOG031352.txt>>
> >
> > Wayne
> > _______________________________________________
> > This is the Java Programming on and around the iSeries / AS400
> > (JAVA400-L) mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/java400-l
> > or email: JAVA400-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/java400-l.

-- 
mfG

Dieter Bender


DV-Beratung Dieter Bender
Wetzlarerstr. 25
35435 Wettenberg
Tel. +49 641 9805855
Fax +49 641 9805856
www.bender-dv.de