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
Workspace zSecure
Categories zSecure Audit
Created by Guest
Created on Mar 27, 2024

zSecure - Allow function e.g. SUM for User-Defined Variables

zSecure gives us the ability to define our own file structures using e.g. DEVTYPE TYPE=$txt, but then doesn't allow us to use any of the fields we define in DEFINE statements, such as in SUM(xxx). It's a case of, "giving with one hand and taking away with the other". We'd like zSecure to handle this.

Example -

 1 !  deftype type=$txt                                        
2 !  define type=$txt date as word(record,01)                 
3 !  define type=$txt time as word(record,02)                 
4 !  define type=$txt type as word(record,03)                 
5 !  define type=$txt syst as word(record,04)                 
6 !  define type=$txt jobn as word(record,05)                 
7 !  define type=$txt user as word(record,06)                 
8 !  define type=$txt data as word(record,07)                 
9 !  define type=$txt ctrl as word(record,08)                 
10 !  define type=$txt bi   as word(record,09)                 
11 !  define type=$txt bo   as word(record,10)                 
12 !                                                           
13 !  alloc type=$txt dd=file                                  
14 !  option emptylist=hide required pl=0                      
15 !  suppress racf                                            
16 !  suppress ckfreeze                                        
17 !                                                           
18 !  newlist type=$txt detail title="Sum" nodup               
19 !                                                           
20 !  define type=$txt tot_in('Total bytes_in',15)   sum(bi)   
21 !  define type=$txt tot_out('Total bytes_out',15) sum(bo)   
22 !                                                           
23 !  select data=unprotected                                  
24 !                                                           
25 !  summary tot_in tot_out                                                                         

Errors -

CKR0425 12 Field "BI" to be processed not valid for NEWLIST TYPE=<deftype> at SYSIN line 20  
CKR0425 12 Field "BO" to be processed not valid for NEWLIST TYPE=<deftype> at SYSIN line 21  
CKR0425 12 Field "BO" to be processed not valid for NEWLIST TYPE=<deftype> at SYSIN line 25  
CKR0425 12 Field "BI" to be processed not valid for NEWLIST TYPE=<deftype> at SYSIN line 25  

Idea priority Medium
  • Guest
    Apr 23, 2024

    For now we will interpret this idea as adding support for a CONVERT on a DEFINE of a deftype.

  • Guest
    Apr 12, 2024

    The sample CARLa has one or two wrong assumptions. It confuses character fields with binary fields. In other words, if the word with some number in the input file is in EBCDIC characters, it needs a CONVERT to DECIMAL before you perform a SUM statistic on it and expect the numbers to add sensibly. If the word in the file is already in binary form, the DEFINE must specify a format on the field definition that implies such, rather than inherit a default format from RECORD. Which of the two cases applies here?