Method 1:
If the program is an OPM program, you can use STRISDB to simultaneously
service and debug the interactive job that is looping from another
workstation.
Example: STRISDB PGM(P4211) INVPGM(*NO) SRVJOB(*SELECT)
This will show you a list of jobs running on the system. Page down until
you find the job you want to service, then place a '1' in the option field
to select it for servicing/debugging. At this point, set a break point.
When the program reaches the break point, you will get the ISDB/400 display,
and can then step thru the code.
Method 2:
If the program is an ILE OR an OPM program,
1) STRSRVJOB JOB(jobnbr/Userid/Jobname)
2) STRDBG PGM(P4211) UPDPROD(*YES)
3) Set a break point
4) Step thru the code
HTH
Steve Landess
Austin, Texas
(512) 423-0935
----- Original Message -----
From: "chemker" <
[email protected]>
To: <
[email protected]>
Sent: Thursday, April 24, 2003 3:00 PM
Subject: Loop
program message to answer? We are having problems with the creating of
credit orders from history looping but cannot duplicate the problem to
debug. It would help if we could get a dump of the program, rather than
just ending the job.Thank you.
Steve Landess
V4R4 A7.3 cume9
EDI
(512) 423-0935