× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I guess the main reason I said "ick" was the limited space on the D-spec. I also don't like all of the quotes and colons (though, it _is_ consistent with the other keywords.)

In my mind, I was comparing it to CTDATA, where you can have the entire source record to denote the inz data, and you don't have to fool around with quotes or colons. That really makes it easy to read/understand. (Though, one thing I don't like about CTDATA is that it starts in column 1 rather than column 6.)

The solution with the "dummy" fields that are INZ() separately is nice because you use a separate line for each value, so "column cram" is a smaller issue.

I do like INZ() better than INZARRAY(), for that same reason -- less column cram.


On 4/2/2011 7:23 AM, Barbara Morris wrote:
On 4/1/2011 5:19 PM, Alan Campin wrote:

Would be nice if IBM would just give use an INZARRAY keyword.

InzArray('*PGM':'*SRVPGM':'*CMD':'*FILE')

On 4/1/2011 6:29 PM, Scott Klement wrote:

Ick.


Why ick? I don't think a new keyword is needed; INZ could do fine, just
with a new rule that allows multiple values for arrays.

It wouldn't be great for longer values, but that's true of all INZ values.

D arr s 100a dim(2)
D inz(
D 'I must go down to the +
D sea again, +
D to the lonely sea +
D and the sky,' :
D 'And all I ask is a tall +
D ship and a star +
D to steer her by,')




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.