|
Doug, >>I don't really expect a PTF. >>All along the rules have been operational descriptors are only available for character fields. >>Last I knew, this wasn't something Toronoto had any control over. Is your thinking that a data structure is fundementally different (on a procedure call) from a character variable? Does anybody have a V5R1 machine on which they can test a parm that is defined with LIKEDS() and see if the opdesc thing works? Bob -----Original Message----- From: rpg400-l-bounces@midrange.com [mailto:rpg400-l-bounces@midrange.com] On Behalf Of Douglas Handy Sent: Sunday, January 12, 2003 3:14 PM To: RPG programming on the AS400 / iSeries Subject: Re: CEEDOD problem -- more info Bob, >I've narrowed down the issue with CEEDOD failing. It occurs whenever >the value that is specified for a procedure is a data structure. I've >written a short example program that reproduces the problem everytime. >Here's the code, and thanks to those who repsonded, now we just need a >PTF!. I was surprised by your earlier post, because I have used OPDESC for lots of my service program routines for years and never had the error. But this explains it, because I always pass character variables to them -- not DS names. I don't really expect a PTF. All along the rules have been operational descriptors are only available for character fields. Last I knew, this wasn't something Toronoto had any control over. Doug _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo.cgi/rpg400-l or email: RPG400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.