|
You have told me the how but I want to know the why. Marvin -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Tyler, Matt Sent: Friday, July 22, 2005 2:06 PM To: 'RPG programming on the AS400 / iSeries' Subject: RE: another SQL precompiler issue - mods for recieving fetches If you are talking about INDARA, it's really easy. 1. In the DDS key INDARA at file level. 2. In your RPG, on the file definition put the keyword INDDS(ind_ds); where ind_ds is a data structure you define with indicator type subfields. You cannot put *IN*/*IN() indicators here, but you can map to *IN() easily enough. There is a lot of examples given in this forum, just search for INDDS and/or INDARA. http://archive.midrange.com/cgi-bin/htsearch Thank you, Matt Tyler WinCo Foods, LLC mattt@xxxxxxxxxxxxxx -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Marvin Radding Sent: Friday, July 22, 2005 2:56 PM To: RPG programming on the AS400 / iSeries Subject: RE: another SQL precompiler issue - mods for recieving fetches -----Original Message----- From: rpg400-l-bounces+mradding=dpi-west.com@xxxxxxxxxxxx [mailto:rpg400-l-bounces+mradding=dpi-west.com@xxxxxxxxxxxx] On Behalf Of Tyler, Matt Sent: Friday, July 22, 2005 1:43 PM To: 'RPG programming on the AS400 / iSeries' Subject: RE: another SQL precompiler issue - mods for recieving fetches Have you thought about using the INDARA option? It removes the indicators from the normal data buffer. Thank you, Matt Tyler WinCo Foods, LLC mattt@xxxxxxxxxxxxxx [Marvin Radding:] On this subject, can you tell me the criteria that determines which to use? I am unclear on how and when to use this feature. Thanks, Marvin
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.