Fixes are available
Closed as fixed if next.
When one or more instances are configured to use Apache Zookeeper for the name service, Streams Studio instance management functions, including create, start, stop, and refresh, might fail. Known error messages for this problem include: Start Instance <instance_name> failed: Unable to login to instance '<instance_name>'. Unable to access the started instance's name service. Unable to login to instance '<instance_name>'. Unable to access the started instance's AAS service. Unable to refresh the instance state: Unable to get a handle to the SAM for instance <instance_name>.
To work around the problem, use a file system (FS), or a distributed name server (DN) for the name service.
Users Affected: Users who use the Streams Studio for instance management and Apache ZooKeeper for the name service. Problem Description: See Error Description. Problem Conclusion: This problem is fixed in Version 3.1 Fix Pack 1 and later fix packs.
Reported component name
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Applicable component levels