What's the DB2 version and platform you are using?
What are you actually doing?

The error messages say the following:

$ db2 "? asn5150w"

ASN5150W MONITOR "<monitor_qualifier>". The program
         "<program_name>" is not running. The server is
         "<server_name>", and the schema is "<schema>".

Explanation:

The alert condition STATUS indicates that the program specified
in this message is not running.

User Response:

Verify the status of the program on the specified server.

$ db2 "? asn0059w"

ASN0059W CAPTURE "<capture_schema>". The SYNCHPOINT field in the
         IBMSNAP_PRUNCNTL table is not zeros for the CAPSTART of
         subscription with MAP_ID "<map_id>".

Explanation:

When the Apply program signals a full refresh to the Capture
program, the Apply program inserts a row for the CAPSTART signal
in the IBMSNAP_SIGNAL table. At the same time, the SYNCHPOINT
column of the IBMSNAP_PRUNCNTL table is set to hex zeroes. The
Capture program then responds to the Apply program to confirm
that the Capture program received the CAPSTART signal, as
follows: the Capture program sets the value for the SYNCHPOINT
column in the IBMSNAP_PRUNCNTL table to the number of the log
sequence that corresponds to the CAPSTART log record.  Because
the Apply program set the value in the SYNCHPOINT column to hex
zeroes, the Apply program checks if a nonzero value has been
inserted by the Capture program. The Capture program updates the
value for SYNCHPOINT, even if the value was not hex zeroes.
However, if the value for SYNCHPOINT is not hex zeroes, the
Capture program issues this warning that the value it found was
not expected.

This warning can occur if you issue the APPLY CAPSTART signal
yourself and do not completely simulate the actions of the Apply
program.

User Response:

This message is for your information only, and no action is
required.

What that means for you, I do not know because we have no details on your
scenario.