Thanks Roy (and Javier).
Yes, that's what I thought, but here, from my understanding, you
take ALL the packages back to the lower * level, not just one or
you do is disable the function of the new FL for ALL packages, and
objects CREATED in the lower * FL will have to be bound or rebound
rrhe higher FL once you go back to it.
So, again from what I understand, it's like a subsystem-wide
(and any objects created in this mode will have to be bound/rebound
the higher FL, as I said above).
On Thu, 11 Oct 2018 at 07:23, Boxwell, Roy
<[login to unmask email]> wrote:
> What they mean is that if you have bound 10,000 Packages at ,
> and then see that some SQLs are going wrong for whatever
reason. You can
> then fall back the system to FL502 and REBIND the static
packages that are
> causing trouble leaving the rest, if they are **not** causing
> do not want 10,000 AUTOBINDs do you? Dynamic SQL is a bit
trickier as you
> have to bind the Dynamic SQL Access packages (SYSLHxx etc etc)
also at the
> lower FL level to stop any “rogue” SQLs running at
the bad FL level.
> APPLCOMPAT is really a package level attribute to peg packages
> FL501 even though you are happily running at FL503 –
This gives you time to
> fix things like ICIs etc.
> *Roy Boxwell*
> SOFTWARE ENGINEERING GMBH and SEGUS Inc.
> -Product Development-
> *Heinrichstrasse 83-8540239 Duesseldorf/Germany*
> *Tel. *
> *+49 (0)211 96149-675Fax +49 (0)211 96149-32Email:
**[login to unmask email]*
> <[login to unmask email]>
> *http://www.seg.de* http://www.seg.de
> *Software Engineering GmbHAmtsgericht Düsseldorf, HRB
> 37894Geschäftsführung: Gerhard Schubert, Ulf
> *From:* Aurora Emanuela Dellanno [mailto:[login to unmask email]
> *Sent:* Wednesday, October 10, 2018 3:26 PM
> *To:* [login to unmask email]
> *Subject:* [DB2-L] - Db2 12 star * function levels
> so, I read in the What's New book that "Activating a lower
> function level by itself does not immediately disable all use
> capabilities at higher function levels. Instead, it provides
> for limiting or disabling the use of capabilities at higher
> levels, while the problems encountered in higher function
> can someone please explain this to me in plain English? is it
> basically with the default APPLCOMPAT?
> This is confusing me even further: "applications that use
> a higher function level can continue to do so if they are not
> the reason for activating the lower function level" - how does
> what the reason for a function level is? do you need to have a
> friendly talk with it?
> TIA for anything that gets me out of this maze...
> -----End Original Message-----