Well, it happened. A user with the following:
Special authority . . . . . . . . . . . . : *NONE
Initial program . . . . . . . . . . . . . : (redacted) Custom program
Initial menu . . . . . . . . . . . . . . . : *SIGNOFF
Library . . . . . . . . . . . . . . . . :
Limit capabilities . . . . . . . . . . . . : *YES
created a table in QGPL with the same name as a table in another library. Normally not an issue as the library list has QGPL at the end. But one user (luckily in IT) has his reversed and it was blowing up stuff.
This new table was completely unrelated to the existing table. In fact, it had strange column names which led me to believe it was derived from some gyrations of the system catalog. Like SYSTABLES, etc. Had our knickers in a twist to get rid of it quick so we didn't waste a bunch of time with it before deleting it.
The job it was created from? QZDASOINIT.
Tell me that some new IT intern cannot quickly grasp the system catalog with zero interaction with existing staff (different plants - different countries). All IBM i type development is done here. IT down there (1.5 people) is primarily tech support staff.
------------------------------
Robert Berendt IBMChampion
Business Systems Analyst, Lead
Dekko
Fort Wayne
------------------------------