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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
We received an email from you on June 18th which said: Thanks for letting me know. I had not read the comment. I will try it as soon as I have time. If this works it will be great.
Having not heard back any more, this RFE is being closed.
Regarding "All of this files should be automatically deployed to the Liberty Unix filesystem on activation of a CICS bundle." - these configuration files can be placed into the CICS bundle root or sub directory. The configuration files can be referenced in the JVM profile by use of the &CONFIGROOT; symbol, or Liberty server.xml or within the application itself using the value of the com.ibm.cics.jvmserver.configroot system property - see topic Referencing zFS artifacts in a bundle.
Java developers could also place the configuration files within the relevant Java project/packaging and thus will be deployed with that project. For example for OSGi bundles, if you include the resource file in the bundle at the top-level and add an entry into the build.properties of the project it is exported to the file-system with the OSGi bundle. Then use the standard, InputStream inputStream = getClass().getResourceAsStream("/resource.file"); to get it in source.