Hello zOSMF TechXchange,

Seeking some advice for a configuration of zOSMF in a SYSPLEX environment.

There are 5 PROD LPAR's, 3 DEVL LPAR's, 2 GDPS LPAR's and , 3 TEST LPAR's (TEST not in the SYSPLEX)  - I'm trying to envision a zOSMF configuration.  Where do I 'plant' the zOSMF STC's across this configuration?  I think one STC in each 'group' of PROD DEVL GDPS TEST servers but guidelines in the documentation suggest just one STC for the entire SYSPLEX.  We inherited the SYSPLEX and I would have like an architecture where these systems were split out into their own SYSPLEX environments (PROD DEVL GDPS TEST) but this site has all 10 (PROD DEVL GDPS) in one SYSPLEX.  It would have been nice to have the 3 TEST in their own SYSPLEX for testing, crashing, burning.  Currently, someone has planted one STC as a 'driver' server (AUTOSTART=LOCAL) in the 'group's (PROD DEVL GDPS) group.  I looked at this configuration as (PROD DEVL GDPS TEST) but the SYSPLEX and it's members are the rule in considering the zOSMF configuration I think as the documentation outlines. 

In these logical 'group's, would I start a 'secondary' server (AUTOSTART=CONNECT) that communicate with the main server (AUTOSTART=LOCAL) that communicates with the other LPARs?  Or, is only the one STC in the group is all that is needed for all 10 LPARs (PROD DEVL GDPS)?  Having a separate TEST zOSMF STC would be nice for thorough testing but they are not 'group'd as a SYSPLEX. 

Anyone have a suggestion would be greatly appreciated!  I'm new to setting up this configuration but appreciate anyone's advice - especially as I consider the zOSMF Ansible for use to manage workflows for distributing maintenance, products, and for auto-ipl when testing is needed.  I might be reaching here with Ansible but I thought that is what it is useful as the SysProg team could on-demand the IPL from Ansible after distributing their new software maintenance or products for testing in the TEST LPAR's. 

Thank you to anyone reading my ramblings.    

Hi Lynn,

Generally speaking, there should be one z/OSMF that manages the entire SYSPLEX.  If I understand your environment, each of your test systems is an isolated system, therefore each of them would have their own z/OSMF.

You would want to configure the z/OSMF System table in the z/OSMF for your SYSPLEX to include all of the systems in your SYSPLEX so z/OSMF's plugins know how to target them for different actions.  You can also add your test systems to the System table, identifying their individual respective z/OSMF end-points.  I believe that would allow you to target them for software maintenance and distribution.

Depending on what you want to be able to do from your Test systems, you would configure their respective System tables accordingly.

Kurt Quackenbush is the SME regarding software maintenance and distribution using z/OSMF's Software Management and Software Update plugins. 

John Czukkermann
z/OSMF Development

Hello zOSMF TechXchange,

Seeking some advice for a configuration of zOSMF in a SYSPLEX environment.

There are 5 PROD LPAR's, 3 DEVL LPAR's, 2 GDPS LPAR's and , 3 TEST LPAR's (TEST not in the SYSPLEX)  - I'm trying to envision a zOSMF configuration.  Where do I 'plant' the zOSMF STC's across this configuration?  I think one STC in each 'group' of PROD DEVL GDPS TEST servers but guidelines in the documentation suggest just one STC for the entire SYSPLEX.  We inherited the SYSPLEX and I would have like an architecture where these systems were split out into their own SYSPLEX environments (PROD DEVL GDPS TEST) but this site has all 10 (PROD DEVL GDPS) in one SYSPLEX.  It would have been nice to have the 3 TEST in their own SYSPLEX for testing, crashing, burning.  Currently, someone has planted one STC as a 'driver' server (AUTOSTART=LOCAL) in the 'group's (PROD DEVL GDPS) group.  I looked at this configuration as (PROD DEVL GDPS TEST) but the SYSPLEX and it's members are the rule in considering the zOSMF configuration I think as the documentation outlines. 

In these logical 'group's, would I start a 'secondary' server (AUTOSTART=CONNECT) that communicate with the main server (AUTOSTART=LOCAL) that communicates with the other LPARs?  Or, is only the one STC in the group is all that is needed for all 10 LPARs (PROD DEVL GDPS)?  Having a separate TEST zOSMF STC would be nice for thorough testing but they are not 'group'd as a SYSPLEX. 

Anyone have a suggestion would be greatly appreciated!  I'm new to setting up this configuration but appreciate anyone's advice - especially as I consider the zOSMF Ansible for use to manage workflows for distributing maintenance, products, and for auto-ipl when testing is needed.  I might be reaching here with Ansible but I thought that is what it is useful as the SysProg team could on-demand the IPL from Ansible after distributing their new software maintenance or products for testing in the TEST LPAR's. 

Thank you to anyone reading my ramblings.    

Hi Lynn,

Generally speaking, there should be one z/OSMF that manages the entire SYSPLEX.  If I understand your environment, each of your test systems is an isolated system, therefore each of them would have their own z/OSMF.

You would want to configure the z/OSMF System table in the z/OSMF for your SYSPLEX to include all of the systems in your SYSPLEX so z/OSMF's plugins know how to target them for different actions.  You can also add your test systems to the System table, identifying their individual respective z/OSMF end-points.  I believe that would allow you to target them for software maintenance and distribution.

Depending on what you want to be able to do from your Test systems, you would configure their respective System tables accordingly.

Kurt Quackenbush is the SME regarding software maintenance and distribution using z/OSMF's Software Management and Software Update plugins. 

John Czukkermann
z/OSMF Development

Hello zOSMF TechXchange,

Seeking some advice for a configuration of zOSMF in a SYSPLEX environment.

There are 5 PROD LPAR's, 3 DEVL LPAR's, 2 GDPS LPAR's and , 3 TEST LPAR's (TEST not in the SYSPLEX)  - I'm trying to envision a zOSMF configuration.  Where do I 'plant' the zOSMF STC's across this configuration?  I think one STC in each 'group' of PROD DEVL GDPS TEST servers but guidelines in the documentation suggest just one STC for the entire SYSPLEX.  We inherited the SYSPLEX and I would have like an architecture where these systems were split out into their own SYSPLEX environments (PROD DEVL GDPS TEST) but this site has all 10 (PROD DEVL GDPS) in one SYSPLEX.  It would have been nice to have the 3 TEST in their own SYSPLEX for testing, crashing, burning.  Currently, someone has planted one STC as a 'driver' server (AUTOSTART=LOCAL) in the 'group's (PROD DEVL GDPS) group.  I looked at this configuration as (PROD DEVL GDPS TEST) but the SYSPLEX and it's members are the rule in considering the zOSMF configuration I think as the documentation outlines. 

In these logical 'group's, would I start a 'secondary' server (AUTOSTART=CONNECT) that communicate with the main server (AUTOSTART=LOCAL) that communicates with the other LPARs?  Or, is only the one STC in the group is all that is needed for all 10 LPARs (PROD DEVL GDPS)?  Having a separate TEST zOSMF STC would be nice for thorough testing but they are not 'group'd as a SYSPLEX. 

Anyone have a suggestion would be greatly appreciated!  I'm new to setting up this configuration but appreciate anyone's advice - especially as I consider the zOSMF Ansible for use to manage workflows for distributing maintenance, products, and for auto-ipl when testing is needed.  I might be reaching here with Ansible but I thought that is what it is useful as the SysProg team could on-demand the IPL from Ansible after distributing their new software maintenance or products for testing in the TEST LPAR's. 

Thank you to anyone reading my ramblings.