TCP/IP Stack Configuration with Configuration Assistant for IBM z/OS CS
- 1. 1© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. TCP/IP stack configuration with Configuration Assistant for IBM z/OS CS Mike Fox [email protected] Senior Software Architect IBM Enterprise Network Solutions Company
- 2. 2© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Agenda • Background on Configuration Assistant • TCP/IP profile technology • Basic profile support • Sysplex • Reusable Configuration • Configuration Assistant System symbols (APAR PI66143) • New in APAR PI66143: Profile import • New in APAR PI80101: Dynamic Reconfiguration 2
- 3. 3© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. 3 What is the Configuration Assistant • The Configuration Assistant is a GUI tool to simplify configuration of z/OS Communications Server • Policy-based networking technologies • IP Security – IP Filter rules and VPN tunnels • Along with configuration for NSS and DMD daemons Ø Quickly create IP Sec policy to filter traffic to/from the network, or to secure and protect data • Application Transport TLS (AT-TLS) • Create policies to secure your applications using SSL/TLS. Predefined rules are provided for many IBM z/OS applications! • Intrusion Detection Services (IDS) • Detect signature events (ex:scans and attacks) that can cause a misuse of system resources. • Policy-based Routing (PBR) • Create policies to allow TCP/IP to route traffic based upon criteria other than destination IP Address • Quality of Service (Qos) • Create policies to influence the performance of TCP/IP traffic • TCP/IP profile (new for z/OS V2R2) • The focus of this presentation Sockets API NSSD AT-TLS policy Policy administrator using Configuration Assistant QoS IP SecQoS Pagent Ike IP (v4 & v6) IDS IDS PBR DMD TRMD Syslogd logs (Transport Layer)(TCP) (UDP)
- 4. 4© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Configuration Assistant is a z/OSMF plug-in • You access the Configuration Assistant under the “Configuration” header in the z/OSMF navigation pane • This gets you to the Configuration Assistant opening screen shown here, where you open or create your backing store • Backing store is the configuration data file used by Configuration Assistant 4
- 5. 5© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Technologies configured by the Configuration Assistant This screen shot shows the TCP/IP technologies that Configuration Assistant configures • The first seven in the list are policy-based security and routing technologies that have been supported in the Configuration Assistant since its beginning. They are not the focus of this presentation. • The last one, TCP/IP profile, is the focus of this presentation 5
- 6. 6© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. The systems tree The systems tree defines the layout of your system… sysplexes, z/OS images, and TCP/IP stacks • You create this by adding elements using the Actions pulldown • This tree is shared by all of the technologies that are configured in the backing store • To configure a stack, sysplex, or image, you select it and pull down Actions->Configure • Which configuration options are then available depends on what technology you are configuring (i.e., TCP/IP Stack, AT-TLS, QoS, etc) 6
- 7. 7© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Systems tree, continued In the example to the left, z/OS image LPAR2 is selected, and then the Actions menu is pulled down. From here the user can: • Create a new sysplex (“z/OS Group”) • Create a new z/OS image in the sysplex that LPAR2 belongs to • Create a new stack on LPAR2 7
- 8. 8© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Systems tree, continued In this example, the user has selected STACK1 on LPAR1. He or she can then either pull down the Actions menu or, as in this example, right-click on the stack, to take specific actions • Other actions will be discussed later, but clicking “Configure” here will allow the user to edit the stack’s configuration • This logic works in all technologies. In TCPIP technology, the stack’s profile would be configured. In IPSEC technology, the stack’s filter rules would be configured, etc. 8
- 9. 9© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Getting help 9
- 10. 10© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. New for z/OS V2R2: TCP/IP profile configuration • In z/OS V2R2, “TCP/IP Profile” was added as a technology supported by Configuration Assistant • Previous to this only policy-based technologies were supported • This technology allows you to configure and manage your TCP/IP profile. 10
- 11. 11© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. TCP/IP profile basics • The TCP/IP profile technology allows you to configure a complete TCP/IP profile. • The configuration tasks are grouped into logical task areas 11 This path allows you to configure stack-specific resources. Sysplex and reusable resources will be discussed in later slides. Next slide
- 12. 12© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. TCP/IP profile example: defining an interface 12 Next slide
- 13. 13© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. TCP/IP profile example: defining an interface 13 Next slide
- 14. 14© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. TCP/IP profile example: defining an interface 14
- 15. 15© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Installing the configuration Installing the configuration means generating the TCP/IP profile and putting it in place. You can either save it to the file system of the image that z/OSMF is running on, or FTP it to another image. 15
- 16. 16© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Viewing the generated configuration This example shows how to view the generated TCP/IP profile from the install panel for a stack. The OSA11 interface we created earlier is highlighted. 16
- 17. 17© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Where can I find <statement> 17 This is an example of one of many tables in this help panel that you can use to find where the resource you’re looking for is located within the Configuration Assistant.
- 18. 18© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Sysplex single-system representation • Configuration Assistant implements the “single system image” concept of the z/OS sysplex • Sysplex networking parameters are configured as one task for all stacks in the sysplex and Configuration Assistant pushes the necessary configuration to each stack • Simplifies the coordinated definition that’s required for flat file sysplex definition 18
- 19. 19© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Sysplex example – Dynamic XCF network • First you define the Dynamic XCF subnet for the sysplex, using these panels • Then you attach individual stacks to Dynamic XCF, on the next panel 19 Next slide
- 20. 20© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Dynamic XCF continued • On this panel you attach a stack to the sysplex by specifying its Dynamic XCF IP address and any other Dynamic XCF characteristics • Similar steps for IPv6 Dynamic XCF 20 On this panel, CA reminds you of the dynamic XCF subnet and warns you if your attachment address is outside that subnet
- 21. 21© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Dynamic XCF example continued • Once all the stacks have been attached to the sysplex, Configuration Assistant pushes the correct DYNAMICXCF statement to each stack in the sysplex • Other sysplex resources such as Dynamic Distributed DVIPAs, VIPARANGE DVIPAs, and VIPAROUTE routing work similarly • Since all the sysplex resources for a sysplex are configured in a central place, this reduces coordination between stack configurations and errors that can result from mis-coordination. 21
- 22. 22© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Sysplex resources in generated configuration This example shows the DYNAMICXCF statements created in the generated profile for STACK1 after it’s been attached to the sysplex. 22
- 23. 23© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Introduction to reusable configuration Many customers use INCLUDE files in their TCP/IP profiles to help manage common configuration across multiple stacks. Examples of INCLUDE file use cases include: • Common PORT and AUTOLOG definitions • Common INTERFACE definitions • Common configuration options • For example: GLOBALCONFIG, IPCONFIG, etc. In Configuration Assistant, this is handled using objects known as Reusable Configuration 23
- 24. 24© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Reusable configuration, continued Reusable configuration objects are accessed from their own tab on the main TCP/IP systems tree. A reusable configuration object is a set of configuration that will be used by multiple TCP/IP stacks in the Configuration Assistant. 24
- 25. 25© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Creating reusable configuration In this example we will create a reusable configuration for common port definitions. First you give the RC a name… 25 Next slide
- 26. 26© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Creating reusable configuration, cont. Then you select which stacks will use this RC. These are the stacks that will make use of the common configuration that you create in the RC. In this example, we are creating common PORT definitions that will be used by all the stacks in PLEX1. Once the RC is created we are prompted to configure it. 26 Next slide
- 27. 27© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Configuring reusable configuration You configure reusable configuration just like any other TCP/IP configuration, using the same panels • There are some exceptions that will be touched on later In this case we are configuring common ports, so we select port defintions from the main resource screen. 27 Next slide
- 28. 28© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. RC Port configuration example In this example we have created a reservation for the standard telnet port 28 Next slide
- 29. 29© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. RC Port configuration example In this example we have created a reservation for the standard telnet port in this reusable configuration. 29
- 30. 30© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Push the reusable configuration to stacks Once reusable configuration is created, you push it to the stacks that use this RC by performing the “Promote to installed” action. This does two things: 1. Validates the reusable configuration against each stack (e.g., ensures no conflicts like duplicate names) 2. If 1 is successful, adds the configuration from the RC to all the using stacks. 30 Note: reusable configuration cannot be modified from within the using stacks. It must be modified in the RC interface, and then reinstalled.
- 31. 31© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Installed reusable configuration In the Reusable Configuration panel, a status of Installed indicates that the contents of the RC have been pushed to all using stacks 31 This is the port configuration panel for STACK1. You can see that the port 23 reservation came from reusable configuration PORTS. If you want to modify it this definition, you must do it in the RC, not here.
- 32. 32© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Reusable configuration generated files Configuration Assistant combines all configuration into a single TCP/IP profile when installing files, so the reusable resources are simply included in the profile, not maintained by CA as separate include files. 32
- 33. 33© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Configuration Assistant system symbols • Customers often use MVS system symbols along with include files to manage common configuration. Common use cases for MVS system symbols include: • Interface name and/or IP address for an interface that is in a common include file, for example: • 1.1.1.&HOST. • OSA&CHPID. • Configuration Assistant implements its own system symbols. • Introduced in Configuration Assistant APAR PI66143 on 9/1/2016 • CA system symbols have the same syntax as MVS system symbols (&SYMBOL_NAME.) • CA does not access MVS system symbol values • When importing TCP/IP configuration (covered in later slides) MVS system symbols are converted to CA system symbols • CA system symbols are created and resolved within the Configuration Assistant and are used when configuring stacks • CA system symbols are defined in reusable configuration and then given values for each stack that uses that reusable configuration • Configuration Assistant then generates TCP/IP profiles with all symbols resolved • A stack with unresolved CA system symbols is incomplete and cannot be installed until all referenced symbols are resolved. 33
- 34. 34© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Configuration Assistant system symbols, continued • CA system symbols are supported in the following fields: • Interface name • Interface IP address • Rule: because interfaces can’t have the same IP address across stacks, it is mandatory to use a CA system symbol in the IP address of any interface that is defined in reusable configuration. • Interface TRLE port name • Interface VLAN identifier • SRCIP IP address • These fields were chosen based on customer use case feedback. • If CA system symbol support is needed in additional fields, please open an RFE against the Communications Server team 34
- 35. 35© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Defining a CA system symbol • To define a CA system symbol, simply enter it into a supported field in a reusable configuration. • In this example, CA system symbol &HOST. is being created. 35
- 36. 36© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Special symbol rule for reusable interfaces The IP address of an interface defined in reusable configuration must be or contain a CA system symbol • This is because reusable interfaces are meant to be included into multiple stacks, and you can’t use the same IP address in multiple stacks! Have to be able to set the IP address per stack. • You can instruct CA to create a default IP address symbol, or you can specify the IP address with a symbol. • The default IP address symbol for this interface would be &OSAHOST_IPADDR. • You can specify a new symbol here, or as in this example, reuse a symbol that’s already been created. • Note that the symbol &HOST. is also used in the TRLE port name 36
- 37. 37© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Resolving symbol values: via the RC 37 Next slide • This slide shows an example of setting a symbol through the reusable configuration that defines/ uses it. • This interface gives you easy access to all stacks that need a value defined for this symbol
- 38. 38© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Resolving symbol values: via the RC • This slide shows an example of setting a symbol through the reusable configuration that defines/ uses it. • This interface gives you easy access to all stacks that need a value defined for this symbol 38
- 39. 39© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Symbols: automatic error checking When you set a CA stack symbol value, CA verifies that the value you select won’t cause any errors. This helps cut down on configuration errors! • In this example, the user attempted to set &HOST. to 999. • Because &HOST. is used as an IP address octet, it cannot accept this value. Clicking OK on this error dialog shows all users of the symbol, to help you debug this error. 39
- 40. 40© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Resolving symbol values: via the stack • This example shows how to resolve and update symbol values for a stack • This interface gives access to all symbols used by a stack, across multiple reusable configurations 40 Next slide
- 41. 41© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Resolving symbol values: via the stack 41
- 42. 42© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Resolved symbols: generated configuration • Configuration Assistant generates a TCP/IP profile with all CA system symbols resolved. 42
- 43. 43© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Introduction to TCP/IP profile import Most of our customers already have working TCP/IP profiles and need a way to import them into the Configuration Assistant. • We don’t expect you to recreate your TCP/IP configuration by hand in the Configuration Assistant! • TCP/IP profile import for the Configuration Assistant was shipped in 9/1/2016 APAR PI66143 • Requires companion z/OS Communications Server APAR PI63449. • TCP/IP profile import works in three major steps: 1. Run the VARY TCPIP,,EXPORTPROF operator command on z/OS Communications Server to format a TCP/IP configuration into a file that can be read by the Configuration Assistant 2. Import the file created in step 1 into the Configuration Assistant 3. Correct any errors as required to make the imported configuration installable 43
- 44. 44© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Step 1: Export TCP/IP configuration Invoke the VARY TCPIP,,EXPORTPROF operator command against z/OS Communications server and specify the MVS dataset that is the root file of the configuration to be exported. • The stack will read the file and all its includes and create a file in z/OS UNIX directory /var/exportprof for the Configuration Assistant to read. • The stack reads and exports the specified profile, it does not export its running configuration • The stack will detect syntax errors in the profile, but it will not detect context errors (for example, two IP interfaces with the same IP address). • The stack will also export the values of all MVS system symbols used in the profile . • Rule: if the profile to be exported contains MVS system symbols, you must run EXPORTPROF on the same MVS image that the profile runs on, to ensure correct symbol values are exported 44
- 45. 45© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. TCP/IP profile export example VARY TCPIP,TCPIP1,EXPORTPROF,USER.TCPPARMS(TCPIP) EZZ0060I PROCESSING COMMAND: VARY TCPIP,TCPIP1,EXPO,USER.TCPPARMS(TCPIP) EZZ0067I VARY EXPORTPROF COMMAND BEGINNING EZZ0300I OPENED INCLUDE FILE 'USER.TCPPARMS(PORT)' EZZ0300I OPENED INCLUDE FILE 'USER.TCPPARMS(INTFS)' EZZ0300I OPENED EXPORTPROF FILE 'USER.TCPPARMS(TCPIP)' EZZ0309I PROFILE PROCESSING BEGINNING FOR 'USER.TCPPARMS(TCPIP)' EZZ0309I PROFILE PROCESSING BEGINNING FOR USER.TCPPARMS(PORT) EZZ0316I PROFILE PROCESSING COMPLETE FOR FILE 'USER.TCPPARMS(PORT)' EZZ0304I RESUMING PROCESSING OF FILE 'USER.TCPPARMS(TCPIP)' EZZ0309I PROFILE PROCESSING BEGINNING FOR USER.TCPPARMS(INTFS) EZZ0316I PROFILE PROCESSING COMPLETE FOR FILE 'USER.TCPPARMS(INTFS)' EZZ0304I RESUMING PROCESSING OF FILE 'USER.TCPPARMS(TCPIP)' EZZ0316I PROFILE PROCESSING COMPLETE FOR FILE 'USER.TCPPARMS(TCPIP)' EZZ0070I VARY EXPORTPROF COMMAND CREATED EXPORT FILE: MVS1.TCPIP1.2016.03.20.18.30.04 EZZ0053I COMMAND VARY EXPORTPROF COMPLETED SUCCESSFULLY EZZ0069I VARY EXPORTPROF COMMAND COMPLETE 45 This profile uses two include files, PORT and INTFS. In the next step, you can control how these include files are handled. The Configuration Assistant import file created by this example is: /var/exportprof/MVS1.TCPIP1.2016.03.20.18.30.04
- 46. 46© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Importing TCP/IP configuration To import TCP/IP configuration you must first create a stack to receive the imported configuration. • This stack must have no configuration, except possibly dynamic XCF attachment to the sysplex. • Then select the stack and pull down the import action as shown in the screen shot 46
- 47. 47© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Importing configuration, continued You can import a formatted configuration file from the local file system, or you can have Configuration Assistant FTP it from another system 47
- 48. 48© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Import, continued 48 When you click Next on this panel, the configuration is imported The include file structure of the original configuration is preserved. You can specify which file is the base configuration, which ones to use as reusable configuration (and the names for those reusable configurations), and which ones to ignore. • Sysplex configuration is imported into the sysplex level, regardless of which file it was found in.
- 49. 49© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Post-import actions • Because of the sophistication and variety of the TCP/IP profile possibilities, the Configuration Assistant might not be able to completely resolve an import file. • Additionally, you might have errors in your TCP/IP configuration that you are ignoring, which the Configuration Assistant doesn’t ignore. • Finally, you might import profiles in an order that doesn’t resolve all references at first, especially in a sysplex. • Because of this, you might need to take additional action to complete an import. To determine what, if any, additional actions are required, look at the import report generated from the import. • You can access the import report from the last panel of the import wizard. You are automatically placed into this screen after an import completes. 49
- 50. 50© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Import report example Here is an example of an import report. • The first message is a warning. • The three unresolved reference errors are most likely because the other stacks in the sysplex have not been imported yet. • They may resolve on their own as the rest of the sysplex stacks are imported • If not they will need to be manually fixed 50
- 51. 51© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Example of imported error 51 Since EXPORTPROF can’t catch context errors, you could import erroneous configuration. When this happens the Configuration Assistant will mark the affected resources incomplete and you will have to manually fix them. Configuration Assistant will provide error messages for the affected resources to help you. • In this example, a profile was imported that contained 3 IP interfaces that had the same IP address.
- 52. 52© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Import of MVS system symbols • If the imported profile uses MVS system symbols in fields where CA supports CA system symbols, those MVS symbols are converted to CA system symbols • Restriction: remember that CA system symbols are only supported in reusable configuration. MVS system symbols found in base configuration will simply be imported as constants of their resolved values, regardless of field • The converted CA system symbols are inserted into their appropriate fields, and the symbol tables are populated with their imported values, so you do not need to resolve their values. • MVS system symbols in fields where CA does not support CA system symbols will be imported as constants of their resolved values. 52
- 53. 53© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Imported symbol ambiguity Because of the way EXPORTPROF and MVS symbol resolution works, CA gets configuration with all symbol values resolved, and, must do reverse look-up to restore symbol usage in supported fields. • This can result in symbol ambiguity. • For example if symbol &HOST.=“10”, every “10” found within a field that supports symbols could be replaced with &HOST., but that may not be what was originally configured. • If symbol ambiguity exists, the user must resolve it. • CA will provide all possible representations and the user must choose the correct one by deleting the incorrect ones. • See next slide for an example 53
- 54. 54© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Symbol ambiguity example If symbol ambiguity exists, the import report will indicate it. 54 Look for resources marked “Incomplete” in reusable configurations in the imported configuration. See next slide for how to resolve this one.
- 55. 55© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Symbol ambiguity example, continued In this example, two symbols share the same value. • &GSKVOL.=“MVS220” • &SYSR1.=“MVS220” The user resolves this ambiguity by deleting the incorrect representations from the field and leaving only the correct one. Note: a constant representation is always offered as one of the choices. In this example, it’s the first one. 55
- 56. 56© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Shipping now: Change set VARY OBEY is supported in Configuration Assistant by introducing a new configuration object called a “Change Set” • You create a change set based on an existing configuration object • a stack or group of stacks, or • a reusable configuration, or • a sysplex • The change set is seeded with the configuration from the object it’s based on • You edit the change set to make the configuration changes you want • When you install the change set, Configuration Assistant will generate the VARY OBEY files necessary to put the changes you made into effect • The VARY OBEY files, once placed onto the system are manually applied by the operator • Provides an opportunity for review of the OBEY files before they are applied to production systems. Customer feedback indicated this was important 56 Dynamic configuration is now being delivered on V2R2 in APAR PI80101/PTF UI47643. It will ship in the V2R3 base.
- 57. 57© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Additional change set capabilities • You can undo a change set • This will create the OBEY files necessary to put the configuration back the way it was before any edits were made in the change set • This supports the use case of making a temporary change that can easily be removed. • Or to back off an erroneous change! • You can merge change sets into the base • Once the OBEY files are applied this makes the change permanent • Customer feedback indicated to us that the main use case was to create an OBEY file, apply the change, then update the base configuration to reflect that change • For example: add a PORT reservation for a new application 57
- 58. 58© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Change sets are accessible from the TCP/IP systems tree 58
- 59. 59© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Illustration: Change sets based on TCP/IP stacks Image 1 Stack 1 Image 2 Stack 2 Image 3 Stack 3 Existing Configuration Stack 1’ Stack 2’ Change set based on Stack 1 and Stack2 CA copies existing configuration into change set User changes User changes User edits the copies within the change set to create changed configuration Image 1 Image 2 Stack 1 Stack1 Obey file Stack 2 Stack2 Obey file Image 2 V TCPIP,STACK1,O,OBEYPDS(STACK1) V TCPIP,STACK2,O,OBEYPDS(STACK2) Operator executes VARY OBEY command to put the changes into effect on the affected stacks. This gives an opportunity for reviews and installation change control to occur. CA generates the obey files necessary to put the changes into effect on the installed stack(s) and pushes them to the file system(s) (using FTP or direct file save if running on the same image) Configuration Assistant 59
- 60. 60© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Create a stack change set Next slide • A stack change set can be based on one or more stacks • A stack change set can only be based on stacks that are installed (note that LPAR3.STACK3 is not available for selection!) 60
- 61. 61© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Edit created stack change set Next slide If there are multiple stacks in a change set, you edit them one at a time 61
- 62. 62© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Editing a stack in a change set To configure changes, Simply edit the stack as you would normally using the GUI “Change Set Status” column indicates where changes have been made Next slide 62
- 63. 63© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Change a parameter for the change set Next slideIn this example, we simply edited the Maximum receive buffer value, changing it from 333 to 577 kilobytes 63
- 64. 64© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Seeing what updates were made “Change Set Status” column now indicates that something was changed in that column Green Delta flags help you pick out what’s changed on a panel 64
- 65. 65© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. To compare old and new values, use View Details On the change set configuration screen, View Details gives you an easy before and after view of a stack being changed Next slide 65
- 66. 66© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. View details comparison In this example, a simple scalar parameter was changed. View details is very sophisticated and shows you changes made to table parameters, as shown on the next slide. 66
- 67. 67© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. View Details: table parameters In this example, the static route table was modified by: • Changing the first hop of the default route • Adding a new route to 10.1.0.0/32. View Details helps you see before and after 67
- 68. 68© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Installing changes: creating the OBEY file The OBEY file is created and stored through the Install interface. It works similarly to the Install interface for regular configuration files Once the OBEY file has been installed, the operator can run the VARY OBEY console command to put it into effect 68
- 69. 69© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Change set UNDO Change set Undo is an install action. • After a change set has been installed, you can undo it for a stack by pulling down Actions->Install Change Set Undo on the Manage Installs panel. • This creates and saves an OBEY file that restores the stack’s configuration to the pre-Change Set state. • The change set is still available to be edited and/or re-installed from the Configuration Assistant. Useful for undoing erroneous change sets, or to remove changes that were meant to be temporary 69
- 70. 70© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Change set merge Merge is a change set action • After a change set has been installed, merge the changes into the stack by pulling down Actions->Merge Change Set into Base • This updates the base configuration to the changed configuration and removes the stack from the change set. • If this is the only stack in a change set, the change set is deleted Useful for making the change a permanent part of the stack’s configuration (example: adding a port for a new application) 70
- 71. 71© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Change set merge notes Merging a change set into the base configuration changes the base configuration • This has all the same implications as if the base configuration had been edited manually. • The base configuration must be re-installed so that it is available to the stack next time it IPLs • Because the stack needs to be installed, a new change set cannot be based on it until that install is done. 71
- 72. 72© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Stack change set restrictions When Configuration Assistant is creating an OBEY file for a change set, it creates the OBEY file necessary to change the base configuration to match the change set configuration. For this reason, Configuration Assistant must know exactly what is in the base TCP/IP configuration on the MVS image to correctly generate this file. This requirement results in two main change set restrictions: 1. A change set can only be based on installed configuration. • For a stack change set, this means that stacks whose install status is Needs Install or Never Installed are not eligible to have change sets based on them. . 2. Configuration with a change set based on it cannot be edited. • For a stack change set, this means that a stack that has a change set based on it cannot be edited in the GUI until the change set is either merged or deleted. 72
- 73. 73© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Change set special case: changing IP interfaces The procedure for changing the name, IP address, or most other characteristics of an IP interface for Communications Server is: 1. Stop the interface to be changed 2. Perform a VARY OBEY to delete the interface to be changed 3. Perform a VARY OBEY to add the interface with its new characteristics. Restriction: this must be a different OBEY file from the one used in step 2 • You cannot delete and add an interface in the same OBEY file! Because of this requirement, Configuration Assistant has special processing for these types of interface changes. Configuration Assistant creates two OBEY files: A DELETE file to delete the old definition, and then another OBEY file to add it back with changes. The next few slides illustrate this process. 73
- 74. 74© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Change set example – change interface name In this example, the name of interface “OSA2” is changed to “OSA2A” 74
- 75. 75© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Change interface name, delete file Because the interface’s name was changed, a separate DELETE file is generated alongside the normal OBEY file 75
- 76. 76© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Change interface name, continued The obey file adding the interface back with the new name is created alongside the DELETE file 76
- 77. 77© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Install interface name change files Both the delete and the add with new name OBEY files are saved when this change set is installed. As always, you can edit the name of either one. • Note that the UNDO for this change set will also create both a DELETE and a re-add OBEY file! 77
- 78. 78© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Other IP interface change set restrictions Because an IP interface must be deleted to change it, you cannot change an interface that is referenced elsewhere unless you also delete that reference. This is the same restriction you have when editing interfaces in base configuration in Configuration Assistant. Examples of places were IP interfaces can be referenced: • SOURCEVIPA statements or parameters • Static route outgoing interface • Primary interface for a stack • VIPAROUTE targets If you attempt to change an interface that is referenced elsewhere, Configuration Assistant will tell you where those references are, as shown here. 78
- 79. 79© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Illustration: Change sets based on Reusable Configuration Image 1 Stack 1 Image 2 Stack 2 Image 3 Stack 3 Existing Configuration RC1’ Change set based on RC1 User changes User edits copy within the change set to create changed configuration and triggers validation of changes in all affected stacks Image 1 Image 2 Stack 1 Stack1 Obey file Stack 2 Stack2 Obey file Image 2 V TCPIP,STACK1,O,OBEYPDS(STACK1) V TCPIP,STACK2,O,OBEYPDS(STACK2) Operator executes VARY OBEY command to put the changes into effect on the affected stacks. This gives an opportunity for reviews and installation change control to occur. CA generates the obey files necessary to put the changes into effect on all the stacks affected by the change, and pushes them to the file system(s) (using FTP or direct file save if running on the same image) Configuration Assistant RC1 Reusable configuration installed into Stack 1 and Stack 2 RC1 RC1 CA copies existing reusable configuration into change set 79
- 80. 80© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Create a Reusable Configuration Change set A change set can only be based on a reusable configuration if that RC has been installed into the stacks that use it, AND all those stacks are installed. 80
- 81. 81© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Configuring a reusable configuration change set You configure a reusable configuration change set similarly to how you configure a stack change set. You simply make the desired changes in the editor as if you were editing the Reusable configuration normally. In this example we’ve updated the backlog limit. 81
- 82. 82© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Extra step for RC change sets: validate against base Before a reusable configuration change set can be installed, you must validate it against the base. This validation verifies that no conflicts or errors were created within the stacks that include this reusable configuration • For example, adding a duplicate interface name or address, or deleting an interface that’s referenced in the stack configuration 82
- 83. 83© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. RC change set configuration installation When you install an RC change set, Configuration Assistant automatically generates OBEY files for every stack that uses that RC. You can then view, install, and undo the changes on a stack by stack basis. 83
- 84. 84© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Merging an RC change set When you merge an RC change set into its base RC, the RC is updated to match the change set configuration, the changes are pushed to each stack that uses the RC, and then the change set is deleted. Each stack that uses the RC must be reinstalled to make the changed configuration available for the next stack IPL 84
- 85. 85© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Reusable configuration change set restrictions Reminder: When Configuration Assistant is creating an OBEY file for a change set, it creates the OBEY file necessary to change the base configuration to match the change set configuration. For this reason, Configuration Assistant must know exactly what is in the base TCP/IP configuration on the MVS image to correctly generate this file. This requirement results in two main change set restrictions: 1. A change set can only be based on installed configuration. • For a reusable configuration change set, this means that an RC must be installed in all using stacks, and those stacks all have an install status of “Installed” for the RC to be eligible to have a change set based on it. 2. Configuration with a change set based on it cannot be edited. • For a reusable configuration change set, this means that an RC with a change set cannot be edited in the Configuration Assistant. It also means that none of the stacks that use a reusable configuration that has a change set based on it can be edited. These restrictions are in place until the change set is merged or deleted. 85
- 86. 86© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Illustration: Change sets based on a sysplex Image 1 Stack 1 Image 2 Stack 2 Image 3 Stack 3 Existing Configuration Change set based on Plex1 User edits copy within the change set to create changed configuration and triggers validation of changes in all affected stacks Stack 1 Stack1 Obey file V TCPIP,STACK1,O,OBEYPDS(STACK1) Operator executes VARY OBEY command to put the changes into effect on the affected stacks. This gives an opportunity for reviews and installation change control to occur. Configuration Assistant Sysplex configuration for Stack1, Stack2, and Stack3 Plex1 Plex1 CA copies existing sysplex configuration into change set Plex 1 Plex1 Stack 2 Stack2 Obey file Stack 3 Stack3 Obey file V TCPIP,STACK2,O,OBEYPDS(STACK2) V TCPIP,STACK3,O,OBEYPDS(STACK3) Plex1’User changes CA generates the obey files necessary to put the changes into effect on all the stacks affected by the change, and pushes them to the file system(s) (using FTP or direct file save if running on the same image) Image 3 Image 2 Image 1 86
- 87. 87© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Creating a sysplex change set A change set can only be based on a sysplex if every stack in the sysplex has an install status of “Installed”. 87
- 88. 88© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Configuring sysplex changes Similar to the other change set types, you simply make the changes you want in the GUI. In this example, we have changed the Workload Manager polling interval to 120 seconds. 88
- 89. 89© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Sysplex change set installation When you install a sysplex change set, Configuration Assistant automatically generates OBEY files for every stack in the sysplex that is affected by the change. You can then view, install, and undo the changes on a stack by stack basis. 89
- 90. 90© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Merging a sysplex change set When you merge a sysplex change set into its base sysplex, the sysplex is updated to match the change set configuration, the changes are pushed to each affected stack in the sysplex, and the sysplex is removed from the change set (if it was the only sysplex in the change set, the change set is deleted). Each affected stack must be reinstalled to make the changed configuration available for the next stack IPL 90
- 91. 91© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM. Sysplex change set restrictions Reminder: When Configuration Assistant is creating an OBEY file for a change set, it creates the OBEY file necessary to change the base configuration to match the change set configuration. For this reason, Configuration Assistant must know exactly what is in the base TCP/IP configuration on the MVS image to correctly generate this file. This requirement results in two main change set restrictions: 1. A change set can only be based on installed configuration. • For a sysplex change set, this means that every stack in the sysplex have an install status of “Installed” for the sysplex to be eligible to have a change set based on it. 2. Configuration with a change set based on it cannot be edited. • For a sysplex change set, this means that a sysplex with a change set based on it cannot be edited in the Configuration Assistant. It also means that none of the stacks that are in a sysplex that has a change set based on it can be edited. These restrictions are in place until the change set is merged or deleted. 91
- 92. 92© Copyright IBM Corporation 2017. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.© Copyright IBM Corporation 2017. Materials may not be reproduced in whole or in part without the prior written permission of IBM.