Re: SQL statement inside a CL

[GUY_HENZA@xxxxxxxxxxxxxx]

OK, that too.  I fixed that in my CL but forgot to change my email post.
It was the $ that needed to be proceeded by a \.  Thank you for taking the
time to reply.

Regards,

Guy

Opinions expressed are my own and do not necessarily represent the views of
my employer or anyone in their right mind.


                                                                                                                                          
                      "Joe Wells"                                                                                                         
                      <jwells@xxxxxxxxx>          To:       midrange-l@xxxxxxxxxxxx                                                       
                      Sent by:                    cc:                                                                                     
                      midrange-l-bounces@m        Subject:  Re: SQL statement inside a CL                                                 
                      idrange.com                                                                                                         
                                                                                                                                          
                                                                                                                                          
                      01/17/2008 12:21 PM                                                                                                 
                      Please respond to                                                                                                   
                      Midrange Systems                                                                                                    
                      Technical Discussion                                                                                                
                                                                                                                                          
                                                                                                                                          




Try GHENZA.FSHCNP instead of GHENZA/FSHCNP.

HTH,

Joe



> > > On 1/17/2008 at 8:47 AM, in message
<GUY_HENZA@xxxxxxxxxxxxxx> wrote:

> First, thanks.
> Second, I added the following to my CL;
>
> CLRPFM     FILE(GHENZA/FSHCNP)
> QSH        CMD('DB2 "INSERT INTO GHENZA/FSHCNP
>              (CNREP#, CNPLTS, CN$CAB, CNDESN)
>              SELECT DISTINCT
>              CNREP#, CNPLTS, CN$CAB, CNDESN
>              FROM NDSPRDFIL/FSHCNP"')
>
> and I get;
>  **** CLI ERROR *****
>          SQLSTATE: 42703
> NATIVE ERROR CODE: -206
> Column CN not in specified tables.
>
> Message . . . . :   Column CN not in specified tables.
> Cause . . . . . :   CN is not a column of table *N in *N. If the table
> is
> *N,
>   CN is not a column of any table or view that can be referenced.
> Recovery
> .
>   . . :   Do one of the following and try the request again: -- Ensure
> that
>   the column and table names are specified correctly in the statement. --
> If
>   this is a SELECT statement, ensure that all the required tables were
> named
>   in the FROM clause. -- If the column was intended to be a correlated
>   reference, qualify the column with the correct table designator.
>
>
> It works when I run it interactively...
> Does it not like the CN$CAB field name?  I tried to enclose it in double
> quotes with the same results and it won't accept single quotes.  Any
> suggestions?
>
> Regards,
>
> Guy
>
> Opinions expressed are my own and do not necessarily represent the views
> of
> my employer or anyone in their right mind.