Re: Full System Save issues following O/S Upgrade to 6.1

[CRPence <CRPbottle@xxxxxxxxx>]

On 3/1/11 6:16 AM, Becky.Kangurs@xxxxxxxxxxxxxxxxxxx wrote:
> We run a weekly Full system save using BRMS and at the end of the
> save it backs up BRMS objects but since the recent OS upgrade to 6.1
> it now takes 40 mins to get past "Access path built for member QA1ACG
> file QA1ACG library QUSRBRM". Has anyone experienced this before?

  Probably best to first diagnose the origin for the message.  A trace 
can be used to locate the CPI#### message, then track back to the 
request which effected the access path build\rebuild, or by a call to 
the service provider since presumably the effect is unexpected.

  If there is a request to perform "maintenance" as part of the control 
group [i.e. effect of STRMNTBRM] then perhaps for RGZPFM processing; but 
by naming, that file appears to be CG [Control Group] data.  The message 
could instead be the side-effect of query activity, for which iNav 
database query tools or STRDBMON might assist.  If the access path had 
been invalid but should be maintained *immed, then the message should 
occur only once, though if the file is defined with maint(*rebld) such 
that maintenance is always during open\rebuild then the message would 
occur every time; such that possibly the maintenance attribute for the 
file is suspect.

Regards, Chuck