RE: What does a *SQLPKG do?

OK, so *SQLPKG don't necessarily contain executable code.

Thanks



-----Original Message-----
From: Birgitta Hauser [mailto:Hauser@xxxxxxxxxxxxxxx]
Sent: Tuesday, April 18, 2017 12:32 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: RE: What does a *SQLPKG do?

If you are using dynamic SQL, you won't see it in the PRTSQLINF printer file

The SQL package includes the access plans for static or extended dynamic SQL statements.
The access plans are used for validation, ... but with the SQE access plans are first searched in the SQE Plan Cache (independent whether the SQL statements are static or dynamic).
If there is no access plan found, the SQL package is searched. If an access plan is found, it is validated.
If access plan is found, it is created by scratch.

In (embedded) SQL (Service-)Programs, the access plans for static SQL are automatically included and updated, i.e. the SQL package is included.
With PRTSQLINF, you'll get information about the access plans.

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)