Mainframe Application Tuner upgrade to V12.0

Products

• Mainframe Application Tuner

Issue/Introduction

Upgraded Mainframe Application Tuner to new version v12.0 from v10.0, in the MATUNER started task log there is some time out post. 

Environment

Release:
Component: MATUNE

Resolution

The messages we are concerned with is: 

16.21.27 S0094814 TN3410I CA MAT module TNXMSG loaded at 11272100 <MATUNER > 
16.21.27 S0094814 TN5122I Connecting to CA MAT server on system SYT3 <MATUNER 
16.21.27 S0094814 TN5122I Connecting to CA MAT server on system SYT1 <MATUNER 
16.21.27 S0094814 TN5122I Connecting to CA MAT server on system SYSY <MATUNER 
16.21.27 S0094814 TN5122I Connecting to CA MAT server on system SPOK <MATUNER 
16.21.27 S0094814 TN5125I Sysplex support is operational. Connected to group 
16.21.27 S0094814 TN3410I CA MAT module TNSSV42 loaded at 038079A8 <MATUNER > 
16.21.27 S0094814 TN1021I CA MAT SVC 042 filter installed at 00FB2E00� <MATUNE 
16.21.27 S0094814 TN1010I CA MAT Server Space START complete <MATUNER > 
16.22.18 S0094814 TN5129E XCF handshake timed out with member SPOK <MATUNER > 
16.23.09 S0094814 TN5129E XCF handshake timed out with member SYSY <MATUNER > 
16.23.11 S0094814 TN5127E GIF mismatch with other systems in XCF group <MATUNE 
16.23.11 S0094814 TN5128I Sysplex support is terminating <MATUNER > 

This means that the Sysplex support is not working and probably why you are getting the TN5128I message. 

Possible reasons to this: 

1. In the XCF group you should have only v12 servers. Currently we don't support mixing 2 different versions in the same XCF group. So if any of those servers are not v12 they should be in a different XCF group. 

2. All the v12 servers should share the same v12 GIF file. All the non-v12 servers should share the same non-v12 GIF file. 

If either of the 2 conditions above is somehow not fulfilled the Sysplex support wouldn't work.