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 are rejecting this because this breaks the intent of the DEFINE ALIAS statement which is to define a data type since the INIT and VALUE attributes are not data type attributes. Also, we suspect that the most common INIT value would be zero or '' or SYSNULL (depending on the type) and specify INIT( '' ) or INIT( ''b ) on the declare would do this for almost all types
don't get the question.
so if i want an init i have to code it. if i dont' code it, it won't init.
the init should also work in "cascaded" structs:
define alias acc_nr_t dec fixed(11) init(0);
define struct 1 account_t,
2 type acc_nr_t init(value(:acc_nr_t:)),
2 amount dec fixed(13,2) init(0);
dcl my_account type account_t init(value(:account_t:));
...
//later on
my_account = value(:account_t:);
This is reasonable, but in the example
define alias size_T bin(31) fixed init(42);
dcl defaultSize type size_T init(value(:size_T:));
one could argue if the INIT on the declare should be needed - or should it just come from the type definition?