× 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. WDSCI-L
  3. March 2013

Re: RDP Debug when STRDBG active

On 05 Mar 2013 13:51, CRPence wrote:
<<SNIP>> When STRDBG is issued successfully in a job, then
implicitly the job is self-servicing, and debug is active in that
job; the job is both the servicing-job and the serviced-job. A CHGDBG
issued in that self-serviced job functions without error, acting
against the debug environment started previously in the same job.
However when <*ed:*> CHGDBG is issued within a job that is serviced
from another job, the CHGDBG fails because debug has not been started
in the self-serviced job; i.e. an externally serviced job is not
allowed to perform any debug activity on itself. This means that
STRDBG also fails, but instead of due to mode-checking by the command
analyzer, due to the debugger detecting that the job is being
serviced by another job.

The prior reply I had typed CHGJOB vs the intended CL command CHGDBG. The correction is inline in the quoted text above, after the <*ed:*>


As an Amazon Associate we earn from qualifying purchases.

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