Birgitta Hauser has worked on the IBM i and its predecessors since 1992 as a traditional RPG programmer and also as database and software engineer, focusing on IBM i application and database modernization. In July, 2019 she joined Fresche Solutions. She works in consulting and education as a trainer for RPG and SQL developers. Since 2002 she has frequently spoken at the COMMON User Groups and other IBM i and Power Conferences in Germany, other European Countries, USA and Canada. In addition, she is co-author of two IBM Redbooks and also the author of several articles and papers focusing on RPG and SQL for a German publisher and IBM DeveloperWorks. In 2015 she received the John Earl Speaker Scholarship Award. In 2018 she received the Al Barsa Memorial Scholarship Award, and she is an IBM Champion in 2020.
Guru: ACS 220.127.116.11 Content Assist Includes Prompt For SQL!
February 10, 2020 Birgitta Hauser
STRSQL, the green-screen facility for executing SQL Statements, has had its days. Nevertheless, many SQL users still prefer this legacy interface over the Access Client Solutions (ACS) Run SQL Scripts facility. Others use third-party tools to execute SQL statements. The common excuse has been that the Run SQL Script facility does not include a way to prompt SQL commands, tables, and columns. In ACS version 18.104.22.168, Content Assist includes prompting for SQL statements.
Before ACS Version 22.214.171.124, no prompting was available within the Run SQL Scripts Facility. To access tables, views or materialized query tables (MQTs), we needed to know …Read more
Guru: Logging SQL Errors And Warnings
October 30, 2017 Birgitta Hauser
If something goes wrong with an embedded SQL statement or an SQL routine (a trigger, stored procedure or user-defined function), the system does not crash. Instead, DB2 returns a negative SQL code and an SQL state that starts with something other than 00, 01, or 02. If the routine does not handle the error, the program continues to run.
It is good practice to log errors to a table, especially unexpected ones. Before you can log any errors, you need to know how an SQL error can be trapped and handled. You need to know how to write a condition …Read more