RE: QSYS/QQQOOOPLNC

- He can see the access path recommendations.  (Shoots most of that 
security by obscurity theory.)
- He cannot see the statements that generated the access path 
recommendations because of the message in the subject line.  Why would 
that be a risk?
- He cannot generate the recommended index.  I think it has to do with the 
strange method IBM has of generating the recommended index.
You get the run sql scripts window.  And, instead of a simple create view, 
they'll do something like:
/* Create a procedure to establish processing options for the 
statement(s). */
CREATE PROCEDURE CLIDIVF.QAUGDBIX_BLLL90()
LANGUAGE SQL
NOT DETERMINISTIC
MODIFIES SQL DATA
CALLED ON NULL INPUT
SET OPTION SRTSEQ = *HEX
CREATE INDEX CLIDIVF.BLLL90 ON CLIDIVF.BLL (BLPROD ASC, BLNUM ASC)
PAGESIZE(64);

/* Creating index CLIDIVF.BLLL90 */
CALL CLIDIVF.QAUGDBIX_BLLL90;

/* Deleting procedure CLIDIVF.QAUGDBIX_BLLLL90 */
DROP PROCEDURE CLIDIVF.QAUGDBIX_BLLL90;

I assume it goes through these gyrations just to set the SRTSEQ.

This errors out with:
SQL0551 - Not authorized to object CRTPGM in QSYS type *CMD.
Which, I assume, is because CREATE PROCEDURE creates a C program under the 
covers.

I guess the pro to these limitations is that he can then copy/paste these 
statements into a source member and use our change management software. 
Thus not losing the definition to the new logical file, or index.

Rob Berendt