× 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.


  1.  Home
  2. CODE400-L
  3. November 2001

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 Vadim,

Well, I tried to debug an interactive program with no luck.  Here's what I
did:

- Started the IBM Dist Debugger
- Closed the attach dialog
- Selected file|load program menu item
- Entered the library/program name
- Entered the parms (which happened to be numeric, so I entered them as hex
(x'0468414f' x'000f' x'004437703f' x'0000000f').
  There were 6 of them.
- Selected the "step into" checkbox.
- Click the "load" button.
- Debugger loaded, the source was displayed
- Added a breakpoint and click the "go" button

Then, the following error message displayed:
"Program received unmonitored exception RNX1216: Error message CPF4101
appeared during open for file WHSCTL"

I can't find any info on the message. I'm sure it's something stupid,
but.....well.....that's me! Thanks, Vadim!

Chris




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


Chris, this is a much simpler question!

- When you bring up the 'Attach' dialog, press 'Debugger Settings...'
button.
- 'Debugger Settings' dialog will come up and you can select 'Update
Production Files' checkbox.
- This setting will be saved for the following debug sessions on that
AS/400 host.

Hope this helps.
Vadim Berestetsky
Distributed Debugger Development
Internet:  berestet@ca.ibm.com


Chris Proctor <cproctor@gartsports.com>@midrange.com on 11/07/2001 11:21:33
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 Vadim,

Well, I stepped through your instructions and everything seemed to work
fine, EXCEPT it sat there with the "opening program" dialog for about 10
mins, with no results.  When I looked on the 400, it couldn't open the
files
because UPDPROD(*NO) was selected.  How do I change this through the
debugger to UPDPROD(*YES)? Thanks for the help!

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.
_______________________________________________
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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
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.