2 * Text: "Starting the data collection for %s failed with rc=%d\n"
8 * The specified data collection module used the z/VM diagnose call
9 * DIAG 0xDC to start writing data. z/VM returned an error and the data
10 * collection could not start. If the return code is 5, your z/VM guest
11 * virtual machine is not authorized to write data records.
13 * If the return code is 5, ensure that your z/VM guest virtual machine's
14 * entry in the z/VM directory includes the OPTION APPLMON statement.
15 * For other return codes see the section about DIAGNOSE Code X'DC'
16 * in "z/VM CP Programming Services".
20 * Text: "Stopping the data collection for %s failed with rc=%d\n"
26 * The specified data collection module used the z/VM diagnose call DIAG 0xDC
27 * to stop writing data. z/VM returned an error and the data collection
30 * See the section about DIAGNOSE Code X'DC' in "z/VM CP Programming Services".
34 * Text: "Starting a new OS data collection failed with rc=%d\n"
39 * After a CPU hotplug event, the record size for the running operating
40 * system data collection is no longer correct. The appldata_os module tried
41 * to start a new data collection with the correct record size but received
42 * an error from the z/VM diagnose call DIAG 0xDC. Any data collected with
43 * the current record size might be faulty.
45 * Start a new data collection with the cappldata_os module. For information
46 * about starting data collections see "Device Drivers, Features, and
47 * Commands". For information about the return codes see the section about
48 * DIAGNOSE Code X'DC' in "z/VM CP Programming Services".
52 * Text: "Stopping a faulty OS data collection failed with rc=%d\n"
57 * After a CPU hotplug event, the record size for the running operating
58 * system data collection is no longer correct. The appldata_os module tried
59 * to stop the faulty data collection but received an error from the z/VM
60 * diagnose call DIAG 0xDC. Any data collected with the current record size
63 * Try to restart appldata_os monitoring. For information about stopping
64 * and starting data collections see "Device Drivers, Features, and
65 * Commands". For information about the return codes see the section about
66 * DIAGNOSE Code X'DC' in "z/VM CP Programming Services".
70 * Text: "Maximum OS record size %i exceeds the maximum record size %i\n"
76 * The OS record size grows with the number of CPUs and is adjusted by the
77 * appldata_os module in response to CPU hotplug events. For more than 110
78 * CPUs the record size would exceed the maximum record size of 4024 bytes
79 * that is supported by the z/VM hypervisor. To prevent the maximum supported
80 * record size from being exceeded while data collection is in progress,
81 * you cannot load the appldata_os module on Linux instances that are
82 * configured for a maximum of more than 110 CPUs.
84 * If you do not want to collect operating system data, you can ignore this
85 * message. If you want to collect operating system data, reconfigure your
86 * Linux instance to support less than 110 CPUs.