Here's what i do. When i want to modify a system behaviour, i create copies of the system objects in a library that sit's above QSYS in the system portion of the library list. Then when the new copies of the objects are used instead of the IBM originals (which shouldn't be changed directly). - Create a new library [CRTLIB] (Don't start the name with a 'Q' and only use this lib to override IBM functions. It'll make it easier to manage) - Create a duplicate object from QPJOBLOG in the new library [CRTDUPOBJ] - Change whatever you need to on the duplicate object - Change your systems portion of the library list so that the new library is on top, above QSYS. [CHGSYSVAL QSYSLIBL (then prompt)] The next job you submit should go to the new outq. You shouldn't even need overrides. It's just a guess but i think the reason that your logs are still going to QEZJOBLOG is probably because your override is not in effect when the joblog is written. The only thing you need to be aware of with this approach is that whenever you upgrade the OS or any other time a system object is changed by IBM, you need to review what you've dup'd into your lib. Hope that helps!

Here's what i do. When i want to modify a system behaviour, i create copies of the system objects in a library that sit's above QSYS in the system portion of the library list. Then when the new copies of the objects are used instead of the IBM originals (which shouldn't be changed directly). - Create a new library [CRTLIB] (Don't start the name with a 'Q' and only use this lib to override IBM functions. It'll make it easier to manage) - Create a duplicate object from QPJOBLOG in the new library [CRTDUPOBJ] - Change whatever you need to on the duplicate object - Change your systems portion of the library list so that the new library is on top, above QSYS. [CHGSYSVAL QSYSLIBL (then prompt)] The next job you submit should go to the new outq. You shouldn't even need overrides. It's just a guess but i think the reason that your logs are still going to QEZJOBLOG is probably because your override is not in effect when the joblog is written. The only thing you need to be aware of with this approach is that whenever you upgrade the OS or any other time a system object is changed by IBM, you need to review what you've dup'd into your lib. Hope that helps!