×
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 am leaning towards this technique (picked up off the list a few months
back) but thought there might
be a more elegant solution or one that is easy to look at visually and
verify data keyed correctly that is, as far as the arrWhs to arrDuns
relationship.
Example using only the first 3 records for brevity -
// The warehouse & dunns arrays must be in synch for this to work
// Build warehouse array
dcl-ds *n ;
*n char( 2) inz('10') ;
*n char( 2) inz('18') ;
*n char( 2) inz('20') ;
arrWhs char( 2) dim(3) pos(1) ascend ;
end-ds ;
// Build dunns array
dcl-ds *n ;
*n char( 9) inz('006477244') ;
*n char( 9) inz('612726414') ;
*n char( 9) inz('612726414') ;
arrDuns char( 9) dim(3) pos(1) ascend ;
end-ds ;
<snip>
<old code>
d-specs:
d TABWHS s 2 dim(15) ctdata perrcd(1)
d TABDUN s 9 dim(15) alt(TABWHS)
c-specs:
c s2whs lookup TABWHS TABDUN 61 (EQ)
data:
** Warehouse/DUNS # tables
10006477244
18612726414
20612726414
25612726414
30187812631
40006198980
51006477244
54043835454
59043835454
60006477244
64926463431
75588109301
80006477244
85926463431
88545318045
</old code>
</snip>
<br />
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else is
unauthorized. If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on it, is
prohibited and may be unlawful.
midrange.com
