Just poking around found this description of the monitor record:
DESCRIPTIVE NAME - Monitor Sample Record
Domain 10 - Appldata domain
Record 2 - Application Data Sample Record
DESCRIPTION - Application data as found in the application-defined
buffer at the time of this sample interval. A
separate record is generated for each buffer
declared by the virtual machine(s) via the Diagnose
'DC' START operation.
Seems to imply a separate record is generated for each buffer
declared.. I'm not sure what the application data sample is in this
case. Are the records truly duplicates? (the whole record is
absolutely identical, displayable chars or not) Perhaps the
application data needs to be appended to come up with the entire
field?
Scott Rohling
On Thu, Jun 9, 2011 at 8:04 AM, Berry van Sleeuwen <
berry.vansleeu...@xs4all.nl> wrote:
> Hi listers,
>
> I am looking at processing the userrecords in the CP MONITOR for the TCPIP
> stacks. These are in CP MONITOR domain 0A record 02. The data is collected
> though a STARMON stage, basically "PIPE STARMON | locate <selection> | >
> fielid".
>
> Most LPARs have records like I'd expect them but I have found that in one
> LPAR we have duplicate records for subrecordtype 05 for each of the the OSA
> devices.
>
> The CTC's for VSE systems have one record per minute for each VSE system.
> The OSA links have 2 identical records (apart from a slight difference in
> timestamp, a few miliseconds apart). A second IP stack even writes 3
> records
> for every minute.
>
> So basically we see:
> 00:01 VSE1
> 00:01 VSE2
> 00:01 OSA1
> 00:01 OSA2
> 00:01 OSA1
> 00:01 OSA2
> 00:02 ...
>
> What can cause the CP monitor to have these duplicate records?
>
> TIA, Berry.
>
