Effectively Plan for Your Move to the Cloud
Tue, Jun 27, 2023 12:00 PM CDT{LOCAL_TZ} Read More
Effectively Plan for Your Move to the Cloud
Tue, Jun 27, 2023 12:00 PM CDT{LOCAL_TZ} Read More
Join Rocket Software’s Jeroen van Dun, Senior Manager, Product Management, for a future-facing discussion about AI, ML, and IBM i strategy.
Jeroen van Dun is a Senior Manager, Product Management at Rocket Software. Read More
Mainframe modernization holds the key to IBM i success CIO Read More
Having been busy recently performing presentations to various user groups and conferences I noticed an oversight in my work. In my presentations I had given an example of using the ON-EXIT group showing how I can use an indicator to indicate if an error had occurred in the procedure or subprocedure. In my post, on this website, about ON-EXIT I only mentioned it in passing. In this post I want to overcome oversight to show how I can do this.
The ON-EXIT group can be added to the end of every procedure or subprocedure in a RPG program. Regardless of whether the procedure or subprocedures errors or not, the code within the ON-EXIT group is always executed.
Let me start with my first example program, this one does not have any procedures or subprocedures:
Read more » Read More
The detail that I did not include regarding this service and IASPs is this – by default, the DUMP_PLAN_CACHE service only copies Plan Cache entries for those queries referencing tables in the System ASP.
That means if you had a critical query like the following and DBLIB resided in an IASP, then the Plan Cache snapshot would contain no record of this query. Read More