For software management. We have tried a few products installation already in our sandbox environment, where we typically first install software. I wanted some clarification regarding remote deployments. I am not sure if I have understood this wrong.

I though the idea was once you deploy from your PSWI the first time,  I now have a 'software instance' with our naming conventions that can be 'rolled out' to other lpars using z/OSMF. Basically using the tool to move software around from sysplex to sysplex with minimal updates other than maybe volumes or names.

I tried this today with a software instance we had installed. I proceed to select an lpar in a different sysplex as the target system but when I got to 'Data Sets' section of the wizard I see a lot more datasets than the ones part of the software instance. They are all SMPTLIBs datasets that have nothing to do with the software being deployed.

Am I trying to use the tool for something that's not intended for?

Thank you,

Cindy

HI Cindy,

What you intend to do is totally what it is intended to do!

It is interesting you are seeing target libraries (which I believe you refer to as "SMPTLIBs"?) which are not part of your software instance being deployed, in the Data Set section.  On your software instance, can you look at the data sets which z/OSMF Software Management believes is part of that instance, and see them there?  From there, those should be all the data sets composing your software instance which would be deployed.  Of course, you don't need to deploy the distribution libraires.  Go into Software Instance and select what you wanted to re-deploy to another system, do Actions -> View -> Data Sets.  Does what you see there match the data set list you are seeing on the Deployment Data Set wizard?

For software management. We have tried a few products installation already in our sandbox environment, where we typically first install software. I wanted some clarification regarding remote deployments. I am not sure if I have understood this wrong.

I though the idea was once you deploy from your PSWI the first time,  I now have a 'software instance' with our naming conventions that can be 'rolled out' to other lpars using z/OSMF. Basically using the tool to move software around from sysplex to sysplex with minimal updates other than maybe volumes or names.

I tried this today with a software instance we had installed. I proceed to select an lpar in a different sysplex as the target system but when I got to 'Data Sets' section of the wizard I see a lot more datasets than the ones part of the software instance. They are all SMPTLIBs datasets that have nothing to do with the software being deployed.

Am I trying to use the tool for something that's not intended for?

Thank you,

Cindy

Hi Marna,

In software Instance, Actions -> View -> Data Sets it matches what i see on the deployment wizard. I see the actual product datasets, about 30, plus the rest of the SMPTLIBs , SMPPTSs, GLOBAL CSI, etc. 

For the remote deployment, i selected to deploy to an existing global csi in the target system. So I was expecting to only see the product related datasets, only 30. 

HI Cindy,

What you intend to do is totally what it is intended to do!

It is interesting you are seeing target libraries (which I believe you refer to as "SMPTLIBs"?) which are not part of your software instance being deployed, in the Data Set section.  On your software instance, can you look at the data sets which z/OSMF Software Management believes is part of that instance, and see them there?  From there, those should be all the data sets composing your software instance which would be deployed.  Of course, you don't need to deploy the distribution libraires.  Go into Software Instance and select what you wanted to re-deploy to another system, do Actions -> View -> Data Sets.  Does what you see there match the data set list you are seeing on the Deployment Data Set wizard?

For software management. We have tried a few products installation already in our sandbox environment, where we typically first install software. I wanted some clarification regarding remote deployments. I am not sure if I have understood this wrong.

I though the idea was once you deploy from your PSWI the first time,  I now have a 'software instance' with our naming conventions that can be 'rolled out' to other lpars using z/OSMF. Basically using the tool to move software around from sysplex to sysplex with minimal updates other than maybe volumes or names.

I tried this today with a software instance we had installed. I proceed to select an lpar in a different sysplex as the target system but when I got to 'Data Sets' section of the wizard I see a lot more datasets than the ones part of the software instance. They are all SMPTLIBs datasets that have nothing to do with the software being deployed.

Am I trying to use the tool for something that's not intended for?

Thank you,

Cindy

Hi Cindy,

Ah!  Yes - your SMP/E supporting data sets (CSIs, SMPPTS, SMPLTS, SMP...) are absolutely part of your deployed software instance!  This is a best practice and is necessary if we want to have complete knowledge of what is being deployed.  I know that many legacy homegrown processes for cloning software never took the SMP/E environment, and folks often used one CSI target zone to represent several physical images (1:M).  The z/OSMF deployment process incorporates this best practice to ensure that you have an SMP/E environment for each of your software instances (when they are SMP/E managed, of course).  

For having complete and accurate knowledge of what is being deployed, we need a 1:1 relationship between the SMP/E environment and the deployed data sets.  In other words, we minimumally need to take along an SMP/E target zone to accommpany the SMP/E-managed target data sets so we have accurate information whereever they may be.  

Hi Marna,

In software Instance, Actions -> View -> Data Sets it matches what i see on the deployment wizard. I see the actual product datasets, about 30, plus the rest of the SMPTLIBs , SMPPTSs, GLOBAL CSI, etc. 

For the remote deployment, i selected to deploy to an existing global csi in the target system. So I was expecting to only see the product related datasets, only 30. 

HI Cindy,

What you intend to do is totally what it is intended to do!

It is interesting you are seeing target libraries (which I believe you refer to as "SMPTLIBs"?) which are not part of your software instance being deployed, in the Data Set section.  On your software instance, can you look at the data sets which z/OSMF Software Management believes is part of that instance, and see them there?  From there, those should be all the data sets composing your software instance which would be deployed.  Of course, you don't need to deploy the distribution libraires.  Go into Software Instance and select what you wanted to re-deploy to another system, do Actions -> View -> Data Sets.  Does what you see there match the data set list you are seeing on the Deployment Data Set wizard?

For software management. We have tried a few products installation already in our sandbox environment, where we typically first install software. I wanted some clarification regarding remote deployments. I am not sure if I have understood this wrong.

I though the idea was once you deploy from your PSWI the first time,  I now have a 'software instance' with our naming conventions that can be 'rolled out' to other lpars using z/OSMF. Basically using the tool to move software around from sysplex to sysplex with minimal updates other than maybe volumes or names.

I tried this today with a software instance we had installed. I proceed to select an lpar in a different sysplex as the target system but when I got to 'Data Sets' section of the wizard I see a lot more datasets than the ones part of the software instance. They are all SMPTLIBs datasets that have nothing to do with the software being deployed.

Am I trying to use the tool for something that's not intended for?

Thank you,

Cindy

That I get. But what surprises me is that in the wizard I only see old SMPTLIB datasets + the ones that came with the ibm order. I do not understand why z/OSMF is thinking the SMPTLIBs are needed to be ported over into the target system. It does not try to send the SMPPTS, SMPSCDS that are part of the GLOBAL zone in the source system, why does it think it needs to take old SMPTLIBs that are in the GLOBAL zone.

Curious, what SMP/E action is software management doing to get the 'data sets' lists' in the wizard?

Thank you

Hi Cindy,

Ah!  Yes - your SMP/E supporting data sets (CSIs, SMPPTS, SMPLTS, SMP...) are absolutely part of your deployed software instance!  This is a best practice and is necessary if we want to have complete knowledge of what is being deployed.  I know that many legacy homegrown processes for cloning software never took the SMP/E environment, and folks often used one CSI target zone to represent several physical images (1:M).  The z/OSMF deployment process incorporates this best practice to ensure that you have an SMP/E environment for each of your software instances (when they are SMP/E managed, of course).  

For having complete and accurate knowledge of what is being deployed, we need a 1:1 relationship between the SMP/E environment and the deployed data sets.  In other words, we minimumally need to take along an SMP/E target zone to accommpany the SMP/E-managed target data sets so we have accurate information whereever they may be.  

Hi Marna,

In software Instance, Actions -> View -> Data Sets it matches what i see on the deployment wizard. I see the actual product datasets, about 30, plus the rest of the SMPTLIBs , SMPPTSs, GLOBAL CSI, etc. 

For the remote deployment, i selected to deploy to an existing global csi in the target system. So I was expecting to only see the product related datasets, only 30. 

HI Cindy,

What you intend to do is totally what it is intended to do!

It is interesting you are seeing target libraries (which I believe you refer to as "SMPTLIBs"?) which are not part of your software instance being deployed, in the Data Set section.  On your software instance, can you look at the data sets which z/OSMF Software Management believes is part of that instance, and see them there?  From there, those should be all the data sets composing your software instance which would be deployed.  Of course, you don't need to deploy the distribution libraires.  Go into Software Instance and select what you wanted to re-deploy to another system, do Actions -> View -> Data Sets.  Does what you see there match the data set list you are seeing on the Deployment Data Set wizard?

For software management. We have tried a few products installation already in our sandbox environment, where we typically first install software. I wanted some clarification regarding remote deployments. I am not sure if I have understood this wrong.

I though the idea was once you deploy from your PSWI the first time,  I now have a 'software instance' with our naming conventions that can be 'rolled out' to other lpars using z/OSMF. Basically using the tool to move software around from sysplex to sysplex with minimal updates other than maybe volumes or names.

I tried this today with a software instance we had installed. I proceed to select an lpar in a different sysplex as the target system but when I got to 'Data Sets' section of the wizard I see a lot more datasets than the ones part of the software instance. They are all SMPTLIBs datasets that have nothing to do with the software being deployed.

Am I trying to use the tool for something that's not intended for?

Thank you,

Cindy