RE: Debugging a batch job -- CODE400-L

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Thank you for the "step-by-step" instructions, Vadim. I'm pretty new to the
debugger (I've only called it from codeedit) so far, but I'm going to give
it try. Believe me, I'll let you know if I have problems! ;)

Thanks!

Chris

-----Original Message-----
From: berestet@ca.ibm.com [mailto:berestet@ca.ibm.com]
Sent: Wednesday, November 07, 2001 8:45 AM
To: code400-l@midrange.com
Subject: RE: Debugging a batch job


Rob, Chris,

There should be no mystery with debugging batch jobs using the Distributed
Debugger.
If you have the latest release of WDT/400 here is a list of steps
(relatively simple steps, I hope) to follow:
-SBMJOB CMD(....) HOLD(*YES)
-You should get back the job info of the submitted job. (Alternatively, use
WRKSBMJOB command)
-Bring up the Distributed Debugger. Make sure 'Attach' dialog is up.
-In the 'Job to debug' field enter //JobNumber (e.g. //123456) and press
'Job List...' button
-Select your job from the list that comes up
-Specify fully qualified name of the program you would like to debug
-Select 'Step Into'
-Press 'Attach' button
-In a few seconds you should see the source and continue with the debug
session.
NOTE: debugger will release held job automatically.

As you could see, the key step is to find out the name of the submitted job
correctly.


Rob,
It seems like you follow these steps correctly. I wonder if you could send
me your phone # so we could chat about this.
My e-mail address is at the bottom of this note.

Thanks,
Vadim Berestetsky
Distributed Debugger Development
Internet:  berestet@ca.ibm.com


Chris Proctor <cproctor@gartsports.com>@midrange.com on 11/07/2001 10:13:17
AM

Please respond to code400-l@midrange.com

Sent by:  code400-l-admin@midrange.com


To:   "'code400-l@midrange.com'" <code400-l@midrange.com>
cc:
Subject:  RE: Debugging a batch job


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Hi Rob,

Would you do me a favor?..... I've been watching your emails about batch
debug yesterday and I would very much like to know how it works (if you
ever
actually get it to work! :)  ) Would you please post an email with the
steps
you performed to do it? I need this functionality pretty frequently, but
I've never actually been able to do it!! I would be greatly appreciative!

Thanks

Chris Proctor
Gart Sports
Denver

-----Original Message-----
From: rob@dekko.com [mailto:rob@dekko.com]
Sent: Wednesday, November 07, 2001 6:46 AM
To: code400-l@midrange.com
Subject: Re: Debugging a batch job



When I try to do the traditional STRSRVJOB/STRDBG on this job it brings up
the source but when I try to set a breakpoint I get:
Message ID . . . . . . :   CPF1938
Date sent  . . . . . . :   11/07/01      Time sent  . . . . . . :
08:43:10
Message . . . . :   Command is not allowed while serviced job is not
active.
Cause . . . . . :   You tried to enter a debug command to a serviced job,
but
  that job is not active.  The job was not active for one of the following
  reasons:
    -- The job was held on the job queue because the Hold Job (HLDJOB)
command
  or the Hold Job Queue (HLDJOBQ) command was used.
    -- The job was held after it started running because the Hold Job
(HLDJOB)
  command was used.
    -- The job stopped processing temporarily because the Transfer
Secondary
  Job (TFRSECJOB) command or the Transfer Group Job (TFRGRPJOB) command was
  used.
Recovery  . . . :   Do one of the following and try the request again:
    -- If The job was held on the job queue, use the Release Job (RLSJOB)
  command to release the job or use the Release Job Queue (RLSJOBQ) command
to
  release the job queue.
    -- If the job was held after it started running, use the Release Job
  (RLSJOB) command to release the job.
    -- If the job stopped processing temporarily because the Transfer
  Secondary Job (TFRSECJOB) command or the Transfer Group Job (TFRGRPJOB)
  command was used, transfer back to the alternative job using the System
  Request menu or transfer back to the group job using the Transfer Group
Job
  (TFRGRPJOB) command.
Technical description . . . . . . . . :   In order for the debug command to
  complete, data must be processed by the serviced job.  However, the job
is
  not active, so the job cannot run to process the data.


Rob Berendt

==================
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin

_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.




_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.