/* dasd_diag */

/*?
 * Text: "%s: A 64-bit DIAG call failed\n"
 * Severity: Warning
 * Parameter:
 *   @1: bus ID of the DASD
 * Description:
 * 64-bit DIAG calls require a 64-bit z/VM version.
 * User action:
 * Use z/VM 5.2 or later or set the sysfs 'use_diag' attribute of the DASD to 0
 * to switch off DIAG.
 */

/*?
 * Text: "%s: Accessing the DASD failed because of an incorrect format (rc=%d)\n"
 * Severity: Warning
 * Parameter:
 *   @1: bus ID of the DASD
 *   @2: return code
 * Description:
 * The format of the DASD is not correct.
 * User action:
 * Check the device format. For details about the return code see the
 * section about the INITIALIZE function for DIAGNOSE Code X'250'
 * in "z/VM CP Programming Services". If you cannot resolve the error, note
 * the return code and contact your support organization.
 */

/*?
 * Text: "%s: New DASD with %ld byte/block, total size %ld KB%s\n"
 * Severity: Informational
 * Parameter:
 *   @1: bus ID of the DASD
 *   @2: bytes per block
 *   @3: size
 *   @4: access mode
 * Description:
 * A DASD with the indicated block size and total size has been set online.
 * If the DASD is configured as read-only to the real or virtual hardware,
 * the message includes an indication of this hardware access mode. The
 * hardware access mode is independent from the 'readonly' attribute of
 * the device in sysfs.
 * User action:
 * None.
 */

/*?
 * Text: "%s: DIAG ERP failed with rc=%d\n"
 * Severity: Warning
 * Parameter:
 *   @1: bus ID of the DASD
 *   @2: return code
 * Description:
 * An error in the DIAG processing could not be recovered by the error
 * recovery procedure (ERP) of the DIAG discipline.
 * User action:
 * Note the return code, check for related I/O errors, and report this problem
 * to your support organization.
 */

/*?
 * Text: "%s: DIAG initialization failed with rc=%d\n"
 * Severity: Warning
 * Parameter:
 *   @1: bus ID of the DASD
 *   @2: return code
 * Description:
 * Initializing the DASD with the DIAG discipline failed. Possible reasons for
 * this problem are that the device has a device type other than FBA or ECKD,
 * or has a block size other than one of the supported sizes:
 * 512 byte, 1024 byte, 2048 byte, or 4096 byte.
 * User action:
 * Ensure that the device can be written to and has a supported device type
 * and block size. For details about the return code see the section about
 * the INITIALIZE function for DIAGNOSE Code X'250' in "z/VM CP Programming
 * Services". If you cannot resolve the error, note the error code and contact
 * your support organization.
 */

/*?
 * Text: "%s: Device type %d is not supported in DIAG mode\n"
 * Severity: Warning
 * Parameter:
 *   @1: bus ID of the DASD
 *   @2: device type
 * Description:
 * Only DASD of type FBA and ECKD are supported in DIAG mode.
 * User action:
 * Set the sysfs 'use_diag' attribute of the DASD to 0 and try again to access
 * the DASD.
 */

/*?
 * Text: "Discipline %s cannot be used without z/VM\n"
 * Severity: Informational
 * Parameter:
 *   @1: discipline name
 * Description:
 * The discipline that is specified with the dasd= kernel or module parameter
 * is only available for Linux instances that run as guest operating
 * systems of the z/VM hypervisor.
 * User action:
 * Remove the unsupported discipline from the parameter string.
 */

/*?
 * Text: "%s: The access mode of a DIAG device changed to read-only"
 * Severity: Warning
 * Parameter:
 *   @1: bus ID of the DASD
 * Description:
 * A device changed its access mode from writeable to
 * read-only while in use.
 * User action:
 * Set the device offline, ensure that the device is configured correctly in
 * z/VM, then set the device online again.
 */
