-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add LIC and PAL log support #171
Conversation
Signed-off-by: Sanjula Ganepola <[email protected]>
Signed-off-by: Sanjula Ganepola <[email protected]>
Signed-off-by: Sanjula Ganepola <[email protected]>
Jesse,How are you getting access to the LIC and PAL log? What table is that information in?Sent from my iPhoneOn Dec 18, 2024, at 9:46 AM, Sanjula Ganepola ***@***.***> wrote:
Merged #171 into main.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Hello @thebeardedgeek. Users will define a STRWCH command that will watch for these logs. When a watch event is triggered the MANZAN handler (just an ILE program) will put the event data into a table ( |
That’s great! Is there a way to get to this same data using SQL to see what it would look like? I have a few systems I would like to use this for. Sent from my iPhoneOn Dec 18, 2024, at 10:13 AM, Sanjula Ganepola ***@***.***> wrote:
Hello @thebeardedgeek. Users will define a STRWCH command that will watch for these logs. When a watch event is triggered the MANZAN handler (just an ILE program) will put the event data into a table (MANZANMSG, MANZANVLOG, or MANZANPAL) which the Manzan distributor will read off of and then send to the appropriate user defined destinations.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
As you can see here in the architecture, we want to support having custom code to be able to query off the table. However, in giving this a try now, it looks like we have a restriction on Manzan where a destination must be specified for a data source which must be lifted in order to support this (glad you brought this up!). I will have a look at fixing this. To still see what the data looks like in the meantime, instead of starting Manzan, you could just start a watch program manually and specify it to call the Manzan As a side note since you are interested in these LIC and PAL logs, are you aware of any reproducible way to trigger new LIC or PAL log entries? I have been trying to find a way to test this feature in Manzan, but have not found an easy way to trigger new logs to test if they are properly added to the table and then sent to a destination. |
No description provided.