ESP3016E CONSOLE nnnn name is invalid

Products

• ESP Workload Automation

Issue/Introduction

Received ESP3016E when starting new ESP Proxy. (CONSOLE NAME nnnn is invalid) 

 

Environment

Component: ESP Workload Automation
Release:   12.0

Resolution

When creating an extended MCS with a name that defaults to the SYSID (or the SMF ID in case no SYSID initparm is present). Use the SYSIDs for valid console names, and use SMF IDs starting with an alpha character. 

This behavior is described in the MCS initialization parameter:    SYSID Specify system identifier

By default, ESP is activated as an extended MCS console and does not need to be added to the MCS initialization parameter.

The console name is up to eight characters, and If omitted, the console name defaults to the value specified in the SYSID initialization parameter. If the SYSID initialization parameter is omitted, the current SMF system identifier is used.

Here are the ways to avoid this error message:
1. Add an MCS DEACTIVATE statement to your init parm for this proxy member, and there will be no adverse effects since the result will be the same message ESP3016E.  The extended MCS feature will simply be deactivated.

2. Change the SYSID of this proxy instance. We recommend not using the SMF ID as the SYSID because changing it would require a cold start and might not be the best solution. 

3. Changing the system ID requires an ESP cold start to reset the ownership, which might happen if the SMF ID is used as a default and it changes. For this reason, we recommend that the SMF ID is not used, but that each ESP be given a unique system ID.