We have an ODBC connected job that calls stored procedures. We have tested on several different i5 machines, and on some it runs to completion and on one i5 the joblog is created like the job ended (Print job log at disconnect on the Diagnostic tab), yet the job can be displayed (same job/user/number) and a new joblog is looping with message MCH3601 from From module . . . . . . . . : QZDASQL From procedure . . . . . . : PGMEXIT followed by PWS0005 From module . . . . . . . . : QZDASQL From procedure . . . . . . : SNDMSG looping quickly and of course the joblog wraps. We tried this with a non SSL connection (QZDASOINIT job) with the same results. The job has to be ended manually. Has anyone seen a similar case?