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

I forgot to add, these are stored procedures that return the result set.

My skills are not on the client side so I cannot write something to see the
result set being returned. Would be nice if I could run something on the PC
to see the results.

The stored procedure is being called through ODBC either iAccess or a MSFT
transport medium. I do not believe its done through the JDBC. I can only
ask for that answer on Wednesday.

Darryl

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

Hi Darryl - forgot to reply to list in Thunderbird!

So far as I know, packed fields in data structures are in their packed
form - no conversion. Since they are not characters, I would not think
CCSIDs have anything to do with them.

However, a data structure __is__ basically a character variable, so maybe
there would be some conversion of the bytes in the packed subfield.

Seems we need to know what process the consuming application is using -
JDBC, ODBC, FTP, etc.

The system does not convert packed to zoned or character in data
structures, I'm very sure of this.

HTH
Vern

On 7/3/2017 7:53 AM, a4g atl 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