Coding in RPG (IBM i/AS400). Using audit columns in our tables.

In this video, I'd like to talk about how you can add audit columns to your tables, where you can store information about every record. For example, you can add information about who inserted or updated the record, when.... etc.
I show you a few examples of fields that you can add.

Please, let me know what you think about it. Leave your comments below.
Don't forget to subscribe!

#ibmi #ibm #rpg #rpgle #rpgfree #newvideo #ibmtraining #ibmcoding #rpgtraining #sqlrpgle #sqltraining #as400 #common #modernize #ibmchampion

0:00 Introduction
0:45 Creating the table from within VSCode
2:30 Adding a generated always identity column as primary key
5:50 Two options for adding records to my table
8:40 Talking about audit columns
9:03 Adding a columns for storing the last operation made in a record
9:45 Adding a columns for storing the user that mades the last operation (insert or update)
10:15 Adding a columns for storing the job name from the last operation was made
10:45 Adding a column for storing the timestamp of the last operation made
12:05 Adding a new record to see how it is stored, with all the audit columns
14:06 Changing my table so the audit columns are going to be implicitly hidden
15:50 Is it possible to have audit columns in our physical files. Explanation.
16:38 Final comments and ending

[Steve-Richter]

I found it important to always provide a constraint name to the primary key:
constraint pk_newtable primary key( newtable_id )
Otherwise the system assigns a constraint name. Which then causes Mimix to sometimes throw errors when it replicates the table on the target system.

[higiniofuentes]

Sería interesante hacer una sección de sólo DB2, porque aquí no hay RPG(IV o V) de ningún tipo 😉!