Debugging a CLP program within STRSRVJOB -- RPG400-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Debugging a CLP program within STRSRVJOB
From: Alan Shore <AlanShore@xxxxxxxx>
Date: Tue, 12 Feb 2008 15:20:06 -0500
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

Afternoon all
I have used STRSRVJOB along with STRDBG to debug another users interactive
session when the suspect program is an RPG ILE program.
This time (first time for me) the suspect program is a CLP, and obviously
(?) I need to use STRISDB in the following manner

STRISDB PGM(libraryname/programname) UPDPROD(*YES) INVPGM(*NO)

AFTER I enter the STRSRVJOB
However this does NOT give me an "IN" to the suspect program in question.
Can this be done?
Am I doing something wrong?

I've checked the archives and GOOGLED on STRSRVJOB, but the only things I
find is linked to STRDBG

As always, any help MUCH appreciated

Thanks in advance

Alan Shore

NBTY, Inc
(631) 244-2000 ext. 5019
AShore@xxxxxxxx
"If you're going through Hell, keep going" - Winston Churchill

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Debugging a CLP program within STRSRVJOB , Carel Teijgeler
RE: Debugging a CLP program within STRSRVJOB , Haas, Matt (CL Tech Sv)
Re: Debugging a CLP program within STRSRVJOB , Rory Hewitt
Re: Debugging a CLP program within STRSRVJOB , Simon Coulter

This mailing list archive is Copyright 1997-2026 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.