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 Future consideration
Categories Runtime
Created by Guest
Created on Jan 13, 2022

CICS record based channel containers/queues

CICS should support an alternative or enhancement to channel containers that is record based rather than byte based. These would be similar to temporary storage queues, except they would have the same visibility and lifetime rules as any other channel containers.

My thought is that the term QUEUE would be used in a similar manner as CONTAINER, but that is not a requirement as such.

The following are the specific requirements:
- This new feature (queue or whatever) would be attached to a channel in a manner similar to how containers are created and accessed (PUT, GET, DELETE, MOVE, etc.)
- Should support variable length records
- Should support full-word record lengths
- Should support full-word record numbers
- Should have the ability to append a new record to the end of the queue
- Should have the ability to rewrite/update an existing record (even if the record length is different)
- Should have the ability to specify a specific record number, or to read the next record
- Should have the ability to query on the number of existing records
- Should have the ability to query on the length of an existing record
- Should support a NODATA option
- May support code page conversion for CHAR records

Notes:
- I use the term “record” instead of “item”, but they are both really the same thing.

Idea priority Medium