Lines Matching refs:be

19 The z/VM guest on which you want to access this API needs to be configured in
21 IUCV *MONITOR statement in its user entry. If the monitor DCSS to be used is
45 always start at 0 and be at least 64MB in size.
62 which can be loaded via the modprobe command, or it can be compiled into the
65 kernel, the kernel parameter "monreader.mondcss=<DCSS NAME>" can be specified
87 which data should be collected. This can be done by the CP command MONITOR
92 After loading the module, a char device will be created along with the device
97 If your distribution does not support udev, a device node will not be created
100 numbers can be found in /sys/class/misc/monreader/dev.
102 <major>:<minor>. The device node can be created via the mknod command, enter
104 to be created.
130 of the record set in the monitor DCSS. The start and end address can be used
133 correctly (domain 1, record 13), i.e. it can be used to determine the record
138 be found here (z/VM 5.1): http://www.vm.ibm.com/pubs/mon510/index.html
151 There may be more than one combination of MCE and corresponding record set
154 Any received data must be considered invalid until a complete set was
158 The maximum size of a data set can be as large as the size of the
160 The size of the monitor DCSS will be printed into syslog after loading the
176            read with 0 size is valid but subsequent records may be missing.
178 In the last case (EOVERFLOW) there may be missing data, in the first two cases
179 (EIO, EFAULT) there will be missing data. It's up to the application if it will
187 cannot be established. In this case errno will be set to EIO and an error
188 message with an IPUSER SEVER code will be printed into syslog. The IPUSER SEVER
193 As soon as the device is opened, incoming messages will be accepted and they