When managing a z/VSE environment, locating the correct system configuration data is essential for stability and performance. In z/VM 5.3, this configuration information is stored in specific files and datasets that the control program references during IPL and runtime. Understanding where these settings live helps operators maintain consistent behavior across sysplex nodes.
The following overview summarizes key aspects of the z/VM 5.3 system config file location, related datasets, and important directory paths that operators should verify during installation and maintenance.
| Component | Typical Location in z/VM 5.3 | Referenced By | Notes |
|---|---|---|---|
| VM Control Program (CP) Parameters | CMS directory file CPDATA or XCPDATA | CP during IPL and reconfiguration | Contains parameters such as MEMORY, CPU, and LAN settings |
| System Parameter File (SPF) for z/VM | Unix System Services file /etc/zvm/config.data | z/VM automation tools | Used by some scripts and installers for default configuration |
| CMS Directory File for Guests | Class DIR entries in user or system directories | Loaders and directory services | Holds mode, memory, and disk definitions for virtual machines |
| Load Module and Macro Libraries | Linklist such as SYS1.LINKLIB and macro libraries | CP and guest systems | Holds executable modules and macros used during configuration |
Understanding VM Control Program Configuration Storage
The VM Control Program (CP) maintains its runtime parameters in CMS directory files, primarily CPDATA and XCPDATA. These directory files are not standard sequential datasets; they reside in the CMS file system and are accessed by CP during system initialization and reconfiguration. Operators should ensure that these files are properly backed up and version-controlled as part of standard change procedures.
In z/VM 5.3, Unix System Services provides an optional unified view of configuration through files such as /etc/zvm/config.data. This location is particularly useful when using automation tools that run under USS and need consistent access to configuration data without switching contexts between CMS and MVS.
Directory Entries and Guest System Definitions
How CMS Directory Files Reference Guests
Each virtual machine is represented by an entry in a CMS directory, which stores mode, memory allocation, and disk layout. These entries allow CP to start guests consistently and enable operators to modify resources without editing multiple datasets manually. Directory files are central to z/VM 5.3 configuration management and should be protected with appropriate RACF profiles.
Directory entries also define network interfaces, consoles, and boot parameters for each guest. Keeping these definitions aligned with actual hardware and sysplex configurations reduces startup failures and improves overall reliability during system maintenance.
Linklists, Load Modules, and Macro Libraries
z/VM 5.3 relies on traditional linklists such as SYS1.LINKLIB to resolve CP macros and load modules required for system initialization. Operators should verify that these linklists point to the correct levels of system macros and that any custom modules are accessible from these libraries.
Consistent naming and ordering in linklists prevent version conflicts when multiple guests or service aids are active. Coordinating changes to these libraries with configuration updates ensures that new parameters are picked up correctly during IPL or dynamic reconfiguration.
Key Recommendations and Operational Takeaways
- Back up CPDATA and XCPDATA regularly and after every change to CP parameters.
- Use RACF or appropriate security managers to control access to CMS directory files.
- Validate linklist contents and macro libraries before IPL or reconfiguration events.
- Document any changes to guest directory entries and keep versioned copies of configuration files.
- Coordinate updates between CP parameters, USS config.data, and MVS load modules to avoid inconsistencies.
FAQ
Reader questions
Where exactly is the main CP parameter dataset or file located on z/VM 5.3?
The primary CP parameters are stored in the CMS directory file CPDATA, with XCPDATA used as an alternate or extended parameter set accessible from Unix System Services.
Can the system configuration for z/VM 5.3 be stored in a regular MVS dataset instead of a CMS directory file?
While some helper configurations can exist in MVS datasets, CP requires its core runtime parameters in CMS directory files such as CPDATA; MVS datasets may hold macros or load modules but are not a substitute for the CP configuration file.
What should I check first if a z/VM 5.3 guest fails to start after a configuration change?
Verify the corresponding CMS directory entry for the guest and confirm that CPDATA or XCPDATA parameters match the intended hardware and memory settings; also ensure that any referenced load modules are available in the system linklist.
Are there any ZFS or USS locations specific to z/VM 5.3 configuration that operators should know about?
Unix System Services provides /etc/zvm/ for configuration data and diagnostic tools, and certain installers may write default config.data there; however, CP continues to rely on CPDATA in the CMS file system for core startup behavior.