Is it a specific program or service program procedure, that you want to debug? If yes, have you tried to set a matching service entry point (SEP)?
Original Message:
Sent: 3/30/2026 8:29:00 PM
From: Satid S
Subject: RE: Debug an IWS job
Dear Michael
Why not just initiate a connection from your IWS client to QZRCSRVS job in IBM i but do not proceed to run any thing yet. This way you can check for your Current User in WRKACTJOB (it would help to use a very unique user profile at that moment) to identify which job you will run STRSVRJOB against.
If you cannot connect and pause, you can just kill or hold ALL BUT ONE QZRCSRVS job and then connect. But this may not be convenient in production workload.
------------------------------
Satid S
------------------------------
Original Message:
Sent: Mon March 30, 2026 06:55 PM
From: Michael Cramer
Subject: Debug an IWS job
the job ends before I can issue a strsrvjob.
------------------------------
Michael Cramer
Original Message:
Sent: Mon March 30, 2026 04:53 PM
From: Rich Malloy
Subject: Debug an IWS job
While this may be old - wonder if it would help. Page 143 is about debugging IWS programs/jobs
Integrated Web Services Server
------------------------------
Rich Malloy
Principal Systems Engineer - IBMi
Cox Automotive
Draper UT
Original Message:
Sent: Mon March 30, 2026 01:55 PM
From: Michael Cramer
Subject: Debug an IWS job
Hi,
I normally can identify from the joblog which QZRCSRVS is handling my request and use a service job to debug but in this case none are showing this error:
I tried to change the logging level on the http server as well but I'm not getting much more information. How do I debug this?
Invocation of program failed.CEE9901: Application error. RNX9001 unmonitored by MyPGM at statement *N, instruction X'0000'.
------------------------------
Michael Cramer
------------------------------