Frosty the Coder
Legendary Poster
List,
During our package build request, when a table was changed, we had been in the habit of requesting that CNC:
A: End the HTML/JAS/Web (whatever!) instances for the environments being deployed to
B: Clearing F989998 and F989999 from central objects in those same environments
C: and restarting the HTML/JAS/Web instances for those environments.
Over the weekend, I was chatting w/a support CNC who said we no longer needed to
clear F989998 nor F989999 as the build process had been improved to do this automatically.
Is this true?
Are "delete serialized objects" and "deleting SQL Packages (iSeries)" the same sort of thing?
What about "bouncing the servers"?
Is this just an extreme method of "clearing cache"?
My bottom line question is:
What should we ask to do, that is beyond regular "build/deploy", when we are implementing table changes?
During our package build request, when a table was changed, we had been in the habit of requesting that CNC:
A: End the HTML/JAS/Web (whatever!) instances for the environments being deployed to
B: Clearing F989998 and F989999 from central objects in those same environments
C: and restarting the HTML/JAS/Web instances for those environments.
Over the weekend, I was chatting w/a support CNC who said we no longer needed to
clear F989998 nor F989999 as the build process had been improved to do this automatically.
Is this true?
Are "delete serialized objects" and "deleting SQL Packages (iSeries)" the same sort of thing?
What about "bouncing the servers"?
Is this just an extreme method of "clearing cache"?
My bottom line question is:
What should we ask to do, that is beyond regular "build/deploy", when we are implementing table changes?