Re: Protection error in RPG/Java program and a JVM error.

On 16-Nov-2015 20:27 -0600, Darryl Freinkel wrote:

I have the following error occurring MCH6801 when running my
program.

I found a similar issue in google but it's related to WAS. I have no
idea if it's applicable to my programs.

Is there something I need to added to avoid this protection error?

For lack of context, what "this protection error" is mostly undefined; well, other than knowing of an apparent error msg MCH6801 [from which one can infer from the text "this protection error" that the Violation Type was either of VT3="read protection error" or VT4="write protection error"] and an allusion to a likeness to the following TechNote [to which there is neither a link provided, nor is there a document identifier included].

Message MCH6801 is Thrown when Attempting to Start an IBM Technology
for Java Virtual Machine Instance

Technote (troubleshooting)

Problem(Abstract)

This describes a known issue of a message MCH6801 being thrown when
attempting to create an instance of the IBM Technology for Java
Virtual Machine. It is most often seen in the WebSphere Application
Server Network Deployment (ND) environment.

Symptom

The following message is thrown when attempting to create an instance
of the IBM Technology for Java Virtual Machine in IBM i 5.4 and
later. The issue was originally reported in a WebSphere Application
Server (WAS) Network Deployment (ND) environment where the DMGR and
nodeagent application servers were configured to run as QEJBSVR user
profile. There was also a federated WAS ND profile containing two
application servers. Both application servers were configured to run
under their own user profile and not use QEJBSVR.

The above seems to be a match to the TechNote document:
[http://www.ibm.com/support/docview.wss?uid=nas8N1012715]
Title: Message MCH6801 is Thrown when Attempting to Start an IBM Technology for Java Virtual Machine Instance
Reference #: N1012715 Historical Number 537964645

See the following message where I suggest the lack of context, and how that is obtained, as well as how that issue as described possibly being associated with WAS may be more generically an issue; i.e. without any WAS involved, though still with /current profile/ involvement with access to addressed memory\storage, and thus quite possibly still applicable:
[http://archive.midrange.com/midrange-l/201509/msg00512.html]

Anyhow, the other archived message thread had the OP responding with the following as their resolution [rather than followup with the requested missing context, other context was found to be an issue; i.e. an issue with the *LIBL that was established for the failing request, and therefore the wrong HSSFR4 was being invoked] that could be sufficient information to assist in resolving this failing scenario:
[http://archive.midrange.com/midrange-l/201509/msg00520.html]