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



The problem is that when I did the //083210 the job never appeared when I
clicked the Job List button.  Nor did it appear when I used /QNOTES/.  The
danged thing would not appear until the job was released.  How do I work
around that?

Rob Berendt

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



                    berestet@ca.ibm.co
                    m                        To:     code400-l@midrange.com
                    Sent by:                 cc:
                    code400-l-admin@mi       Fax to:
                    drange.com               Subject:     Re: Debugging a batch 
job


                    11/06/2001 05:13
                    PM
                    Please respond to
                    code400-l






Hi Rob,

Here is what I would try:
   In the 'Job to debug' field enter  //083210  and click 'Job List...'
   button
   You should be able to find your job in the list that comes up
   Alternatively, you could enter  /QNOTES/  and click 'Job List...'

If the list comes up empty, type WRKSBMJOB to see the status of your
submitted job.

Let me know what happens.
Vadim Berestetsky
Distributed Debugger Development
Internet:  berestet@ca.ibm.com


rob@dekko.com@midrange.com on 11/06/2001 04:55:46 PM

Please respond to code400-l@midrange.com

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


To:   code400-l@midrange.com
cc:
Subject:  Debugging a batch job



I am trying to debug a batch job.  I am following some instructions I have
which say to:
-SBMJOB CMD(....) HOLD(*YES)
-Start debugger with prompt.
-Get job info of submitted job
-Start debug session
-Release job
-Bring up your source from the Programs page
-Set line breakpoints.  Watches are not available while browsing.
-Run
-Start your program on the 400 when message tells you to.
-Dismiss message.

So I
-did the SBMJOB.
-Start, Programs, IBM Web Sphere Development Tools for iSeries, IBM
Distributed Debugger, IBM Distributed Debugger.
-made sure my host name was correct
-Turned off Step Into
-Specified the name of the program to add to debug
-Try to select the job to debug.  This is where I can't find the job.  This
is the job I am trying to debug:
Job            User           Number     Priority     Status
DOMSYN1000     QNOTES         083210        5          HLD
I tried DOMSYN1000/QNOTES/083210, */QNOTES/*, and whatever - no luck.

Any clues?

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.







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.