×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I have often seen issues with SQL processes after an OS for various
releases. Assuming you have the latest Database group on (which it sounds
like you have) then my experience is that often the SQL package is the
culprit.
I have found that running a post upgrade STROBJCVN often helps as it usually
causes the packages to be converted (or whatever happens under the covers).
I think the upgrade documentation covers this and refers to recreation of
the SQL package.
The object(s) should get converted at first touch if object conversion was
run but this doesn't always seem to be the case.
Deleting the SQL package is often the easy fix, although I always take a
save beforehand to ensure I can put things back how they were. Don't be like
some sites I have seen and get over enthusiastic and delete the model
packages supplied by IBM :)
This may not be the cause in your particular case, but it something I have
struck a number of times so it may be of some help.
Regards
Evan Harris
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Peter Dow (ML)
Sent: Thursday, 10 January 2008 9:33 a.m.
To: Midrange Systems Technical Discussion
Subject: 5.3 to 5.4 upgrade issues
Hi Everyone,
A customer of mine just upgraded from v5r3 to v5r4 over the weekend.
Since then there have been occasional odd problems, like
- CPF4204 (Internal failure occurred in query processor.) from an RPGLE
program and some SQL statements processed with RUNSQLSTM. Recompiled
the logical file they all had in common and the problem went away.
- SQL0900 (Application process not in a connected state.) from an
SQLRPGLE program that does several consecutive SQL UPDATE statements.
Recompiled the program (making sure it was COMMIT(*NONE)) and the
problem went away.
What took place during the upgrade that would cause these problems? Is
there some background file or program conversion that didn't get to
these files or programs?
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.