|
I guess I would ask my normal question. Why would you need to pass a parameter that big? It sounds like you are returning some form of an array. Assuming that is true, couldn't you just define a procedure to build a list and store it and then a procedure to get a count and finally a procedure to retrieve each record from a list in a loop. If you are wanting to the opposite, you could define a function to create a list or a function to add items to internal list. Hard to imagine having a single record bigger than 64k. Maybe you could a better idea of what you are trying to do. -----Original Message----- From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx] Sent: Thursday, February 24, 2005 6:26 AM To: rpg400-l@xxxxxxxxxxxx Subject: Redbook on iSeries limits Isn't a redbook or some other reference on iSeries limitations? What is the maximum length of a parameter to a subprocedure? Is using a data structure as a parameter a valid workaround? I know this is somewhere but I can't seem to find it. Additional search words (for the archives): limitations, limits, maximum, maximums, iseries, as/400, as400, i5, os/400, os400, i5os, i5/os, redbook, redpiece, web, site, website, url, link, document, publication, IBM, list, reference, guide, guidebook, book Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com
As an Amazon Associate we earn from qualifying purchases.
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.