I agree in theory, but a) PERFSVM was running just before I increased the size of the minidisks, and gets the DCSS size too small message after increasing the size of the minidisk. And b) increasing the size of the DCSS hasn¹t won me any points with PERFSVM or *MONITOR either. What I¹m seeing now is:
10:12:00 FCXPMN446E Incomplete monitor data: DCSS size too small 10:13:00 FCXPMN446E Incomplete monitor data: DCSS size too small 10:14:00 FCXPMN446E Incomplete monitor data: DCSS size too small 10:15:00 FCXPMN446E Incomplete monitor data: DCSS size too small 10:16:00 FCXPMN446E Incomplete monitor data: DCSS size too small 10:23:51 FCXPMN443E IUCV connection severed by *MONITOR, rc = 44 10:26:31 FCXPMN440E Error 41 loading MONITOR segment MONDCSS 10:38:48 FCXPMN446E Incomplete monitor data: DCSS size too small 10:41:20 FCXCMS801A RC 1 for CMSSTOR OBTAIN from 80DFD5CE for 1765179 DWs 10:41:22 FCXPER327A Insufficient storage: I/O Device data may be incomplete 10:42:17 FCXPER327A Insufficient storage: I/O Device data may be incomplete 10:44:13 FCXCMS801A RC 1 for CMSSTOR OBTAIN from 80DFD5CE for 1765179 DWs 10:44:15 FCXPER327A Insufficient storage: I/O Device data may be incomplete 10:45:30 FCXPMN443E IUCV connection severed by *MONITOR, rc = 44 13:37:33 FCXPMN443E IUCV connection severed by *MONITOR, rc = 44 13:44:54 FCXCMS801A RC 1 for CMSSTOR OBTAIN from 80DFD5CE for 1765179 DWs 13:44:56 FCXPER327A Insufficient storage: I/O Device data may be incomplete MONDCSS is currently defined as: 0057 MONDCSS CPDCSS N/A 09000 0AFFF SC R 00002 N/A N/A Q NSS USERS MONDCSS shows: FILE FILENAME FILETYPE CLASS 0057 MONDCSS CPDCSS R SYSTEM PERFSVM I can no longer get PERFSVM to run on either system. I¹ve tried about everything I can think of on one system, and have left the other untouched, other than the larger 191 minidisk. Neither work, and both fail in similar ways.... Any additional thoughts? Otherwise, I¹m going to have to open an ETR. -- .~. Robert P. Nix Mayo Foundation /V\ RO-OE-5-55 200 First Street SW / ( ) \ 507-284-0844 Rochester, MN 55905 ^^-^^ ----- "In theory, theory and practice are the same, but ³Join the story... Ride Ural.² in practice, theory and practice are different." On 7/11/07 1:12 PM, "Kris Buelens" <[EMAIL PROTECTED]> wrote: > This is not related the size of a minidisk, but the size of a DisContiguous > Saved Segment, a piece of virtual storage, in this case shared between CP > (that stores the performance data in it ) and PERFSVM that retrieves them out > of it. > > It is created by issuing DEFSEG MONDCSS sss-eee SC (I'm a bit uncertain > about "SC") > followed by SAVESEG MONDCSS > sss end eee are the hex starting page address and ending address > You can issue Q NSS NAME MONDCSS MAP to find its current size. > To have the new version active, all users of it should be stopped. Q NSS > USERS MONDCSS will show the current users, CP itself will not be listed, but > if you issue MONITOR STOP, CP will stop using it too. > > 2007/7/11, RPN01 <[EMAIL PROTECTED]>: >> We've been running PerfKit for quite some time, and the 191 disk got too >> small for the trend data. I brought down both PERFSVM virtual machines (we >> run two CECs and CSE), created new, larger disks, and set up the PERFSVM's to >> use them, and then xautolog'ed both PERFSVMs. >> >> Now, both are getting the message "FCXPMN446E Incomplete monitor data: DCSS >> size too small". >> >> The current data was just copied from one disk to another; what does the DCSS >> size have to do with that? If the DCSS is too small, what is the yardstick >> needed to decide how big to make it?
