-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with docs.zowe.org/stable/user-guide/api-mediation/wto-message-on-startup/ #4133
Comments
It will be in Syslog if you ask the Luancher to redirect the message with the ZWEAM001I id and don't provide the changes to change this. |
But will it actually look like this in the SYSLOG:
I'm thinking you would see that in the job SYSPRINT DD, not the SYSLOG. In the SYSLOG, you'd probably see only:
|
The customer was complaining that they see 2024-09-30 10:17:53.814 ZWEAGW1:DiscoveryClient-InstanceInfoReplicator-%d:3335 jb892003 INFO ((o.z.a.g.c.GatewayHealthIndicator)) ZWEAM001I API Mediation Layer started in their Syslog. |
I'm curious if this was actually in the job SYSPRINT DD for Zowe STC, not the SYSLOG. |
If it's really important, we have internally contact for the customer to ask them |
Shouldn't we see this internally? When I look at the SYSLOG on our systems, I only see this message in the SYSPRINT DD. I don't see it issues in SYSLOG. It makes me wonder if the real requirement was that we issued a WTO whenever our service as up and available. |
Description
The doc contains this section:
Pages to Update
Screenshots
Expected behavior
Additional context
The text was updated successfully, but these errors were encountered: