|
James, I suspect that your variables which access storage that is defined in another program need to be defined as STAT(ic) storage variables. I am still learning the difference myself, of course; so I could be wrong. Worth a try. The first time I tried to used the PARM type of variable, I forgot that the Operand List needed to define the p o i n t e r s to my variables defined in the program, and not the variables themselves! The error message I got was different from yours though; as one would expect (not the same mistake exactly)... Rich Hart -----Original Message----- From: jamesl@hb.quik.com [mailto:jamesl@hb.quik.com] Sent: Wednesday, October 30, 2002 12:32 PM To: mi400@midrange.com Subject: [MI400] CPF24B4 in QCLRPGAS This is a multi-part message in MIME format... -- To: mi400@midrange.com From: jamesl@hb.quik.com X-Advert: http://emumail.com Reply-To: jamesl@hb.quik.com Date: Wed, 30 Oct 2002 18:31:45 AST X-Mailer: EMUmail Subject: CPF24B4 in QCLRPGAS Fellow MI geeks and gurus: I hava a program using the QCLRPGAS API repeatedly to access its own associated space. The first time it makes the call, everything works fine. The second time, though, it fails with a CPF24B4 in the error parameter. Any idea what I could be doing wrong? The parameters are all SPPs init'ed to point to AUTO variables of the appropriate type. -- JHHL _______________________________________________ This is the MI Programming on the AS400 / iSeries (MI400) mailing list To post a message email: MI400@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/mi400 or email: MI400-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/mi400.
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.