Re: How does a SQL result set return pack fields to the caller

Okay

here is how you return a datastructure to a stored procedure:

exec sql SET RESULT SETS ARRAY :RS FOR :row ROWS;

where:
- :RS is the multi occurrence data structure
- :row is the number of rows being returned.

Our data structure is defined for 10,000 occurrences but the program only
returns the rows populated.

The calling program will receive a blob of data that it then parses out.

Darryl.

On Mon, Jul 3, 2017 at 12:04 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

agreed


On 7/3/2017 10:03 AM, Charles Wilt wrote:

ok, yeah...that's probably what he's talking about...

A DS can be used to build a results set, but it isn't _IN_ the results
set.

So I go back to my first post...leave the DS subfields as packed/zoned.

Charles





On Mon, Jul 3, 2017 at 8:40 AM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

Charles

I wonder about your statement - data structures can be used as host
structures for SQL.. Then the data structure is not returned as such, the
subfields are handles separately, IIRC.

Someone please verify!

Vern


On 7/3/2017 9:27 AM, Charles Wilt wrote:

Wait...what? They are returning an actual data structure (as you'd

define
in RPG) in a SQL result set?

That seems like a bad idea in the first place...SQL has no support for
structures...

Charles

On Mon, Jul 3, 2017 at 6:53 AM, a4g atl <a4ginatl2@xxxxxxxxx> wrote:

I am supporting a site that uses result sets to return data to the
caller

which is usually a external system but within the enterprise network.

I see they have a mix of result sets (data structures) that have packed
fields in them. My practice has always been to define the fields in a
data
structure for a result set as character.

The developer of the calling apps could not give me a proper answer so
I
am
going to bounce the question here.

Does the system convert packed fields to zoned or character fields?

I assume it can based on the CCSIDs in use.

What is the best practice?

TIA

Darryl Freinkel
--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


--

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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD