QZDASSINIT job creates joblog on disconnect - then loops

[annneal@aol.com]

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?

[Guest.Visitor]

Potentially problem with exit point. Do: WRKREGINF QIBM_QZDA_SQL* and take option 8 to see if there are any exit points registered. If there are, remove them and recycle ODBC. Recycling is accomplished by doing: ENDHOSTSVR *DATABASE ENDPJ QUSRWRK QZDASOINIT OPTION(*IMMED) /* wait till all QZDASOINIT jobs are gone */ STRHOSTSVR *DATABASE If there are no exit points, call IBM support.