Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Categories Other
Created by Guest
Created on Sep 6, 2023

Would like to see a CEMT Command to Inquire/SET the CICS/JVM Profile

It would be nice to have the capability to issue a CEMT SET/INQUIRE on a CICS/JAVA Profile for a specific JVM.

Currently we cannot View the properties of a JVMProfile from within a CICS Address Space, we need to go to TSO and use OMVS or ISHELL to view the properties of the JVMProfile.

I would be a helpful to (1) issue a CEMT INQUIRE on the Properties of a JVMProfile from within a CICS Region, ...  (2) Dynamically Change The Profile from the CEMT Command, and then (3)  Issue a SET New verion of the JVMProfile without Stopping/starting the JVM Server and/or recycling the CICS Address Space.  The Dynamic changes would not necessarily update the DFHJVM Profile.

.

Once We know the change is good, we can use OMVS/ISHELL to permanently change the JVMPROFILE for a specific JVMServer.

.

Idea priority Medium
  • Guest
    Reply
    |
    Oct 2, 2023
    We acknowledge that once the JVMSERVER has started, it is theoretically possible to modify the JVM profile on zFS, such that the disk contents are out of synchronisation with the active environment. These types of update/change should have careful change-process around them to ensure they are controlled.

    However, one setting that might be useful is "PRINT_PROFILE=TRUE", which causes the JVMSERVER to take a snapshot of the JVM profile contents at the time it goes ENABLED and is therefore the set of properties that will apply for the life-time of the JVM (the JVMSERVERs enable/disable cycle). The output is typically written to SYSPRINT in the CICS log.


    Although a valid suggestion, this request is declined at this time for the following reasons:

    - The JVM profile is a free-form textual file and is not well suited to display in CEMT.

    - Strategic solutions for finding, viewing and modifying JVM profiles are to use zFS based tooling. For example, SSH, or FTP as very simple approaches. Dedicated sys-prog tools such as CICS Explorer provide zFS hyperlinks from the JVMSERVER resource directly to the file.

    - JVM profile changes cannot be enacted dynamically. The JVMSERVER must be restarted (disable/re-enable) to re-load changes, and values taken during start-up are considered absolute. Note: it is NOT necessary to restart the CICS region to update and refresh properties, only the specific JVMSERVER(s) needs to be re-enabled.

    - The JVM profile dictates how a JVMSERVER starts and will control major differences in behaviour (for example whether the server is Axis2, OSGi, or Liberty). Changes to the JVM profile should first be made in a test environment. The JVM is not designed to read and apply properties once in flight.