RE: Logging of SQL statements -- MIDRANGE-L

Thanks Birgitta ! That is awesome and just what we are looking for. I wonder if there is a way to save that information.

Cyndi

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Birgitta Hauser
Sent: Monday, August 7, 2017 10:48 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: RE: Logging of SQL statements

Just have a look into the SQE Plan Cache (with the Client Access or ACS Analysis Tools).
Each SQL Statement needs an Access Plan. All Access Plans are stored in the SQE Plan Cache.
You can analyze the access plans and also can get the SQL statement (including the variable values set by host variables).
The access plans exist as long as no IPL is performed or the plan cache is manually cleared.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok) "What is worse than training your staff and losing them? Not training them and keeping them!"
"Train people well enough so they can leave, treat them well enough so they don't want to." (Richard Branson)

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Cyndi Bradberry
Sent: Montag, 7. August 2017 23:05
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Logging of SQL statements

We have C# running on Microsoft IIS handling our web services. They have found they are vulnerable to SQL injection attacks. They are working on programming their sites to not allow it, but we would like to have a belt and suspenders approach.

The files are journaled, but they really want to capture the entire SQL string if possible. I will look into the QIBM_QZDA_SQL1 and database monitoring.

Thanks for the suggestions.

Cyndi B.
Boise, ID

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD