× 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.



Tim,

I would use a user space or maybe a user index if you wanted the summary at 
page end to be sorted.  

User spaces are conceptually just really big data areas.  There are as group of 
API's that handle creation, writing, and reading information to and from them.  
They can also be access using a pointer it that is allowed in your shop.  You 
would define a layout (probably using a data structure) that would contain the 
fee description and an amount field.  This structure would be repeated for the 
number of different fees found on the PO.  To print the fees at the bottom 
simply read through the list built as the PO was read and print each item.  
This link should take you to the user space API documentation. 
http://publib.boulder.ibm.com/iseries/v5r2/ic2924/index.htm

User indexes function very much the same except that you identify a specific 
number of bytes at the beginning of each entry to be the key.  In your case 
this would be the fee type.  Add entries to the index as the line items are 
read.  Read through the entries at the end of each PO and print the fee types.  
This link should take you to the user index API documentation.  
http://publib.boulder.ibm.com/iseries/v5r2/ic2924/index.htm

There is also quite a bit of information in the archives on using user spaces 
and indexes in similar situations.

Rick

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Hatzenbeler, Tim
> Sent: Tuesday, March 09, 2004 1:56 PM
> To: 'Midrange Systems Technical Discussion'
> Subject: is there a better way...
> 
> 
> 
> I'm reading a PO, and there are various charges through each line of
> detail... And I was asked to group the charges at the bottom 
> of the page...
> 
> line 1 
>      tax 8.96
>      frt 12.45
>      delivery 45.67
> line 2 
>      tax 9.12
> line3
>      frt 9.23
> 
> 
> and at the bottom of the page, i need
>      tax xx.xx
>      frt xx.xx
>      delivery xx.xx
> 
> so I was was thinking about using a mods to do this... With a 
> simple add,
> find, update procedure...  But I was wondering, if there were 
> better arrary
> handling features in the latest  versions of rpg, to handle this...
> d chargegroup     ds                  occurs(999) inz        
> d  chargedesc                   30                           
> d  chargetotal                  17  2                        
> 
> but, i'm not allowed to use embedded sql grouping / sum 
> features... It has
> to be all old fashioned rpg code...
> 
> I can't hard code these charge types, they can change anytime 
> accounting
> feels like it...
> 
> Thanks, tim
> 
> This e-mail message, including any attachments, is for the 
> sole use of the
> intended recipient(s) and may contain confidential or privileged
> information.  Any unauthorized review, use, disclosure or 
> distribution is
> prohibited.  If you are not the intended recipient, please contact the
> sender by reply e-mail and destroy the message.
> _______________________________________________
> This is the Midrange Systems Technical Discussion 
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
> 


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.