FPEV0187I <V1> - <Name> <Status> <Detect> <Level> <Location> <Type> <Dsg> <Lpar>
Explanation
This message is issued in response to a DISPLAY command or during OMEGAMON® Collector startup. It indicates that the indicated DB2® subsystem was auto-detected at the LPAR and is monitored with
limited functionality.
- <V1> is the name of the master controller inside the OMEGAMON Collector (MSTR).
- <Name> is the DB2 subsystem ID.
- <Status> is the monitoring status of the DB2 subsystem, which can be one of the following:
- DENIED
- The OMEGAMON Collector started task user ID does not have the required privileges to connect (IDENTIFY) to this DB2 subsystem.
- DOWN
- The DB2 subsystem is not running.
- EXCLUDED
- The DB2 subsystem is excluded from monitoring. This
happens in the following cases:
- The indicated DB2 subsystem was marked in the Configuration Tool as not to be monitored.
- Monitoring of the indicated DB2 subsystem was stopped by an operator command.
- The monitoring subtask stopped because of a problem.
For other possible reasons check the SYSPRINT for messages that explain why the DB2 subsystem is not monitored.
- IGNORED
- The version of this DB2 subsystem is not supported. Therefore, this DB2 subsystem cannot be monitored.
- INITIAL
- The DB2 subsystem is known to the OMEGAMON Collector, but there is neither a connection established nor a monitoring subtask started yet.
- MONITORED
- The DB2 subsystem is monitored.
- MONDSG
- The indicated DB2 subsystem is monitored implicitly. The DB2 subsystem is a local member of a data sharing group that is excluded from monitoring (configuration) or it is not configured while AUTODETECT is disabled. The DB2 subsystem is monitored implicitly by another local data sharing group member without starting any additional subtasks for monitoring this DB2 subsystem.
- RESTRICT
- The DB2 subsystem is known to the OMEGAMON Collector, but the OMEGAMON Collector is not authorized to connect to the DB2 subsystem because the DB2 subsystem is started in restricted access mode (maintenance).
- UNKNOWN
- The status of the DB2 subsystem cannot be determined for
one of the following reasons:
- The DB2 subsystem is a remote member of a data sharing group and no local member of the data sharing group is currently monitored. Therefore, no information about the DB2 subsystem can be obtained.
- The DB2 subsystem is a local member of a data sharing group that is excluded from monitoring (configuration) or it is not configured while AUTODETECT is disabled. This DB2 subsystem can be monitored implicitly by another local data sharing group member without starting additional subtasks for monitoring this DB2 subsystem. If explicit monitoring of all local data sharing group members is stopped, no implicit monitoring is possible, and therefore, no information can be obtained for local and remote members of the data sharing group.
- UP
- The DB2 subsystem is running, but the subtask that monitors this DB2 subsystem is not yet started.
<Detect> indicates whether the DB2 subsystem was found by means of auto-detection.- Y
- This DB2 subsystem was auto-detected.
- N
- This DB2 subsystem was configured explicitly or is a remote or implicitly monitored data sharing group member.
- <Level> indicates the DB2
version, release, and modification level as a six-digit character string.
- <Location> indicates where the DB2
subsystem is running.
- LOCAL
- The DB2 subsystem runs in the same LPAR as the OMEGAMON Collector.
- REMOTE
- The DB2 subsystem is a data sharing group member that does not run on the same LPAR as the OMEGAMON Collector.
- <Type> indicates the type of the DB2 subsystem.
- SINGLE
- The DB2 subsystem does not run in a data sharing group environment.
- MEMBER
- The DB2 subsystem is a member of a data sharing group.
- <Dsg> The name of the data sharing group to which this DB2 subsystem belongs.
- <Lpar> indicates the name of the z/OS® system where the member is running or was last running before monitoring stopped.
User response
If the status is DENIED, contact your security administrator and request authority for the OMEGAMON Collector to access this DB2 subsystem.