In my VMPRF automation, I had code to issue CP Q DASD and enable monitoring
only these addresses. Maybe this works for VMPTK too. This code shoule be
part of the code that starts the CP monitor.
/* now get all not-offline dasd and make a RANGE to pass to CP later */
'PIPE CP Q DASD ACTIVE', /* GET all "not-offline" dasd */
'|SPEC W2 1', /* keep only address */
'|JOIN * / /|VAR CUUS' /* get'em all in 1 string */
parse var cuus devs cuus /* get first dasd address */
o_dcuu=x2d(devs); n=1 /* get decimal address of first dasd */
do while cuus^=''
parse var cuus cuu cuus
if o_dcuu+n=x2d(cuu) then n=n+1 /* consecutive address */
else do /* not consecutive: */
if n>1 then do
devs=devs'-'d2x(o_dcuu+n-1,4) /* complete prev range */
n=1
end
devs=devs cuu
o_dcuu=x2d(cuu)
end
end
if n>1 then devs=devs'-'d2x(o_dcuu+n-1,4) /* fill out last range */
'PIPE LITERAL' devs, /* Avoid problem: */
'| SPILL 200', /* FPLCOM062E Command length 243 too long for CP*/
'| CHANGE ""MONITOR SAMP ENA I/O DEVICE "',
'| CP',
'| NFIND HCP 6240I_', /* ignore mon already active msgs */
'| CONSOLE'
2007/5/23, Dave Jones <[EMAIL PROTECTED]>:
Hi, Ed.
Are these DASD displayed when you do a Q DASD ALL? If they are, are they
marked as free or off line? Who "owns" these DASD?
[EMAIL PROTECTED] wrote:
> Hi
>
> I am surprised to see the PTK
> is reporting on DASD devices that are not part of our z/VM system.
>
> Yes, these DASD devices are (probably) available in the IOGEN but should
> be filtered by what is in getting past the SYSTEM CONFIG ?
>
> These same devices do NOT display in a Q DASD command.
>
> I suspect that this is why I had to resize the size of the Monitor DCSS:
>
> MONITOR SAMPLE CONFIG SIZE 350
>
> Any ideas on how to prevent PTK from looking at these devices ?
>
> I don't think that I have remote monitoring setup so that it could be
> doing this.
>
> Thanks.
>
>
> Ed Rohr
> Freightliner LLC
> Portland, Oregon
> (503) 745-9027
>
>
--
DJ
V/Soft
--
Kris Buelens,
IBM Belgium, VM customer support
