Hello,

I'm currently upgrading from zOS 2.4 to zOS 3.1.  This is not the first time upgrading OS, but is the first time using ZOSMF to accomplish this.  I'm working on the Deployment and was all the way through the Volume and Storage Classes section and noticed there is no way for me to add an SSA.  

I'm using the 'Use Existing Master Catalog'  objective.  We normally have our target datasets on a specific volume and they are indirectly cataloged.  I was able to do this via the panels.  We also have an SSA for these indirectly cataloged datasets with a HLQ of SYZ31.  The SYZ31 alias would be defined in our new Usercat and the Usercat is connected to our existing Mastercats.  I don't see anywhere that I can specify our SSA?

I looked at some of Kurt's videos and documents and it seems like the SSA is only built for an objective of 'Create a new Master Catalog'?  Is this correct? Would I have to go back to the beginning and change my objective to Create a New Master Catalog?  Can this new MasterCat be a usercat instead of a Master?

Also, on the Data Sets section, we do put our Target and DLIBs on a dedicated volume and have them indirectly cataloged.  In our shop we also have to specify a STORCLAS of (SCNONSMS) so that the ACS routines will be bypassed and the adhoc volume will be honored.  I see there is no way for me to specify a volume and a Storage Class, so at the end, do I just have the JCL created and then go in and edit the JCL to add the STORCLAS(SCNONSMS) and then submit the job via ZOSMF?  Is that doable?

Thanks in advance,

Arlene

Arlene, I'm a little confused about the end result you desire.  You indirectly catalog data sets, yet you also want an SSA pointing to a user catalog?  Would the user catalog be only temporary, or do you intend to keep it connected to your existing master catalog?  When you IPL z/OS 3.1, I assume you will use your existing master catalog, is that correct?  In any case, it is true that z/OSMF will only create temporary catalog aliases (SSAs) if you choose to create a new master catalog.  The aliases simply aren't necessary if using your existing master catalog.  Feel free to generate and examine the JCL for both methods if you want to understand in more detail and compare.  Just be sure not to run any of the generated JCL until you're sure of your choice.

Regarding STORCLAS and volume, z/OSMF does not allow you to specify both, you must choose a volume or to SMS manage the data sets (STORCLAS is a choice if you select to SMS manage).  The generated JCL will call the GIMUNZIP program, and it also does not allow you to specify both a volume and a STORCLAS, so editing the JCL is not really an option.  Sorry.

Hello,

I'm currently upgrading from zOS 2.4 to zOS 3.1.  This is not the first time upgrading OS, but is the first time using ZOSMF to accomplish this.  I'm working on the Deployment and was all the way through the Volume and Storage Classes section and noticed there is no way for me to add an SSA.  

I'm using the 'Use Existing Master Catalog'  objective.  We normally have our target datasets on a specific volume and they are indirectly cataloged.  I was able to do this via the panels.  We also have an SSA for these indirectly cataloged datasets with a HLQ of SYZ31.  The SYZ31 alias would be defined in our new Usercat and the Usercat is connected to our existing Mastercats.  I don't see anywhere that I can specify our SSA?

I looked at some of Kurt's videos and documents and it seems like the SSA is only built for an objective of 'Create a new Master Catalog'?  Is this correct? Would I have to go back to the beginning and change my objective to Create a New Master Catalog?  Can this new MasterCat be a usercat instead of a Master?

Also, on the Data Sets section, we do put our Target and DLIBs on a dedicated volume and have them indirectly cataloged.  In our shop we also have to specify a STORCLAS of (SCNONSMS) so that the ACS routines will be bypassed and the adhoc volume will be honored.  I see there is no way for me to specify a volume and a Storage Class, so at the end, do I just have the JCL created and then go in and edit the JCL to add the STORCLAS(SCNONSMS) and then submit the job via ZOSMF?  Is that doable?

Thanks in advance,

Arlene

Hi Kurt,

Yes, we keep the SSA, it is not temporary.  We have the Target/DLIB indirectly cataloged on specific adhoc volumes (CTGT31/CDLB31) and also have an alias of SYZ31 in our new UserCat that points to these volsers.  So, in SMPE we have the SYZ31.- coded, with no volser.  

I guess for this issue, I can just forget the SSA and use the indirect entries and ZOSMF should create the SMPE entries with the truename and volser, right?

The volser and STORCLAS issue is more of a big deal.  The way our SMS ACS routines are currently set up, I need to specify a STORCLAS(SCNONSMS) in order for my hard-coded volser to be honored.  If I just have the VOLSER with no STORCLAS(SCNONSMS), then SMS will intercept my allocation and put it into an SMS pool and will not honor the volser.

What happens if after the JCL is created, I update the JCL and then go back into ZOSMF and submit the job?  How does it prevent me from doing this?

Thanks,

Arlene

Arlene, I'm a little confused about the end result you desire.  You indirectly catalog data sets, yet you also want an SSA pointing to a user catalog?  Would the user catalog be only temporary, or do you intend to keep it connected to your existing master catalog?  When you IPL z/OS 3.1, I assume you will use your existing master catalog, is that correct?  In any case, it is true that z/OSMF will only create temporary catalog aliases (SSAs) if you choose to create a new master catalog.  The aliases simply aren't necessary if using your existing master catalog.  Feel free to generate and examine the JCL for both methods if you want to understand in more detail and compare.  Just be sure not to run any of the generated JCL until you're sure of your choice.

Regarding STORCLAS and volume, z/OSMF does not allow you to specify both, you must choose a volume or to SMS manage the data sets (STORCLAS is a choice if you select to SMS manage).  The generated JCL will call the GIMUNZIP program, and it also does not allow you to specify both a volume and a STORCLAS, so editing the JCL is not really an option.  Sorry.

Hello,

I'm currently upgrading from zOS 2.4 to zOS 3.1.  This is not the first time upgrading OS, but is the first time using ZOSMF to accomplish this.  I'm working on the Deployment and was all the way through the Volume and Storage Classes section and noticed there is no way for me to add an SSA.  

I'm using the 'Use Existing Master Catalog'  objective.  We normally have our target datasets on a specific volume and they are indirectly cataloged.  I was able to do this via the panels.  We also have an SSA for these indirectly cataloged datasets with a HLQ of SYZ31.  The SYZ31 alias would be defined in our new Usercat and the Usercat is connected to our existing Mastercats.  I don't see anywhere that I can specify our SSA?

I looked at some of Kurt's videos and documents and it seems like the SSA is only built for an objective of 'Create a new Master Catalog'?  Is this correct? Would I have to go back to the beginning and change my objective to Create a New Master Catalog?  Can this new MasterCat be a usercat instead of a Master?

Also, on the Data Sets section, we do put our Target and DLIBs on a dedicated volume and have them indirectly cataloged.  In our shop we also have to specify a STORCLAS of (SCNONSMS) so that the ACS routines will be bypassed and the adhoc volume will be honored.  I see there is no way for me to specify a volume and a Storage Class, so at the end, do I just have the JCL created and then go in and edit the JCL to add the STORCLAS(SCNONSMS) and then submit the job via ZOSMF?  Is that doable?

Thanks in advance,

Arlene

>  I can just forget the SSA and use the indirect entries, and ZOSMF should create the SMPE entries with the truename and volser, right?

That is correct, for indirectly cataloged data sets the DDDEF entry identifies the true name and the volume.

Editing the JCL will not help because it is the GIMUNZIP program that allocates the new data sets and it will not accept both a volume and a storage class.  Sorry to say I think you'll have to update your ACS routines.

Hi Kurt,

Yes, we keep the SSA, it is not temporary.  We have the Target/DLIB indirectly cataloged on specific adhoc volumes (CTGT31/CDLB31) and also have an alias of SYZ31 in our new UserCat that points to these volsers.  So, in SMPE we have the SYZ31.- coded, with no volser.  

I guess for this issue, I can just forget the SSA and use the indirect entries and ZOSMF should create the SMPE entries with the truename and volser, right?

The volser and STORCLAS issue is more of a big deal.  The way our SMS ACS routines are currently set up, I need to specify a STORCLAS(SCNONSMS) in order for my hard-coded volser to be honored.  If I just have the VOLSER with no STORCLAS(SCNONSMS), then SMS will intercept my allocation and put it into an SMS pool and will not honor the volser.

What happens if after the JCL is created, I update the JCL and then go back into ZOSMF and submit the job?  How does it prevent me from doing this?

Thanks,

Arlene

Arlene, I'm a little confused about the end result you desire.  You indirectly catalog data sets, yet you also want an SSA pointing to a user catalog?  Would the user catalog be only temporary, or do you intend to keep it connected to your existing master catalog?  When you IPL z/OS 3.1, I assume you will use your existing master catalog, is that correct?  In any case, it is true that z/OSMF will only create temporary catalog aliases (SSAs) if you choose to create a new master catalog.  The aliases simply aren't necessary if using your existing master catalog.  Feel free to generate and examine the JCL for both methods if you want to understand in more detail and compare.  Just be sure not to run any of the generated JCL until you're sure of your choice.

Regarding STORCLAS and volume, z/OSMF does not allow you to specify both, you must choose a volume or to SMS manage the data sets (STORCLAS is a choice if you select to SMS manage).  The generated JCL will call the GIMUNZIP program, and it also does not allow you to specify both a volume and a STORCLAS, so editing the JCL is not really an option.  Sorry.

Hello,

I'm currently upgrading from zOS 2.4 to zOS 3.1.  This is not the first time upgrading OS, but is the first time using ZOSMF to accomplish this.  I'm working on the Deployment and was all the way through the Volume and Storage Classes section and noticed there is no way for me to add an SSA.  

I'm using the 'Use Existing Master Catalog'  objective.  We normally have our target datasets on a specific volume and they are indirectly cataloged.  I was able to do this via the panels.  We also have an SSA for these indirectly cataloged datasets with a HLQ of SYZ31.  The SYZ31 alias would be defined in our new Usercat and the Usercat is connected to our existing Mastercats.  I don't see anywhere that I can specify our SSA?

I looked at some of Kurt's videos and documents and it seems like the SSA is only built for an objective of 'Create a new Master Catalog'?  Is this correct? Would I have to go back to the beginning and change my objective to Create a New Master Catalog?  Can this new MasterCat be a usercat instead of a Master?

Also, on the Data Sets section, we do put our Target and DLIBs on a dedicated volume and have them indirectly cataloged.  In our shop we also have to specify a STORCLAS of (SCNONSMS) so that the ACS routines will be bypassed and the adhoc volume will be honored.  I see there is no way for me to specify a volume and a Storage Class, so at the end, do I just have the JCL created and then go in and edit the JCL to add the STORCLAS(SCNONSMS) and then submit the job via ZOSMF?  Is that doable?

Thanks in advance,

Arlene

Kurt,

Thanks for the replies. I'll go and talk to our Storage team and will move forward.

Arlene

>  I can just forget the SSA and use the indirect entries, and ZOSMF should create the SMPE entries with the truename and volser, right?

That is correct, for indirectly cataloged data sets the DDDEF entry identifies the true name and the volume.

Editing the JCL will not help because it is the GIMUNZIP program that allocates the new data sets and it will not accept both a volume and a storage class.  Sorry to say I think you'll have to update your ACS routines.

Hi Kurt,

Yes, we keep the SSA, it is not temporary.  We have the Target/DLIB indirectly cataloged on specific adhoc volumes (CTGT31/CDLB31) and also have an alias of SYZ31 in our new UserCat that points to these volsers.  So, in SMPE we have the SYZ31.- coded, with no volser.  

I guess for this issue, I can just forget the SSA and use the indirect entries and ZOSMF should create the SMPE entries with the truename and volser, right?

The volser and STORCLAS issue is more of a big deal.  The way our SMS ACS routines are currently set up, I need to specify a STORCLAS(SCNONSMS) in order for my hard-coded volser to be honored.  If I just have the VOLSER with no STORCLAS(SCNONSMS), then SMS will intercept my allocation and put it into an SMS pool and will not honor the volser.

What happens if after the JCL is created, I update the JCL and then go back into ZOSMF and submit the job?  How does it prevent me from doing this?

Thanks,

Arlene

Arlene, I'm a little confused about the end result you desire.  You indirectly catalog data sets, yet you also want an SSA pointing to a user catalog?  Would the user catalog be only temporary, or do you intend to keep it connected to your existing master catalog?  When you IPL z/OS 3.1, I assume you will use your existing master catalog, is that correct?  In any case, it is true that z/OSMF will only create temporary catalog aliases (SSAs) if you choose to create a new master catalog.  The aliases simply aren't necessary if using your existing master catalog.  Feel free to generate and examine the JCL for both methods if you want to understand in more detail and compare.  Just be sure not to run any of the generated JCL until you're sure of your choice.

Regarding STORCLAS and volume, z/OSMF does not allow you to specify both, you must choose a volume or to SMS manage the data sets (STORCLAS is a choice if you select to SMS manage).  The generated JCL will call the GIMUNZIP program, and it also does not allow you to specify both a volume and a STORCLAS, so editing the JCL is not really an option.  Sorry.

Hello,

I'm currently upgrading from zOS 2.4 to zOS 3.1.  This is not the first time upgrading OS, but is the first time using ZOSMF to accomplish this.  I'm working on the Deployment and was all the way through the Volume and Storage Classes section and noticed there is no way for me to add an SSA.  

I'm using the 'Use Existing Master Catalog'  objective.  We normally have our target datasets on a specific volume and they are indirectly cataloged.  I was able to do this via the panels.  We also have an SSA for these indirectly cataloged datasets with a HLQ of SYZ31.  The SYZ31 alias would be defined in our new Usercat and the Usercat is connected to our existing Mastercats.  I don't see anywhere that I can specify our SSA?

I looked at some of Kurt's videos and documents and it seems like the SSA is only built for an objective of 'Create a new Master Catalog'?  Is this correct? Would I have to go back to the beginning and change my objective to Create a New Master Catalog?  Can this new MasterCat be a usercat instead of a Master?

Also, on the Data Sets section, we do put our Target and DLIBs on a dedicated volume and have them indirectly cataloged.  In our shop we also have to specify a STORCLAS of (SCNONSMS) so that the ACS routines will be bypassed and the adhoc volume will be honored.  I see there is no way for me to specify a volume and a Storage Class, so at the end, do I just have the JCL created and then go in and edit the JCL to add the STORCLAS(SCNONSMS) and then submit the job via ZOSMF?  Is that doable?

Thanks in advance,

Arlene

Arlene, I apologize, I should have verified before I responded.  I was wrong, GIMUNZIP does accept both a volume and a storclas.  Sorry about that.  So, if you carefully edit the generated JCL to add the storclass to each <ARCHDEF> statement, GIMUNZIP will accept both and pass both to allocation.

https://www.ibm.com/docs/en/zos/3.1.0?topic=routine-gimunzip-package-control-tags

Kurt,

Thanks for the replies. I'll go and talk to our Storage team and will move forward.

Arlene

>  I can just forget the SSA and use the indirect entries, and ZOSMF should create the SMPE entries with the truename and volser, right?

That is correct, for indirectly cataloged data sets the DDDEF entry identifies the true name and the volume.

Editing the JCL will not help because it is the GIMUNZIP program that allocates the new data sets and it will not accept both a volume and a storage class.  Sorry to say I think you'll have to update your ACS routines.

Hi Kurt,

Yes, we keep the SSA, it is not temporary.  We have the Target/DLIB indirectly cataloged on specific adhoc volumes (CTGT31/CDLB31) and also have an alias of SYZ31 in our new UserCat that points to these volsers.  So, in SMPE we have the SYZ31.- coded, with no volser.  

I guess for this issue, I can just forget the SSA and use the indirect entries and ZOSMF should create the SMPE entries with the truename and volser, right?

The volser and STORCLAS issue is more of a big deal.  The way our SMS ACS routines are currently set up, I need to specify a STORCLAS(SCNONSMS) in order for my hard-coded volser to be honored.  If I just have the VOLSER with no STORCLAS(SCNONSMS), then SMS will intercept my allocation and put it into an SMS pool and will not honor the volser.

What happens if after the JCL is created, I update the JCL and then go back into ZOSMF and submit the job?  How does it prevent me from doing this?

Thanks,

Arlene

Arlene, I'm a little confused about the end result you desire.  You indirectly catalog data sets, yet you also want an SSA pointing to a user catalog?  Would the user catalog be only temporary, or do you intend to keep it connected to your existing master catalog?  When you IPL z/OS 3.1, I assume you will use your existing master catalog, is that correct?  In any case, it is true that z/OSMF will only create temporary catalog aliases (SSAs) if you choose to create a new master catalog.  The aliases simply aren't necessary if using your existing master catalog.  Feel free to generate and examine the JCL for both methods if you want to understand in more detail and compare.  Just be sure not to run any of the generated JCL until you're sure of your choice.

Regarding STORCLAS and volume, z/OSMF does not allow you to specify both, you must choose a volume or to SMS manage the data sets (STORCLAS is a choice if you select to SMS manage).  The generated JCL will call the GIMUNZIP program, and it also does not allow you to specify both a volume and a STORCLAS, so editing the JCL is not really an option.  Sorry.

Hello,

I'm currently upgrading from zOS 2.4 to zOS 3.1.  This is not the first time upgrading OS, but is the first time using ZOSMF to accomplish this.  I'm working on the Deployment and was all the way through the Volume and Storage Classes section and noticed there is no way for me to add an SSA.  

I'm using the 'Use Existing Master Catalog'  objective.  We normally have our target datasets on a specific volume and they are indirectly cataloged.  I was able to do this via the panels.  We also have an SSA for these indirectly cataloged datasets with a HLQ of SYZ31.  The SYZ31 alias would be defined in our new Usercat and the Usercat is connected to our existing Mastercats.  I don't see anywhere that I can specify our SSA?

I looked at some of Kurt's videos and documents and it seems like the SSA is only built for an objective of 'Create a new Master Catalog'?  Is this correct? Would I have to go back to the beginning and change my objective to Create a New Master Catalog?  Can this new MasterCat be a usercat instead of a Master?

Also, on the Data Sets section, we do put our Target and DLIBs on a dedicated volume and have them indirectly cataloged.  In our shop we also have to specify a STORCLAS of (SCNONSMS) so that the ACS routines will be bypassed and the adhoc volume will be honored.  I see there is no way for me to specify a volume and a Storage Class, so at the end, do I just have the JCL created and then go in and edit the JCL to add the STORCLAS(SCNONSMS) and then submit the job via ZOSMF?  Is that doable?

Thanks in advance,

Arlene

Kurt,

No problem, thanks for checking!  

Since I have you, another question on ZOSMF Deployment.  Can I go back and click on a step I already finished at any time?  When I get to the point where I 'View My Deployment Summary' and I see I need to make updates, can I go back to Deployment and directly to the section, say it was 'Data Sets' and modify what is needed and it will still keep the 'Catalogs', 'Volume and Storage Classes' and 'Mount Points' updates and I won't have to do those 3 sections over again?

And if I get done with submitting my Deployment Jobs, can I go back in later and 'Check for Missing SYSMODS'?  Or will that step be closed and I'll be unable to access the step?

Thanks in advance,

Arlene

Arlene, I apologize, I should have verified before I responded.  I was wrong, GIMUNZIP does accept both a volume and a storclas.  Sorry about that.  So, if you carefully edit the generated JCL to add the storclass to each <ARCHDEF> statement, GIMUNZIP will accept both and pass both to allocation.

https://www.ibm.com/docs/en/zos/3.1.0?topic=routine-gimunzip-package-control-tags

Kurt,

Thanks for the replies. I'll go and talk to our Storage team and will move forward.

Arlene

>  I can just forget the SSA and use the indirect entries, and ZOSMF should create the SMPE entries with the truename and volser, right?

That is correct, for indirectly cataloged data sets the DDDEF entry identifies the true name and the volume.

Editing the JCL will not help because it is the GIMUNZIP program that allocates the new data sets and it will not accept both a volume and a storage class.  Sorry to say I think you'll have to update your ACS routines.

Hi Kurt,

Yes, we keep the SSA, it is not temporary.  We have the Target/DLIB indirectly cataloged on specific adhoc volumes (CTGT31/CDLB31) and also have an alias of SYZ31 in our new UserCat that points to these volsers.  So, in SMPE we have the SYZ31.- coded, with no volser.  

I guess for this issue, I can just forget the SSA and use the indirect entries and ZOSMF should create the SMPE entries with the truename and volser, right?

The volser and STORCLAS issue is more of a big deal.  The way our SMS ACS routines are currently set up, I need to specify a STORCLAS(SCNONSMS) in order for my hard-coded volser to be honored.  If I just have the VOLSER with no STORCLAS(SCNONSMS), then SMS will intercept my allocation and put it into an SMS pool and will not honor the volser.

What happens if after the JCL is created, I update the JCL and then go back into ZOSMF and submit the job?  How does it prevent me from doing this?

Thanks,

Arlene

Arlene, I'm a little confused about the end result you desire.  You indirectly catalog data sets, yet you also want an SSA pointing to a user catalog?  Would the user catalog be only temporary, or do you intend to keep it connected to your existing master catalog?  When you IPL z/OS 3.1, I assume you will use your existing master catalog, is that correct?  In any case, it is true that z/OSMF will only create temporary catalog aliases (SSAs) if you choose to create a new master catalog.  The aliases simply aren't necessary if using your existing master catalog.  Feel free to generate and examine the JCL for both methods if you want to understand in more detail and compare.  Just be sure not to run any of the generated JCL until you're sure of your choice.

Regarding STORCLAS and volume, z/OSMF does not allow you to specify both, you must choose a volume or to SMS manage the data sets (STORCLAS is a choice if you select to SMS manage).  The generated JCL will call the GIMUNZIP program, and it also does not allow you to specify both a volume and a STORCLAS, so editing the JCL is not really an option.  Sorry.

Hello,

I'm currently upgrading from zOS 2.4 to zOS 3.1.  This is not the first time upgrading OS, but is the first time using ZOSMF to accomplish this.  I'm working on the Deployment and was all the way through the Volume and Storage Classes section and noticed there is no way for me to add an SSA.  

I'm using the 'Use Existing Master Catalog'  objective.  We normally have our target datasets on a specific volume and they are indirectly cataloged.  I was able to do this via the panels.  We also have an SSA for these indirectly cataloged datasets with a HLQ of SYZ31.  The SYZ31 alias would be defined in our new Usercat and the Usercat is connected to our existing Mastercats.  I don't see anywhere that I can specify our SSA?

I looked at some of Kurt's videos and documents and it seems like the SSA is only built for an objective of 'Create a new Master Catalog'?  Is this correct? Would I have to go back to the beginning and change my objective to Create a New Master Catalog?  Can this new MasterCat be a usercat instead of a Master?

Also, on the Data Sets section, we do put our Target and DLIBs on a dedicated volume and have them indirectly cataloged.  In our shop we also have to specify a STORCLAS of (SCNONSMS) so that the ACS routines will be bypassed and the adhoc volume will be honored.  I see there is no way for me to specify a volume and a Storage Class, so at the end, do I just have the JCL created and then go in and edit the JCL to add the STORCLAS(SCNONSMS) and then submit the job via ZOSMF?  Is that doable?

Thanks in advance,

Arlene

Arlene, yes, you can go back to prior steps in the Deployment Checklist.  Especially while viewing the Deployment Summary if you decide you need to make a change, definitely go back to the Configuration step and make those changes.  If you make a change, on the Data Sets page for example, you are still forced to walk through the remaining steps of the Configuration wizard because it validates as it goes, but z/OSMF should remember your saved configuration so you don't have to redo it entirely from scratch.

Regarding the Check for Missing SYSMODs step, yes, absolutely you can go back and run or rerun those reports, as long as you don't complete the last step of the Checklist, "Specify the properties for the target software instance."

Kurt,

No problem, thanks for checking!  

Since I have you, another question on ZOSMF Deployment.  Can I go back and click on a step I already finished at any time?  When I get to the point where I 'View My Deployment Summary' and I see I need to make updates, can I go back to Deployment and directly to the section, say it was 'Data Sets' and modify what is needed and it will still keep the 'Catalogs', 'Volume and Storage Classes' and 'Mount Points' updates and I won't have to do those 3 sections over again?

And if I get done with submitting my Deployment Jobs, can I go back in later and 'Check for Missing SYSMODS'?  Or will that step be closed and I'll be unable to access the step?

Thanks in advance,

Arlene

Arlene, I apologize, I should have verified before I responded.  I was wrong, GIMUNZIP does accept both a volume and a storclas.  Sorry about that.  So, if you carefully edit the generated JCL to add the storclass to each <ARCHDEF> statement, GIMUNZIP will accept both and pass both to allocation.

https://www.ibm.com/docs/en/zos/3.1.0?topic=routine-gimunzip-package-control-tags

Kurt,

Thanks for the replies. I'll go and talk to our Storage team and will move forward.

Arlene

>  I can just forget the SSA and use the indirect entries, and ZOSMF should create the SMPE entries with the truename and volser, right?

That is correct, for indirectly cataloged data sets the DDDEF entry identifies the true name and the volume.

Editing the JCL will not help because it is the GIMUNZIP program that allocates the new data sets and it will not accept both a volume and a storage class.  Sorry to say I think you'll have to update your ACS routines.

Hi Kurt,

Yes, we keep the SSA, it is not temporary.  We have the Target/DLIB indirectly cataloged on specific adhoc volumes (CTGT31/CDLB31) and also have an alias of SYZ31 in our new UserCat that points to these volsers.  So, in SMPE we have the SYZ31.- coded, with no volser.  

I guess for this issue, I can just forget the SSA and use the indirect entries and ZOSMF should create the SMPE entries with the truename and volser, right?

The volser and STORCLAS issue is more of a big deal.  The way our SMS ACS routines are currently set up, I need to specify a STORCLAS(SCNONSMS) in order for my hard-coded volser to be honored.  If I just have the VOLSER with no STORCLAS(SCNONSMS), then SMS will intercept my allocation and put it into an SMS pool and will not honor the volser.

What happens if after the JCL is created, I update the JCL and then go back into ZOSMF and submit the job?  How does it prevent me from doing this?

Thanks,

Arlene

Arlene, I'm a little confused about the end result you desire.  You indirectly catalog data sets, yet you also want an SSA pointing to a user catalog?  Would the user catalog be only temporary, or do you intend to keep it connected to your existing master catalog?  When you IPL z/OS 3.1, I assume you will use your existing master catalog, is that correct?  In any case, it is true that z/OSMF will only create temporary catalog aliases (SSAs) if you choose to create a new master catalog.  The aliases simply aren't necessary if using your existing master catalog.  Feel free to generate and examine the JCL for both methods if you want to understand in more detail and compare.  Just be sure not to run any of the generated JCL until you're sure of your choice.

Regarding STORCLAS and volume, z/OSMF does not allow you to specify both, you must choose a volume or to SMS manage the data sets (STORCLAS is a choice if you select to SMS manage).  The generated JCL will call the GIMUNZIP program, and it also does not allow you to specify both a volume and a STORCLAS, so editing the JCL is not really an option.  Sorry.

Hello,

I'm currently upgrading from zOS 2.4 to zOS 3.1.  This is not the first time upgrading OS, but is the first time using ZOSMF to accomplish this.  I'm working on the Deployment and was all the way through the Volume and Storage Classes section and noticed there is no way for me to add an SSA.  

I'm using the 'Use Existing Master Catalog'  objective.  We normally have our target datasets on a specific volume and they are indirectly cataloged.  I was able to do this via the panels.  We also have an SSA for these indirectly cataloged datasets with a HLQ of SYZ31.  The SYZ31 alias would be defined in our new Usercat and the Usercat is connected to our existing Mastercats.  I don't see anywhere that I can specify our SSA?

I looked at some of Kurt's videos and documents and it seems like the SSA is only built for an objective of 'Create a new Master Catalog'?  Is this correct? Would I have to go back to the beginning and change my objective to Create a New Master Catalog?  Can this new MasterCat be a usercat instead of a Master?

Also, on the Data Sets section, we do put our Target and DLIBs on a dedicated volume and have them indirectly cataloged.  In our shop we also have to specify a STORCLAS of (SCNONSMS) so that the ACS routines will be bypassed and the adhoc volume will be honored.  I see there is no way for me to specify a volume and a Storage Class, so at the end, do I just have the JCL created and then go in and edit the JCL to add the STORCLAS(SCNONSMS) and then submit the job via ZOSMF?  Is that doable?

Thanks in advance,

Arlene