Re: BI / Reporting tools

A Couple things on the reporting tool. This will be used in our production system and it's intended for end-users,
some report will need to be setup initially set by the developers with scheduling capability to automatically
run reports.

Forgot to add that we are in version 7.1

Jamal, the utmost importance is, if you plan on using your production server for reporting as well you must be aware that:

Preserving the production system is the most important thing. Any bad SQL statement can bring the biggest systems to it's knees.

Most importantly:
1.) Once the database servers are turned on, it is up to the iSeries administrators to limit access. Default access is allow all, if user has a valid iSeries user profile. This includes any SQL Statement including update.
2.) Bad queries. This is most likely the #1 problem. If you plan on launching any SQL statements on your production database, a veteran DB2 for I DBE should review each statement.

Nearly as important, keep up with the SQL updates. There have been so many updates throughout the years but they are completely ignored. Why because it still works.

(As I speak, one of our legacy programs has been creating an index for an OPNQRYF for 14 hours! Are you freaking kidding me!)

Jim

p.s. Regarding security, I worked once at a company which I was a normal regular user and did not have command line access and no special authorities but the company had no security checks in place. I was able to do everything I can today having full SECOFR authority.