|
Can this be done in RGP/400 , or must I do it in ILE? Carl J. Galgano EDI Consulting Services, Inc. 600 Kennesaw Avenue, Suite 400 Marietta, GA 30060 (770) 422-2995 - voice (419) 730-8212 - fax mailto:cgalgano@xxxxxxxxxxxxxxxxx http://www.ediconsulting.com AS400 EDI, Networking, E-Commerce and Communications Consulting and Implementation http://www.icecreamovernight.com Premium Ice Cream Brands shipped Overnight Visit our website to subscribe to our FREE AS/400 Timesharing Service -----Original Message----- From: Elvis Budimlic [mailto:ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx] Sent: Monday, March 22, 2004 2:42 PM To: Midrange Systems Technical Discussion Subject: RE: Record size limitation in RPG - MQ Series Your solution works up to the last part. I think you may want to call QUSPTRUS at the end to retrieve a pointer to the user space and pass that resolved pointer to the MQ API. If you were more comfortable with pointers, you could retrieve the pointer at the beginning of your program and write your entire file using that pointer (i.e. memcpy of your file data) instead of using QUSRTVUS api. Elvis -----Original Message----- Subject: RE: Record size limitation in RPG - MQ Series Once my entire file is in the user space, I then will user the Retrieve User Space API to retrieve it and then call the MQ API (QMQM) to do the MQPUT. Does this sound right? cjg _______________________________________________ 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 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.