On my sandbox system needless to say running DB2 statistics is hit or miss at best.
While researching something else today this caught my eye under ARSMAINT parameters:
(-r parm)
Runs database statistics, which causes the database manager to optimize application group index data and make access to information as efficient as possible. To optimize the database, schedule the ARSMAINT program after the following activities:
After a table is loaded.
After an index is physically created.
After a table space is reorganized if inline statistics were not collected.
After you run extensive updates, deletions, or insertions in a tablespace.
After you run any of the following utilities without collecting inline statistics:
RECOVER TABLESPACE
REBUILD INDEX
REORG INDEX
Before you run REORG with the OFFPOSLIMIT, INDREFLIMIT, or LEAFDISTLIMIT options.
That certainly looked interesting, so I ran the following batch job:
//TMP1 EXEC PGM=IKJEFT01,
// DYNAMNBR=200
//SYSPROC DD DSN=SYS1.SBPXEXEC,DISP=SHR
//*
//SYSTSPRT DD SYSOUT=*
//*
//SYSTSIN DD *
oshell logger -d1 starting arsmaint run
oshell /usr/lpp/ars/V8R5M0/bin/arsmaint -I ARCH850 -r
oshell logger -d1 ending arsmaint run
//*
As soon as you submit this go to the DA screen in SDSF ... quite a bit of activity in DB2 and ARSSOCKD including starting the "WLM-ESTABLISHED ADDRESS SPACE FOR RUNNING DB2 UTILITIES STORED PROCEDURES."
I'm going to use this as part of my regression bucket when testing.
Ed
