CA Datacom environment is set up with a Primary and a Shadow Multi-User.
When the Primary MUF is EOJed, the Shadow MUF enables successfully.
However, attempt to try out the Datacom MIGRATE_TO_SHADOW console command fails with error:
DB02336E - SHADOW MIGRATE IGNORED, XES STRUCTURE UNAVAILABLED
The cause is revealed in the explanation of the DB02336E message. In this case, the customer site had chosen not to set up LIST/LOCK coupler structures which would be needed to run the command.
From the CA Datacom® Messages guide:
SHADOW cccccccc IGNORED, XES STRUCTURE UNAVAILABLE
You have issued either an ALTER_SHADOW_TO_MUFPLEX command or a MIGRATE_TO_SHADOW command against a Shadow MUF that has specified a MUFplex name for which valid LIST/LOCK coupler structures have not been defined. In the message text, cccccccc is either ALTER or MIGRATE to identify which command was issued.
Note: A primary/shadow pair of MUFs may execute without a Coupling Facility, but in that case the above two commands are not permitted.
From the CA Datacom® Messages guide, DB02336E action:
If you only want to transfer processing from the primary MUF to the Shadow MUF, issue an EOJ against the primary MUF. If the ALTER or MIGRATE capability is required, the MUFs must be restarted with a name specified in the MUFPLEX MUF startup option for which Coupling Facility structures have been defined, or Coupling Facility LIST/LOCK structures must be defined which are consistent with the MUFPLEX startup option.
In this case, the customer has no plans to set up LIST/LOCK coupler structures which would be needed to run the command. So, the DB02336E error is legitimate and MIGRATE_TO_SHADOW command is not available for this site.
Customer will continue to use the EOJ process as they have in the past.
CA Datacom® Messages guide
CA Datacom® Core - 15.0 sections
"Connecting to z/OS Using Cross-System Coupling Facility (XCF)"
"Shadow MUF Environment"