SQLPKG

karenet

Active Member
Hi List,
I'd like to know if I can turn off the SQLPKG creation on my TEST AS400 machine. It seems as though corrupted SQLPKG's causes us grief when we are testing our customized app's on our development machine. If we can 'turn off' the SQLPKG creation, it would cause a performance hit, but in turn we would be able to continue testing our custom app's and not wait for the services to come down so the SQLPKG's can be deleted. Any thought's on how to AVOID the SQLPKG creation, either through 1World or the AS400 side?

K
Xe AS400 SP17.1 Win2000
 
You can turn off the SQL Packages. You MAY see a performance
improvement...we did!

We turned them off a year ago and noticed NO performance problems.

The reason that we had to turn them off was because of severe performance
problems in the AP app. We worked on and off for an entire year with IBM to
resolve the problem and got no where. With SQL packages on there was a
condition that would change sub-second response time to 12 - 15 minute
response time. Full table scans were used (not the index).

It was IBM's suggestion to turn it off.



Dan Doenges
7321 AS 400.






OW 7321, SP 12.5, coexistant, ES 400 V4R5, DS NT
 
To turn AS/400 SQL Packages off on a specific machine:
1. Go to the control panel
2. open the ODBC Data Source Administrator
3. select each Client Access Express ODBC DSN
4. uncheck the box labeled "Enable extended dynamic (package) support)"

After you have the change deployed, delete the SQL packages on the AS/400
(do this during off hours). Do a WRKOBJ for all the *SQLPKG objects. You
will recognize the JDE ones.

At our shop, we control ALL ODBC DSNs through NT policies at user signon.
This way at signon time the users get their ODBC DSNs refreshed to what we
have established (centrally). I think the base JDE way is though package
deployment. So you would have to make the change above on the build box, I
think.



Dan






OW 7321, SP 12.5, coexistant, ES 400 V4R5, DS NT
 
Re: RE: SQLPKG

I wouldn't suggest to turn them off. The AS/400 is badly affected by missing indexes and you should investigate this.

As a rule of thumb I always make sure the sqlpkgs are deleted after each deployment. This corruption occurs when a table or index is changed. It will remember the way the table was before the change !
 
Back
Top