After installing MAT 11.0 into a "TEST" environment, I migrated to a "PROD" environement. Why upon starting the PROD instance of MAT 11.0 am I getting a S0C4?

Products

• Mainframe Application Tuner

Issue/Introduction

After installing into a 'TEST' environment I had no problems.  The started task 'MATUNER' started with no errors.  This environment is monoplex (with SYSPLEX).

I wanted this to also be in a production environment SYSPLEX, so for this I did the following:

1. Backup of MAT 11.0 in the TEST environment.

2. Restore of MAT 11.0 'PROD' environment, with the new standard of Production.

3. Customized steps 1-8 in TRCUST pointing to the production datasets.

4. Started 'MATUNER' in 'PROD' but we are receiving a S0C4.

Do you know what steps I must take in the 'PROD' environment which was backed from 'TEST' environment and restored in 'PROD' environment?

Environment

Release:
Component: MATUNE

Resolution

The first step to see if you can resolve the S0C4 is to perform a COLD start of the MAT server task 'MATUNER'.

You might see messages similar to:

TN3325I CA MAT ANCHOR BLOCK LOCATED AT 0057EE0E0

13.48.59 STC09195 TN1066E Pause Element Token error in IEAVDPE2, 00000FFF

13.48.59 STC09195 TN1053W ASID not found for SMSVSAM, VSAM RLS DISABLED.

13.48.59 STC09195 TN5219I SECURITY HAS BEEN SET TO NONE

These message occur because support was added for VSAM RLS.  It depends on the customer running an SMS VSAM address space.  If you are not using RLS and you don't have an SMSVSAM address space when MAT tries to establish support you will see this message.  It's not a fatal error.