RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

A separate bug was requested for this documentation issue.

+++ This bug was initially created as a clone of Bug #681219 +++

Quoting Red Hat Enterprise Linux 6 Installation Guide Edition 1.0, section 26.3. Installation network parameters:

http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/ch-parmfiles-Installation_network_parameters.html

DASD=
 Defines the DASD or range of DASDs to configure for the installation. For a detailed description of the syntax, refer to the dasd_mod device driver module option described in the chapter on the DASD device driver in Linux on System z Device Drivers, Features, and Commands on Red Hat Enterprise Linux 6. 

[snip]

 For example: 
DASD=eb1c,0.0.a000-0.0.a003,eb10-eb14(diag),0.0.ab1c(ro:diag)


Because the DASD= config in CMSCONFFILE is sourced by the shell, the right hand side needs to be quoted to avoid errors reading the metacharacters '(' and ')'. For example:

DASD='eb1c,0.0.a000-0.0.a003,eb10-eb14(diag),0.0.ab1c(ro:diag)'

For completeness, why not single-quote all CMSCONFFILE parameters given by example, both in "Installation network parameters" and "Sample parameter file and CMS configuration file"?

I haven't checked, but this error probably appears in the Installation Guide for other RHEL versions.

Thanks for bringing this to our attention, Philip.

The DASD example was fixed in build 1.0-43 of the guide, and the remaining examples have been corrected for build 1.0-45.