Here is what I encountered.
"^" is the only character on my keyboard that resembles the "check mark" symbol.
Under
Deployment Checklist
^ Specify the properties for this deployment
^ Select the software to deploy
^ Select the objective for this deployment
^ Check for missing SYSMODs
. View missing SYSMOD report
^ Configure the deployment
^ Define the job settings. z/OSMF created the deployment summary and jobs.
. View the deployment summary'
^ Submit deployment jobs.
^ Perform workflows.
^ Specify the properties for the target software instance.
>From what I am showing above, I had completed all of the tasks. It was at
this point that I discovered that a few of the datasets were not allocated on
the volumes that I wanted. As for summary reports, sorting, and filtering
options to check on dataset placement, I did do that. Unfortunately, I am
human and I make mistakes.
When I selected "Configure the deployment" task to change the placement of the
datasets,
I received a warning pop-up window which stated.
You are about to return to a previously completed step. If you make any
changes,
the information you provided in subsequent steps might be discarded, and any
workflow instances you created for this deployment will be deleted. Do you
want
to continue?
Since all of the tasks were completed, I did not want to start over.
"Confidentially doc, I am the wabbit."
Bugs Bunny
Sent with Proton Mail secure email.
On Tuesday, October 7th, 2025 at 3:05 PM, Kurt Quackenbush <[email protected]>
wrote:
> > However, once you go past the step to pick the location, you cannot go back
> > into the dialog and update the volser.
>
>
> That's just not true. If you're still in the Configuration wizard you
> certainly can click the "Back" button at the bottom of the page to step
> backwards in the wizard and make changes on prior steps. If you've already
> generated the jobs but have not run any yet, then you can go back to the
> Configuration wizard and step through making changes to move data sets to
> different volumes for example. However, if you've run some of the jobs, then
> it gets messy and you have to cleanup whatever those jobs have done before
> you go back to modify the configuration and regenerate the jobs.
>
> When z/OSMF generates the deployment jobs it also creates a Deployment
> Summary to describe the changes that will be made by the generated jobs. My
> recommendation is to always review the Deployment Summary very carefully to
> make sure you're happy with your configuration. With all the information
> provided and the sorting and filtering capabilities of z/OSMF hopefully
> you'll spot mistakes in this summary, such as choosing the wrong volume, so
> you can go back and update the Configuration and regenerate the jobs before
> running them.
>
> Kurt Quackenbush
> IBM | z/OS SMP/E and z/OSMF Software Management | [email protected]
>
> Chuck Norris never uses CHECK when he applies PTFs.
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
