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



On 06-Jun-2011 08:24 , Tom Hightower wrote:

One of our power-users was logged in this morning doing some
new-machine testing for me. Checking thru her joblog I saw the
following:

(10:08:40) CPC3202 Member BLDTABLER renamed to member BLDTABLERZ.
(10:08:45) MCH6801 Object domain or storage protection error for
offset in object QDBCMPOP.

Message ID . . . . . . : MCH6801 <ed: reformatted>
"Object domain or storage protection error for offset in object
QDBCMPOP." Cause . . . . . : A program tried to use a blocked
instruction, access a system domain object, or make invalid use of a
protected page. The violation type is 1. The violation type indicates
the type of error: 1-Object domain violation.

She never did see that message, but it is in her joblog. As far as I
can tell, she was just renaming a member in the file (via PDM). Is
there something I need to reload/fix?


Though not all of the relevant context of the error message was included [e.g. f/pgm and t/pgm were not], and that may have better clarified [if only to compare to another failing scenario for a known origin], the msgMCH6801 error in that case is very likely suggesting effectively, the need to issue DSPCMD against the failing command. The DSPCMD output presumably will show that the "State used to call program" for the "Prompt override program" is the value *USER instead of the value *SYSTEM. That POP is used for CHGPFM [Change Physical File Member] for which the prompted option-13="Change text" in WRKMBRPDM effects ?CHGPF for which the prompt override program will be invoked for the key values FILE(&L/&F) MBR(&N) to fill-in the existing parameter values [to be extracted according to those keys].

That loss of the system state is almost always a side-effect of CHGCMD of the failing command.

Note: there is an option in PDM to turn on command logging, so the error would be preceded by the request message which experienced the error.

Regards, Chuck

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.