$re = '/(?ms)(?<date>[0-9]{1,2}\/[0-9]{1,2}\/[0-9]{4})\s(?<time>[0-9]{2}:[0-9]{2}:[0-9]{2})\s-\sProcess\((?<process>.*?)\)\sUser\((?<user>.*?)\)\sProgram\((?<program>.*?)\)\n\s*Host\((?<host>.*?)\)\sInstallation\((?<installation>.*?)\)\s*VRMF\((?<vrmf>.*?)\)\sQMgr\((?<qmgr>.*?)\)\s*(?<errorCode>AMQ[0-9]{4}):\s(?<errorDesc>.*?)EXPLANATION:\s*(?<explanation>.*?)ACTION:\s*(?<action>.*?)\s-{1,10}\s(?<source>.*?)\s\:\s(?<linenumber>[0-9]{0,4})\s-{50,60}/m';
$str = '10/26/2021 12:39:50 - Process(8272.240) User(IBMWebSphMQ05) Program(runmqlsr.exe)
Host(IBMMQ02APWPDCL) Installation(Installation1)
VRMF(9.0.0.3) QMgr(DTCC)
AMQ9616: The CipherSpec proposed is not enabled on the server.
EXPLANATION:
The SSL or TLS subsystem at the server end of a channel been configured in such
a way that it has rejected the CipherSpec proposed by an SSL or TLS client.
This rejection occurred during the secure socket handshake (i.e. it happened
before the proposed CipherSpec was compared with the CipherSpec in the server
channel definition).
This error most commonly occurs when the choice of acceptable CipherSpecs has
been limited in one of the following ways:
(a) The server queue manager SSLFipsRequired attribute is set to YES and the
channel is using a CipherSpec which is not FIPS-certified on the server.
(b) The server queue manager EncryptionPolicySuiteB attribute has been set to a
value other than NONE and the channel is using a CipherSpec which does not
meet the server\'s configured Suite B security level.
(c) The protocol used by the channel has been deprecated. Note that IBM may
need to deprecate a protocol via product maintenance in response to a
security vulnerability, for example SSLv3 has been deprecated. Continued use
of SSLv3 protocol is not recommended but may be enabled by setting
environment variable AMQ_SSL_V3_ENABLE=TRUE.
(d) The requested CipherSpec has been deprecated. Note that IBM may need to
deprecate a CipherSpec via product maintenance in response to a security
vulnerability, for example RC4_MD5_US has been deprecated. Continued use of
deprecated CipherSpecs is not recommended but may be enabled by setting
environment variable AMQ_SSL_WEAK_CIPHER_ENABLE=<CipherSpec>. For example,
AMQ_SSL_WEAK_CIPHER_ENABLE=RC4_MD5_US
The channel is \'????\'; in some cases its name cannot be determined and so is
shown as \'????\'. The channel did not start.
The remote host name is \'vmpqg17seapd (10.12.112.81)\'.
ACTION:
Analyse why the proposed CipherSpec was not enabled on the server. Alter the
client CipherSpec, or reconfigure the server to accept the original client
CipherSpec. Restart the channel.
This message might occur after applying IBM MQ maintenance because the FIPS and
Suite B standards are updated periodically. When such changes occur, IBM MQ is
also updated to implement the latest standard. As a result, you might see
changes in behavior after applying maintenance. For more information about the
versions of FIPS and Suite B standards enforced by IBM MQ, refer to the readme:
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006097
----- amqccisa.c : 7899 -------------------------------------------------------
10/26/2021 12:39:50 - Process(8272.240) User(IBMWebSphMQ05) Program(runmqlsr.exe)
Host(IBMMQ02APWPDCL) Installation(Installation1)
VRMF(9.0.0.3) QMgr(DTCC)
AMQ9999: Channel \'????\' to host \'vmpqg17seapd (10.12.112.81)\' ended abnormally.
EXPLANATION:
The channel program running under process ID 8272(22164) for channel \'????\'
ended abnormally. The host name is \'vmpqg17seapd (10.12.112.81)\'; in some cases
the host name cannot be determined and so is shown as \'????\'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 938 --------------------------------------------------------
10/26/2021 12:39:50 - Process(8272.241) User(IBMWebSphMQ05) Program(runmqlsr.exe)
Host(IBMMQ02APWPDCL) Installation(Installation1)
VRMF(9.0.0.3) QMgr(DTCC)
AMQ9616: The CipherSpec proposed is not enabled on the server.
EXPLANATION:
The SSL or TLS subsystem at the server end of a channel been configured in such
a way that it has rejected the CipherSpec proposed by an SSL or TLS client.
This rejection occurred during the secure socket handshake (i.e. it happened
before the proposed CipherSpec was compared with the CipherSpec in the server
channel definition).
This error most commonly occurs when the choice of acceptable CipherSpecs has
been limited in one of the following ways:
(a) The server queue manager SSLFipsRequired attribute is set to YES and the
channel is using a CipherSpec which is not FIPS-certified on the server.
(b) The server queue manager EncryptionPolicySuiteB attribute has been set to a
value other than NONE and the channel is using a CipherSpec which does not
meet the server\'s configured Suite B security level.
(c) The protocol used by the channel has been deprecated. Note that IBM may
need to deprecate a protocol via product maintenance in response to a
security vulnerability, for example SSLv3 has been deprecated. Continued use
of SSLv3 protocol is not recommended but may be enabled by setting
environment variable AMQ_SSL_V3_ENABLE=TRUE.
(d) The requested CipherSpec has been deprecated. Note that IBM may need to
deprecate a CipherSpec via product maintenance in response to a security
vulnerability, for example RC4_MD5_US has been deprecated. Continued use of
deprecated CipherSpecs is not recommended but may be enabled by setting
environment variable AMQ_SSL_WEAK_CIPHER_ENABLE=<CipherSpec>. For example,
AMQ_SSL_WEAK_CIPHER_ENABLE=RC4_MD5_US
The channel is \'????\'; in some cases its name cannot be determined and so is
shown as \'????\'. The channel did not start.
The remote host name is \'vmpqg17seapd (10.12.112.81)\'.
ACTION:
Analyse why the proposed CipherSpec was not enabled on the server. Alter the
client CipherSpec, or reconfigure the server to accept the original client
CipherSpec. Restart the channel.
This message might occur after applying IBM MQ maintenance because the FIPS and
Suite B standards are updated periodically. When such changes occur, IBM MQ is
also updated to implement the latest standard. As a result, you might see
changes in behavior after applying maintenance. For more information about the
versions of FIPS and Suite B standards enforced by IBM MQ, refer to the readme:
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006097
----- amqccisa.c : 7899 -------------------------------------------------------
10/26/2021 12:39:50 - Process(8272.241) User(IBMWebSphMQ05) Program(runmqlsr.exe)
Host(IBMMQ02APWPDCL) Installation(Installation1)
VRMF(9.0.0.3) QMgr(DTCC)
AMQ9999: Channel \'????\' to host \'vmpqg17seapd (10.12.112.81)\' ended abnormally.
EXPLANATION:
The channel program running under process ID 8272(23212) for channel \'????\'
ended abnormally. The host name is \'vmpqg17seapd (10.12.112.81)\'; in some cases
the host name cannot be determined and so is shown as \'????\'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 938 --------------------------------------------------------
10/26/2021 12:39:50 - Process(8272.242) User(IBMWebSphMQ05) Program(runmqlsr.exe)
Host(IBMMQ02APWPDCL) Installation(Installation1)
VRMF(9.0.0.3) QMgr(DTCC)
AMQ9616: The CipherSpec proposed is not enabled on the server.
EXPLANATION:
The SSL or TLS subsystem at the server end of a channel been configured in such
a way that it has rejected the CipherSpec proposed by an SSL or TLS client.
This rejection occurred during the secure socket handshake (i.e. it happened
before the proposed CipherSpec was compared with the CipherSpec in the server
channel definition).
This error most commonly occurs when the choice of acceptable CipherSpecs has
been limited in one of the following ways:
(a) The server queue manager SSLFipsRequired attribute is set to YES and the
channel is using a CipherSpec which is not FIPS-certified on the server.
(b) The server queue manager EncryptionPolicySuiteB attribute has been set to a
value other than NONE and the channel is using a CipherSpec which does not
meet the server\'s configured Suite B security level.
(c) The protocol used by the channel has been deprecated. Note that IBM may
need to deprecate a protocol via product maintenance in response to a
security vulnerability, for example SSLv3 has been deprecated. Continued use
of SSLv3 protocol is not recommended but may be enabled by setting
environment variable AMQ_SSL_V3_ENABLE=TRUE.
(d) The requested CipherSpec has been deprecated. Note that IBM may need to
deprecate a CipherSpec via product maintenance in response to a security
vulnerability, for example RC4_MD5_US has been deprecated. Continued use of
deprecated CipherSpecs is not recommended but may be enabled by setting
environment variable AMQ_SSL_WEAK_CIPHER_ENABLE=<CipherSpec>. For example,
AMQ_SSL_WEAK_CIPHER_ENABLE=RC4_MD5_US
The channel is \'????\'; in some cases its name cannot be determined and so is
shown as \'????\'. The channel did not start.
The remote host name is \'vmpqg17seapd (10.12.112.81)\'.
ACTION:
Analyse why the proposed CipherSpec was not enabled on the server. Alter the
client CipherSpec, or reconfigure the server to accept the original client
CipherSpec. Restart the channel.
This message might occur after applying IBM MQ maintenance because the FIPS and
Suite B standards are updated periodically. When such changes occur, IBM MQ is
also updated to implement the latest standard. As a result, you might see
changes in behavior after applying maintenance. For more information about the
versions of FIPS and Suite B standards enforced by IBM MQ, refer to the readme:
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006097
----- amqccisa.c : 7899 -------------------------------------------------------
10/26/2021 12:39:50 - Process(8272.242) User(IBMWebSphMQ05) Program(runmqlsr.exe)
Host(IBMMQ02APWPDCL) Installation(Installation1)
VRMF(9.0.0.3) QMgr(DTCC)
AMQ9999: Channel \'????\' to host \'vmpqg17seapd (10.12.112.81)\' ended abnormally.
EXPLANATION:
The channel program running under process ID 8272(25820) for channel \'????\'
ended abnormally. The host name is \'vmpqg17seapd (10.12.112.81)\'; in some cases
the host name cannot be determined and so is shown as \'????\'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 938 --------------------------------------------------------
10/26/2021 12:39:50 - Process(8272.243) User(IBMWebSphMQ05) Program(runmqlsr.exe)
Host(IBMMQ02APWPDCL) Installation(Installation1)
VRMF(9.0.0.3) QMgr(DTCC)
AMQ9616: The CipherSpec proposed is not enabled on the server.
EXPLANATION:
The SSL or TLS subsystem at the server end of a channel been configured in such
a way that it has rejected the CipherSpec proposed by an SSL or TLS client.
This rejection occurred during the secure socket handshake (i.e. it happened
before the proposed CipherSpec was compared with the CipherSpec in the server
channel definition).
This error most commonly occurs when the choice of acceptable CipherSpecs has
been limited in one of the following ways:
(a) The server queue manager SSLFipsRequired attribute is set to YES and the
channel is using a CipherSpec which is not FIPS-certified on the server.
(b) The server queue manager EncryptionPolicySuiteB attribute has been set to a
value other than NONE and the channel is using a CipherSpec which does not
meet the server\'s configured Suite B security level.
(c) The protocol used by the channel has been deprecated. Note that IBM may
need to deprecate a protocol via product maintenance in response to a
security vulnerability, for example SSLv3 has been deprecated. Continued use
of SSLv3 protocol is not recommended but may be enabled by setting
environment variable AMQ_SSL_V3_ENABLE=TRUE.
(d) The requested CipherSpec has been deprecated. Note that IBM may need to
deprecate a CipherSpec via product maintenance in response to a security
vulnerability, for example RC4_MD5_US has been deprecated. Continued use of
deprecated CipherSpecs is not recommended but may be enabled by setting
environment variable AMQ_SSL_WEAK_CIPHER_ENABLE=<CipherSpec>. For example,
AMQ_SSL_WEAK_CIPHER_ENABLE=RC4_MD5_US
The channel is \'????\'; in some cases its name cannot be determined and so is
shown as \'????\'. The channel did not start.
The remote host name is \'vmpqg17seapd (10.12.112.81)\'.
ACTION:
Analyse why the proposed CipherSpec was not enabled on the server. Alter the
client CipherSpec, or reconfigure the server to accept the original client
CipherSpec. Restart the channel.
This message might occur after applying IBM MQ maintenance because the FIPS and
Suite B standards are updated periodically. When such changes occur, IBM MQ is
also updated to implement the latest standard. As a result, you might see
changes in behavior after applying maintenance. For more information about the
versions of FIPS and Suite B standards enforced by IBM MQ, refer to the readme:
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006097
----- amqccisa.c : 7899 -------------------------------------------------------
10/26/2021 12:39:50 - Process(8272.243) User(IBMWebSphMQ05) Program(runmqlsr.exe)
Host(IBMMQ02APWPDCL) Installation(Installation1)
VRMF(9.0.0.3) QMgr(DTCC)
AMQ9999: Channel \'????\' to host \'vmpqg17seapd (10.12.112.81)\' ended abnormally.
EXPLANATION:
The channel program running under process ID 8272(6588) for channel \'????\'
ended abnormally. The host name is \'vmpqg17seapd (10.12.112.81)\'; in some cases
the host name cannot be determined and so is shown as \'????\'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 938 --------------------------------------------------------
10/26/2021 12:39:50 - Process(8272.244) User(IBMWebSphMQ05) Program(runmqlsr.exe)
Host(IBMMQ02APWPDCL) Installation(Installation1)
VRMF(9.0.0.3) QMgr(DTCC)
AMQ9616: The CipherSpec proposed is not enabled on the server.
EXPLANATION:
The SSL or TLS subsystem at the server end of a channel been configured in such
a way that it has rejected the CipherSpec proposed by an SSL or TLS client.
This rejection occurred during the secure socket handshake (i.e. it happened
before the proposed CipherSpec was compared with the CipherSpec in the server
channel definition).
This error most commonly occurs when the choice of acceptable CipherSpecs has
been limited in one of the following ways:
(a) The server queue manager SSLFipsRequired attribute is set to YES and the
channel is using a CipherSpec which is not FIPS-certified on the server.
(b) The server queue manager EncryptionPolicySuiteB attribute has been set to a
value other than NONE and the channel is using a CipherSpec which does not
meet the server\'s configured Suite B security level.
(c) The protocol used by the channel has been deprecated. Note that IBM may
need to deprecate a protocol via product maintenance in response to a
security vulnerability, for example SSLv3 has been deprecated. Continued use
of SSLv3 protocol is not recommended but may be enabled by setting
environment variable AMQ_SSL_V3_ENABLE=TRUE.
(d) The requested CipherSpec has been deprecated. Note that IBM may need to
deprecate a CipherSpec via product maintenance in response to a security
vulnerability, for example RC4_MD5_US has been deprecated. Continued use of
deprecated CipherSpecs is not recommended but may be enabled by setting
environment variable AMQ_SSL_WEAK_CIPHER_ENABLE=<CipherSpec>. For example,
AMQ_SSL_WEAK_CIPHER_ENABLE=RC4_MD5_US
The channel is \'????\'; in some cases its name cannot be determined and so is
shown as \'????\'. The channel did not start.
The remote host name is \'vmpqg17seapd (10.12.112.81)\'.
ACTION:
Analyse why the proposed CipherSpec was not enabled on the server. Alter the
client CipherSpec, or reconfigure the server to accept the original client
CipherSpec. Restart the channel.
This message might occur after applying IBM MQ maintenance because the FIPS and
Suite B standards are updated periodically. When such changes occur, IBM MQ is
also updated to implement the latest standard. As a result, you might see
changes in behavior after applying maintenance. For more information about the
versions of FIPS and Suite B standards enforced by IBM MQ, refer to the readme:
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006097
----- amqccisa.c : 7899 -------------------------------------------------------
10/26/2021 12:39:50 - Process(8272.244) User(IBMWebSphMQ05) Program(runmqlsr.exe)
Host(IBMMQ02APWPDCL) Installation(Installation1)
VRMF(9.0.0.3) QMgr(DTCC)
AMQ9999: Channel \'????\' to host \'vmpqg17seapd (10.12.112.81)\' ended abnormally.
EXPLANATION:
The channel program running under process ID 8272(12328) for channel \'????\'
ended abnormally. The host name is \'vmpqg17seapd (10.12.112.81)\'; in some cases
the host name cannot be determined and so is shown as \'????\'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 938 --------------------------------------------------------
10/26/2021 12:39:50 - Process(8272.245) User(IBMWebSphMQ05) Program(runmqlsr.exe)
Host(IBMMQ02APWPDCL) Installation(Installation1)
VRMF(9.0.0.3) QMgr(DTCC)
AMQ9616: The CipherSpec proposed is not enabled on the server.
EXPLANATION:
The SSL or TLS subsystem at the server end of a channel been configured in such
a way that it has rejected the CipherSpec proposed by an SSL or TLS client.
This rejection occurred during the secure socket handshake (i.e. it happened
before the proposed CipherSpec was compared with the CipherSpec in the server
channel definition).
This error most commonly occurs when the choice of acceptable CipherSpecs has
been limited in one of the following ways:
(a) The server queue manager SSLFipsRequired attribute is set to YES and the
channel is using a CipherSpec which is not FIPS-certified on the server.
(b) The server queue manager EncryptionPolicySuiteB attribute has been set to a
value other than NONE and the channel is using a CipherSpec which does not
meet the server\'s configured Suite B security level.
(c) The protocol used by the channel has been deprecated. Note that IBM may
need to deprecate a protocol via product maintenance in response to a
security vulnerability, for example SSLv3 has been deprecated. Continued use
of SSLv3 protocol is not recommended but may be enabled by setting
environment variable AMQ_SSL_V3_ENABLE=TRUE.
(d) The requested CipherSpec has been deprecated. Note that IBM may need to
deprecate a CipherSpec via product maintenance in response to a security
vulnerability, for example RC4_MD5_US has been deprecated. Continued use of
deprecated CipherSpecs is not recommended but may be enabled by setting
environment variable AMQ_SSL_WEAK_CIPHER_ENABLE=<CipherSpec>. For example,
AMQ_SSL_WEAK_CIPHER_ENABLE=RC4_MD5_US
The channel is \'????\'; in some cases its name cannot be determined and so is
shown as \'????\'. The channel did not start.
The remote host name is \'vmpqg17seapd (10.12.112.81)\'.
ACTION:
Analyse why the proposed CipherSpec was not enabled on the server. Alter the
client CipherSpec, or reconfigure the server to accept the original client
CipherSpec. Restart the channel.
This message might occur after applying IBM MQ maintenance because the FIPS and
Suite B standards are updated periodically. When such changes occur, IBM MQ is
also updated to implement the latest standard. As a result, you might see
changes in behavior after applying maintenance. For more information about the
versions of FIPS and Suite B standards enforced by IBM MQ, refer to the readme:
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006097
----- amqccisa.c : 7899 -------------------------------------------------------
10/26/2021 12:39:50 - Process(8272.245) User(IBMWebSphMQ05) Program(runmqlsr.exe)
Host(IBMMQ02APWPDCL) Installation(Installation1)
VRMF(9.0.0.3) QMgr(DTCC)
AMQ9999: Channel \'????\' to host \'vmpqg17seapd (10.12.112.81)\' ended abnormally.
EXPLANATION:
The channel program running under process ID 8272(23808) for channel \'????\'
ended abnormally. The host name is \'vmpqg17seapd (10.12.112.81)\'; in some cases
the host name cannot be determined and so is shown as \'????\'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 938 --------------------------------------------------------
10/26/2021 12:39:50 - Process(8272.246) User(IBMWebSphMQ05) Program(runmqlsr.exe)
Host(IBMMQ02APWPDCL) Installation(Installation1)
VRMF(9.0.0.3) QMgr(DTCC)
AMQ9616: The CipherSpec proposed is not enabled on the server.
EXPLANATION:
The SSL or TLS subsystem at the server end of a channel been configured in such
a way that it has rejected the CipherSpec proposed by an SSL or TLS client.
This rejection occurred during the secure socket handshake (i.e. it happened
before the proposed CipherSpec was compared with the CipherSpec in the server
channel definition).
This error most commonly occurs when the choice of acceptable CipherSpecs has
been limited in one of the following ways:
(a) The server queue manager SSLFipsRequired attribute is set to YES and the
channel is using a CipherSpec which is not FIPS-certified on the server.
(b) The server queue manager EncryptionPolicySuiteB attribute has been set to a
value other than NONE and the channel is using a CipherSpec which does not
meet the server\'s configured Suite B security level.
(c) The protocol used by the channel has been deprecated. Note that IBM may
need to deprecate a protocol via product maintenance in response to a
security vulnerability, for example SSLv3 has been deprecated. Continued use
of SSLv3 protocol is not recommended but may be enabled by setting
environment variable AMQ_SSL_V3_ENABLE=TRUE.
(d) The requested CipherSpec has been deprecated. Note that IBM may need to
deprecate a CipherSpec via product maintenance in response to a security
vulnerability, for example RC4_MD5_US has been deprecated. Continued use of
deprecated CipherSpecs is not recommended but may be enabled by setting
environment variable AMQ_SSL_WEAK_CIPHER_ENABLE=<CipherSpec>. For example,
AMQ_SSL_WEAK_CIPHER_ENABLE=RC4_MD5_US
The channel is \'????\'; in some cases its name cannot be determined and so is
shown as \'????\'. The channel did not start.
The remote host name is \'vmpqg17seapd (10.12.112.81)\'.
ACTION:
Analyse why the proposed CipherSpec was not enabled on the server. Alter the
client CipherSpec, or reconfigure the server to accept the original client
CipherSpec. Restart the channel.
This message might occur after applying IBM MQ maintenance because the FIPS and
Suite B standards are updated periodically. When such changes occur, IBM MQ is
also updated to implement the latest standard. As a result, you might see
changes in behavior after applying maintenance. For more information about the
versions of FIPS and Suite B standards enforced by IBM MQ, refer to the readme:
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006097
----- amqccisa.c : 7899 -------------------------------------------------------
10/26/2021 12:39:50 - Process(8272.246) User(IBMWebSphMQ05) Program(runmqlsr.exe)
Host(IBMMQ02APWPDCL) Installation(Installation1)
VRMF(9.0.0.3) QMgr(DTCC)
AMQ9999: Channel \'????\' to host \'vmpqg17seapd (10.12.112.81)\' ended abnormally.
EXPLANATION:
The channel program running under process ID 8272(21220) for channel \'????\'
ended abnormally. The host name is \'vmpqg17seapd (10.12.112.81)\'; in some cases
the host name cannot be determined and so is shown as \'????\'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 938 --------------------------------------------------------
10/26/2021 12:39:50 - Process(8272.247) User(IBMWebSphMQ05) Program(runmqlsr.exe)
Host(IBMMQ02APWPDCL) Installation(Installation1)
VRMF(9.0.0.3) QMgr(DTCC)
AMQ9616: The CipherSpec proposed is not enabled on the server.
EXPLANATION:
The SSL or TLS subsystem at the server end of a channel been configured in such
a way that it has rejected the CipherSpec proposed by an SSL or TLS client.
This rejection occurred during the secure socket handshake (i.e. it happened
before the proposed CipherSpec was compared with the CipherSpec in the server
channel definition).
This error most commonly occurs when the choice of acceptable CipherSpecs has
been limited in one of the following ways:
(a) The server queue manager SSLFipsRequired attribute is set to YES and the
channel is using a CipherSpec which is not FIPS-certified on the server.
(b) The server queue manager EncryptionPolicySuiteB attribute has been set to a
value other than NONE and the channel is using a CipherSpec which does not
meet the server\'s configured Suite B security level.
(c) The protocol used by the channel has been deprecated. Note that IBM may
need to deprecate a protocol via product maintenance in response to a
security vulnerability, for example SSLv3 has been deprecated. Continued use
of SSLv3 protocol is not recommended but may be enabled by setting
environment variable AMQ_SSL_V3_ENABLE=TRUE.
(d) The requested CipherSpec has been deprecated. Note that IBM may need to
deprecate a CipherSpec via product maintenance in response to a security
vulnerability, for example RC4_MD5_US has been deprecated. Continued use of
deprecated CipherSpecs is not recommended but may be enabled by setting
environment variable AMQ_SSL_WEAK_CIPHER_ENABLE=<CipherSpec>. For example,
AMQ_SSL_WEAK_CIPHER_ENABLE=RC4_MD5_US
The channel is \'????\'; in some cases its name cannot be determined and so is
shown as \'????\'. The channel did not start.
The remote host name is \'vmpqg17seapd (10.12.112.81)\'.
ACTION:
Analyse why the proposed CipherSpec was not enabled on the server. Alter the
client CipherSpec, or reconfigure the server to accept the original client
CipherSpec. Restart the channel.
This message might occur after applying IBM MQ maintenance because the FIPS and
Suite B standards are updated periodically. When such changes occur, IBM MQ is
also updated to implement the latest standard. As a result, you might see
changes in behavior after applying maintenance. For more information about the
versions of FIPS and Suite B standards enforced by IBM MQ, refer to the readme:
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006097
----- amqccisa.c : 7899 -------------------------------------------------------
10/26/2021 12:39:50 - Process(8272.247) User(IBMWebSphMQ05) Program(runmqlsr.exe)
Host(IBMMQ02APWPDCL) Installation(Installation1)
VRMF(9.0.0.3) QMgr(DTCC)
AMQ9999: Channel \'????\' to host \'vmpqg17seapd (10.12.112.81)\' ended abnormally.
EXPLANATION:
The channel program running under process ID 8272(21620) for channel \'????\'
ended abnormally. The host name is \'vmpqg17seapd (10.12.112.81)\'; in some cases
the host name cannot be determined and so is shown as \'????\'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 938 --------------------------------------------------------
10/26/2021 12:39:51 - Process(8272.248) User(IBMWebSphMQ05) Program(runmqlsr.exe)
Host(IBMMQ02APWPDCL) Installation(Installation1)
VRMF(9.0.0.3) QMgr(DTCC)
AMQ9616: The CipherSpec proposed is not enabled on the server.
EXPLANATION:
The SSL or TLS subsystem at the server end of a channel been configured in such
a way that it has rejected the CipherSpec proposed by an SSL or TLS client.
This rejection occurred during the secure socket handshake (i.e. it happened
before the proposed CipherSpec was compared with the CipherSpec in the server
channel definition).
This error most commonly occurs when the choice of acceptable CipherSpecs has
been limited in one of the following ways:
(a) The server queue manager SSLFipsRequired attribute is set to YES and the
channel is using a CipherSpec which is not FIPS-certified on the server.
(b) The server queue manager EncryptionPolicySuiteB attribute has been set to a
value other than NONE and the channel is using a CipherSpec which does not
meet the server\'s configured Suite B security level.
(c) The protocol used by the channel has been deprecated. Note that IBM may
need to deprecate a protocol via product maintenance in response to a
security vulnerability, for example SSLv3 has been deprecated. Continued use
of SSLv3 protocol is not recommended but may be enabled by setting
environment variable AMQ_SSL_V3_ENABLE=TRUE.
(d) The requested CipherSpec has been deprecated. Note that IBM may need to
deprecate a CipherSpec via product maintenance in response to a security
vulnerability, for example RC4_MD5_US has been deprecated. Continued use of
deprecated CipherSpecs is not recommended but may be enabled by setting
environment variable AMQ_SSL_WEAK_CIPHER_ENABLE=<CipherSpec>. For example,
AMQ_SSL_WEAK_CIPHER_ENABLE=RC4_MD5_US
The channel is \'????\'; in some cases its name cannot be determined and so is
shown as \'????\'. The channel did not start.
The remote host name is \'vmpqg17seapd (10.12.112.81)\'.
ACTION:
Analyse why the proposed CipherSpec was not enabled on the server. Alter the
client CipherSpec, or reconfigure the server to accept the original client
CipherSpec. Restart the channel.
This message might occur after applying IBM MQ maintenance because the FIPS and
Suite B standards are updated periodically. When such changes occur, IBM MQ is
also updated to implement the latest standard. As a result, you might see
changes in behavior after applying maintenance. For more information about the
versions of FIPS and Suite B standards enforced by IBM MQ, refer to the readme:
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006097
----- amqccisa.c : 7899 -------------------------------------------------------
10/26/2021 12:39:51 - Process(8272.248) User(IBMWebSphMQ05) Program(runmqlsr.exe)
Host(IBMMQ02APWPDCL) Installation(Installation1)
VRMF(9.0.0.3) QMgr(DTCC)
AMQ9999: Channel \'????\' to host \'vmpqg17seapd (10.12.112.81)\' ended abnormally.
EXPLANATION:
The channel program running under process ID 8272(5464) for channel \'????\'
ended abnormally. The host name is \'vmpqg17seapd (10.12.112.81)\'; in some cases
the host name cannot be determined and so is shown as \'????\'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 938 --------------------------------------------------------';
preg_match_all($re, $str, $matches, PREG_SET_ORDER, 0);
// Print the entire match result
var_dump($matches);
Please keep in mind that these code samples are automatically generated and are not guaranteed to work. If you find any syntax errors, feel free to submit a bug report. For a full regex reference for PHP, please visit: http://php.net/manual/en/ref.pcre.php