z/OSMF V2R1 Changing the server properties
KaranITSO 120000AGEF Visits (1206)
It might be useful to change some z/OSMF server properties between server restarts. For example, if you have to move the z/OSMF server from one lpar to another and need to update the host name or if you need to change the ports that the server uses to listen on for connections. I'll provide some suggestions as to how this can be accomplished.
After z/OSMF is configured, the host name that is specified during the configuration process is saved in the boot
Do not change this file. There is a step (SUBSYM) in the z/OSMF started task (izusvr1 by default) that replaces the contents of this file on server start. The relevant step in the z/OSMF server proc is shown below.
This step uses the bootstrap.template file (which is created at configuration time with the default path of /etc
This step reads the bootstrap.template file, resolves symbols, then replaces the boot
If you are not using a host name for a DVIPA address or using symbolics to resolve the host name, then before you start the z/OSMF server on an alternative sysplex member, you must update the izu.hostname property in the boostrap.template file to specify the host name of the sysplex member where you are starting z/OSMF.
This task must be done every time that you move z/OSMF from one member of a sysplex to another member.
For example, if the z/OSMF instance was initially started on SC80 but you want to move it to SC81, then you stop z/OSMF on SC80, update the bootstrap.template file as shown in below, and then start z/OSMF on SC81.
If possible, try to use the same set of TCP ports for z/OSMF on all members of the sysplex.
If you are using the same ports on all members of the sysplex where z/OSMF can be started, then no additional changes are required.
However, if the ports that are used for the SSL (the configuration variable that is called IZU_HTTP_SSL_PORT) and non-SSL (the configuration variable IZU_HTTP_PORT) values might change depending on the sysplex member where z/OSMF is started, then you must update the izu.https.port (for the SSL connection) and izu.http.port (for the non-SSL connection) properties in the bootstrap.template file with the correct port values for the system before you start z/OSMF.
The sample below shows a bootstrap.template update when you move z/OSMF from one system (SC80) to another system (SC81) where both the host name and ports are unique for each system.
z/OSMF ports should still be defined as reserved for each member in the sysplex where z/OSMF can be started.
For more useful tips on working with z/OSMF V2R1 see the following IBM Redbooks Publ