13-13Using the Array Configuration UtilityBecause the ACU reads the entire script file before creating anyarrays, the position of the InitializeAll=Yes property withinthe script is not significant. Continuing the previous example, ifInitializeAll=Yes is specified in the second RAID 5’sdefinition, the ACU initializes all drives before creating the firstRAID 0.Note: If a build/verify is in progress when an array isdeleted, it will automatically be terminated.See The InitializeAll Keyword on page 13-20 for details on the syntaxof the InitializeAll property.Record ModeRecord mode writes an existing controller’s array configuration to aspecified script file, enabling you to create the same configurationby running the ACU in playback mode with the resulting script. Inaddition, record mode lists certain controller properties that can beset in playback mode.Because the ACU supports only a subset of array types availablethrough the CLI and the GUI, it cannot record all the possible arrayconfigurations. If the ACU encounters an array that it cannot createit displays a warning (and records the warning in its log file, if thatswitch is used) and does not record any properties for that array inits script file.The script file is limited to one controller and its associated arrayconfiguration files. Although you can have multiple controllers on asingle system, you cannot record all of the controllers and theirassociated array configurations in one file. To record multiplecontrollers, use the ACU record mode once for each individualcontroller. Your end result will be multiple files on the same diskettewith one file corresponding to each controller.Determining Build/Verify/Clear StatusWhen using playback mode to create an array, you can specifywhether to wait for an array’s initial build/verify or clear tocomplete or to continue while the build/verify or clear proceeds inthe background. If you instruct the ACU to continue (Wait=No),
