The actual Service Processor that is running the Application Service has been rebooted and now the information wrt the Virtual Volume Groups is being displayed as expected. Yes this was using a "bigger hammer" than necessary, but it did the job.
So obviously, as mentioned, some of the information for the VVG was being cached and not updated. The fact that I could get the 'correct' information from the cmd line did give me a degree of comfort
that everything was correct.
Thank you for the quick Response
Cheers