Re: View to create a PF?

CHAR (6) is fine.
How do you code numeric like CAST(IRQOH# AS NUMERIC(13.2)


On Fri, Aug 23, 2013 at 11:23 AM, Hoteltravelfundotcom <
hoteltravelfun@xxxxxxxxx> wrote:

Buck, we did the translate on the server but it didn't help. On the job
would be on the SQL options I have tried that as well. I can't change the
CCSID on the LF only on a PF> I wil try ROb's idea CCSID 37 this is not so
bad if it works.


On Fri, Aug 23, 2013 at 11:16 AM, <rob@xxxxxxxxx> wrote:

Resending, cutting off the trailing stuff with the word "shiRt" in it...
censors, please forgive me.






From: rob@xxxxxxxxx
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 08/23/2013 11:10 AM
Subject: Re: View to create a PF?
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Expanding further...
and assuming all columns are character...

CREATE VIEW astccdta.acbalmpk AS (
(SELECT LMLTPC, COALESCE(IRLOC1,'') as IRLOC1, COALESCE(IRLOC2,'')
as IRLOC2, COALESCE(IRLOC3,'') as IRLOC3, IRPRT#, IRQOH#, IRWHS#,
'' as IEPRT#, '.00' as IEQOH#, '' as IELOC1, '' as IELOC2, '' as
IELOC3, '' as IERIDC, '' as IEWHS#

becomes

CREATE VIEW astccdta.acbalmpk AS (
(SELECT
CAST(LMLTPC AS CHAR(??) CCSID 37) AS LMLTPC,
CAST(COALESCE(IRLOC1,'') AS CHAR(??) CCSID 37) as IRLOC1,
CAST(COALESCE(IRLOC2,'') AS CHAR(??) CCSID 37) AS IRLOC2,
...

after awhile you quickly learn that fixing your underlying CCSID's is
probably a great idea.

Hopefully this view is for developer use only. Otherwise, why would
someone go to such trouble to create a view and still use obfuscated
column names?


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