× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Yes.

When you set a SEP, you place it on a program/service program and a user
ID. Job name isn't used.

The next time that user ID runs the program, it comes up in debug.

https://www.ibm.com/support/knowledgecenter/SSAE4W_9.5.0/com.ibm.etools.iseries.debug.doc/topics/cbibsent.html?cp=SSAE4W_9.5.0%2F6-2-4-2



Charles

On Mon, Mar 28, 2016 at 11:26 AM, Michael Ryan <michaelrtr@xxxxxxxxx> wrote:

Even if I don't know the job name?

On Mon, Mar 28, 2016 at 11:22 AM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

​Use the debug Service Entry Points (SEP) from RDi.​..

You can also use SEPs from the green screen, but it's a little more
difficult and I've never done it that way.

Charles

On Mon, Mar 28, 2016 at 9:52 AM, Michael Ryan <michaelrtr@xxxxxxxxx>
wrote:

I need to occasionally debug the PHP script->i program interaction,
especially when I need to see parameters being passed or to trace logic
flow. When I run in stateful more, I'm able to use STRSRVJOB on the
Toolkit
job, and then STRDBG on the program or service program. However, when I
use
stateless mode, the job uses a QSQSRVR job and I don't know which one
will
be used.

I was thinking I could have the PHP script send a SNDMSG command with
an
*INQ so I could identify the QSQSRVR job being used. This works, but
the
PHP script doesn't 'pause' and wait for the response. So then I
thought I
could use SNDPGMMSG, specify a key variable, then use RCVMSG for an
*INQ
type with that MSGKEY.

Anyone have any hints for this type of debugging interaction? Cross
posted
to midrange and web since it has a MSG question as we as a PHP
technique.
Thanks!
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.