From what I know, the QDBSRVxx-jobs are mainly for maintaining the DB2 repository and data dictionary. As soon as you create/restore/alter something that’s of type file, you will find activity in these jobs. They take care of the content of files in lib QSYS2. QZDASOINIT-jobs are for client-server requests against the i5. So, if a client issues a “ALTER TABLE” sql, this will also trigger QDBSRV-jobs to take action. In some cases it takes some time for them to finish work. Since they run async with other jobs, you can discover a lock status. Another thing worth to look at is the async maintanence of existing accesspaths (LFs) the SQL-optimizer decides to use for a sql. Remember: LFs can be marked for MAINT(*DLY or *REBLD).