Start the z Systems Development and Test Environment

The sample runzpdt script available in the ConfigGuideSample directory can be used to start z Systems Development and Test Environment with any z/OS® distribution. This script is described in Starting the z Systems Development and Test Environment.

When you run this z/OS 2.2 ADCD, the load parameter that is specified with the -l switch (the -l is a lowercase L) must correspond to a valid load parameter defined in the distribution. For information about the load parameters available with this distribution, and which major subsystems they start, see z/OS 2.2 ADCD for z Systems Development and Test Environment.

Note: Each loadparm in this z/OS ADCD has an associated parmlib member that is named COMMNDxx, where xx corresponds to a LOADxx loadparm. That parmlib member defines all of the subsystems that are started when that loadparm is IPLed. The COMMNDxx parmlib member runs an SVTAMxx procedure, which uses a VTAMxx parmlib member to start another set of subsystems. You can see all of the subsystems that are started for all loadparms by looking at the COMMNDxx and VTAMxx parmlib members in ADCD.*.PARMLIB.

The first time this z/OS distribution is started, start z Systems Development and Test Environment with the CS loadparm. This loadparm initiates a cold start, and does not start other subsystems. After you verify basic z/OS capabilities, you can then customize the system by using the instructions in Configuring a working z/OS system and create and start different loadparms as needed. As with any z/OS system, warm starts are less disruptive and preserve the JES job spool. Initiate® a warm start when possible.

When you perform an IPL of the supplied z/OS distribution system for the first time, you might see some errors during the IPL process. For example, SMF files might be full. If you are prompted with the IXC420D REPLY I TO INITIALIZE SYSPLEX ADCDPL, . . .message, respond with R 0,I, that is, the letter R, a blank, a zero, a comma, and the letter I.