Permit me to piggyback on your post.  I ran into a situation back in August, 
while installing 3.1.  
I went through the zOSMF dialogs to put the target datasets on the volumes that 
match our current
configuration.  After completing that step and proceeding to the actual unzip 
and allocate on DASD,
I noticed several datasets were on the wrong volume.  However, once you go past 
the step to pick
the location, you cannot go back into the dialog and update the volser.  It is 
easy enough to move
the dataset to the correct volume.  But I want the volume locations in zOSMF to 
match what is on 
DASD, for future installs/deployments.  The only way I could change the volume 
location was to start
all over again.  

Granted, I should not make the mistake to start with.  But we are talking about 
a large number of
datasets and it is easy for me to miss a few.



"Confidentially doc, I am the wabbit."

Bugs Bunny

Sent with Proton Mail secure email.

On Tuesday, October 7th, 2025 at 12:57 PM, Jousma, David 
<[email protected]> wrote:

> No complaints specifically about the process, this is my second server pac 
> via ZOSMF. A question that maybe Marna or Kurt can answer.
> 
> When going through the configuration, and on the catalog step(using existing 
> catalogs), I can mark all HLQ’s as uncatalogued, except SMPE and my ZFS 
> datasets which is fine. My question though, why not SYS1.? The dialogs do not 
> allow SYS1. to be uncatalogued. I see in the generated batch jobs that the 
> process allocates datasets with the # sign on the end, which are temporarily 
> cataloged, so that they can be loaded, and then eventually renamed to remove 
> the #. So I leave SYS1. as cataloged, and get all kinds of errors saying that 
> the files are already cataloged….duh.
> 
> So I am asking why this is? To get around that, I have to make the datasets 
> SYS1.SYS1 to complete the process, then remove the extra SYS1. Off the front 
> when I am done.
> 
> 
> 
> _______________________________
> 
> Dave Jousma
> 
> Vice President | Director, Technology Engineering
> 
> Fifth Third Bank | 1830 East Paris Ave, SE | Grand Rapids, MI 49546
> 
> 
> 
> 
> 
> 
> 
> This e-mail transmission contains information that is confidential and may be 
> privileged. It is intended only for the addressee(s) named above. If you 
> receive this e-mail in error, please do not read, copy or disseminate it in 
> any manner. If you are not the intended recipient, any disclosure, copying, 
> distribution or use of the contents of this information is prohibited. Please 
> reply to the message immediately by informing the sender that the message was 
> misdirected. After replying, please erase it from your computer system. Your 
> assistance in correcting this error is appreciated.
> 
> 
> ----------------------------------------------------------------------
> 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

Reply via email to