Sources for External Data Structures

Date:   6/26/97  6:50 PM

RE:     Sources for External Data Structures

Hans

I am sooooo happy for the two(or is it three) people in the world that have
a dire need for variable length/graphic fields in their programs.
    (Maybe the same two that desperatly needed RPG/370)
As compared to the hundred's of thousands of programmers who have a need
(like yesterday) for not HARD CODING IN EACH PROGRAM WE WRITE initial
values for subfields when the data base ALREADY KNOWS what I want.
(Who the heck took it out, Wait till CUDS at COMMON!!)

As you know,  When we write a maintenance program against a file(maybe
from a package) that has 50 - 500 fields each with their own default
value,  It would be nice to have an externally defined data structure
which we could just say RESET and have the DFT values be initialized
correctly for the next record add.  Without hard coding those values
in each program.  Of course you have heard this many times. sorry.

The other things are great, and needed,  Don't we aready have INDDS by 
using INDARA in the DDS?

>John Carr CDP wrote:
>> Personally
>> Before we get *PRTF's implemented in RPG, I would rather see (for 10 years
>> now)  getting my externally defined data structures Initialized from the
>> values from the DDS  DFT (Default value)of each field implemented!!!!
>>
>> TORONTO are you listening?  IBM has been talking of pushing the business
>> definitions out of the language and into the data base where they belong
>> (Triggers, RI, ETC) However they have forced us to HARD CODE initial values
>> for variables(data base entities) in our programs.

Hans wrote
>Hi John!  I was hoping to say that you'll be getting this one.
>Unfortunately, while I was away on vacation, it was pulled from our
>development plan.   :-(
>
>Anyways, that's what's not in plan.  Here's what we are still working
>on for the next release of ILE RPG IV:

>- New D-Spec keyword VARYING to define varying length character and
>  graphic fields.  Of course, this means we also recognize varying
>  length fields defined in externally described files.
>- Indicator data type (type N)
>- New built-in functions:
>  -- %REPLACE for string manipulation
>  -- %CHAR to convert date/time/timestamp/graphic types to character
>  -- %STATUS
>  -- %ERROR
>  -- %EOF
>  -- %FOUND
>  -- %OPEN
>- New opcode extender (E) to eliminate need for error indicator (used
>  with new bif %ERROR)
>- New H-Spec keywords to specify compiler options in the RPG source
>  (rather than on the CRT command)
>- additional date formats used with MOVE opcode
>- Keywords IMPORT and EXPORT can take parameters to specify a mixed-case
>  external name.
>- New F-spec keyword INDDS to specify a 99 byte data structure which
>  holds conditioning and response indicators for the file.  So each
>  display and printer file can have its own separate indicator area.

>Of course, the usual disclaimers apply:  Since we have not formally
>announced anything, none of this can be considered a formal
>commitment; plans may change; etc.
>
>I know this can't make up for the disappointment of not getting the
>EDS DFT initialization, but I hope you will still like what we do
>deliver in this release.

>Cheers!  Hans

>Hans Boldt, ILE RPG Development, IBM Toronto Lab, hboldt@vnet.ibm.com

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *