Better management of IMS PGM name to Java class name mappings

For IMS Java programms (both Java batch and Java message processing programs) a mapping between IMS program names and Java class names must be provided in IMS PROCLIB member DFSJVMAP. Such a mapping within this member looks like this:

IMSJAVPG=com/ibm/ims/java/sample/MyApplication

You always have to edit the PROCLIB member, if you want to define a new Java program to IMS or if the Java class name respectively the package of the class has been changed. This is not a good way to define this, because typically an application developer would not be permitted to edit something in IMS PROCLIB.

A better way to handle this would be to store this mapping information directly with the program definition ...in a RDDS or in IMS repository - of course APPLCTN macro makes not much sense (therefor also an IMS system programmer or administrator has to do the definition). In the case the mapping information is stored with the program definition, it could be manipulated by IMS type 2 commands. An application developer could be permitted to execute these commands. No IMS PROCLIB member has to be edited, IMS system programmers or administrators would not have to do the mapping definition and mapping definitions would be more flexible.

Having also a possibility to define this mapping in IMS Explorer would be the best for a Java application developer. In this case he would not need to have knowledge about IMS PROCLIB or SPOC and IMS type 2 commands. IMS Explorer could use IMS Enterprise Suite in background to generate IMS type 2 commands that are sent to IMS through IMS Connect to manipulate the mapping in the IMS program definition.

The way to solve the problem I am proposing here might not be the only ways and maybe also not the best way. We are open to discuss other solutions for this problem.