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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Transaction Processing
Product - CICS Transaction Server
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Transaction Processing
Product - CICS Transaction Server
On September 4th 2013, more details on the usecase was requested. This was followed up by an email on October 4th. No information has been received as of January 5th 2014, so this RFE is being closed.
The file referenced by the DOCTEMPLATE resource is loaded and cached by CICS on first use and reused by subsequent tasks. The cache can be refreshed with command SET DOCTEMPLATE() NEWCOPY. For high volume applications avoiding I/O will improve response times.
The DOCUMENT CREATE and DOCUMENT INSERT commands can be used to create a document from several templates or text fragments from the application with automatic symbol substitutions. This in theory should help avoid the application from having to load the contents of the file into its task storage, parse the contents, worry about codepage conversion, and do lots of string manipulation to add content dynamically. Once all the pieces are inserted, DOCUMENT RETRIEVE can then be used to get a copy if it is required by the client.
Saying that, CICS does not prevent applications using files via the languages native APIs - so for example a Java application can use the java.io.FileInputStream. However as this access will not be managed by CICS, eg. updates will not be part of the CICS transaction scope, and CICS will not manage serialisation, and the I/O will occur for each task.
Please can you give more details on the use case.