f



Re: ERROR: CLI describe error: [IBM][CLI Driver][DB2/LINUXX8664]

On Wed, 19 Dec 2007 13:01:54 -0800, shaunak.adgaonkar@gmail.com
<shaunak.adgaonkar@GMAIL.COM> wrote:

>I am kind of stuck to this... Has anyone experienced this
>previously.... Following is my code...
>
>PROC
>SQL;
>CONNECT TO DB2(DB=DOACD011
>SCHEMA='MEMBER'
>        USER=&UID
>PASSWORD=&PWD);
> CREATE TABLE ODS_ALL_RECORDS
>AS
> SELECT * FROM CONNECTION TO
>DB2
>
>(
>
>SELECT
>
>A.SUTL_RGTR_ID
>      ,A.SUTL_RGTR_TYP_CDE
>      ,A.SUTL_RGTR_TITL_NM
>      ,A.CRCT_IND
>        ,CASE
>         A.SUTL_RGTR_STS_DT  WHEN '0001-01-01' THEN
>'1'
>       END AS RSDT
>      ,CASE
>       A.STRG_ANN_INCM_DT WHEN '0001-01-01' THEN
>'1'
>       END AS
>AIDT
>      ,CASE
>A.STRG_NET_WRTH_DT
>          WHEN '0001-01-01' THEN
>'1'
>       END AS
>NWDT
>      ,CASE
>A.INVS_OBJ_DT
>          WHEN '0001-01-01' THEN
>'1'
>       END AS
>IODT
>      ,CASE
>A.SUTL_RGTR_STRT_DT
>          WHEN '0001-01-01' THEN
>'1'
>       END AS STDT
>    FROM MEMBER.SUIT_REG A WHERE A.SUIT_REGR_STS_CDE
>in('ACTIV' ));
>RUN;
>
>
>The error i am getting is
>
>RROR: CLI describe error: [IBM][CLI Driver][DB2/LINUXX8664] SQL0206N
>"A.SUIT_REGR_STS_CDE" is not valid in the context where it is
>       used.  SQLSTATE=42703
>
>
>Any help would be appreciated
>
>Thanks

It appears to be a DB2 thing. I can run the pass-through code unchanged in
PROC SQL.

libname member 'c:\temp';

data member.suit_reg;
retain
SUTL_RGTR_ID SUTL_RGTR_TYP_CDE SUTL_RGTR_TITL_NM CRCT_IND SUTL_RGTR_STS_DT
STRG_ANN_INCM_DT STRG_NET_WRTH_DT INVS_OBJ_DT SUTL_RGTR_STRT_DT
SUIT_REGR_STS_CDE
'';
run;

proc sql;

SELECT

A.SUTL_RGTR_ID
      ,A.SUTL_RGTR_TYP_CDE
      ,A.SUTL_RGTR_TITL_NM
      ,A.CRCT_IND
        ,CASE
         A.SUTL_RGTR_STS_DT  WHEN '0001-01-01' THEN
'1'
       END AS RSDT
      ,CASE
       A.STRG_ANN_INCM_DT WHEN '0001-01-01' THEN
'1'
       END AS
AIDT
      ,CASE
A.STRG_NET_WRTH_DT
          WHEN '0001-01-01' THEN
'1'
       END AS
NWDT
      ,CASE
A.INVS_OBJ_DT
          WHEN '0001-01-01' THEN
'1'
       END AS
IODT
      ,CASE
A.SUTL_RGTR_STRT_DT
          WHEN '0001-01-01' THEN
'1'
       END AS STDT
    FROM MEMBER.SUIT_REG A WHERE A.SUIT_REGR_STS_CDE
in('ACTIV' );

quit;
0
nospam1405 (4666)
12/19/2007 9:19:43 PM
comp.soft-sys.sas 142828 articles. 3 followers. Post Follow

0 Replies
1088 Views

Similar Articles

[PageSpeed] 40

Reply:

Similar Artilces:

ERROR: CLI describe error: [IBM][CLI Driver][DB2/LINUXX8664]
I am kind of stuck to this... Has anyone experienced this previously.... Following is my code... PROC SQL; CONNECT TO DB2(DB=DOACD011 SCHEMA='MEMBER' USER=&UID PASSWORD=&PWD); CREATE TABLE ODS_ALL_RECORDS AS SELECT * FROM CONNECTION TO DB2 ( SELECT A.SUTL_RGTR_ID ,A.SUTL_RGTR_TYP_CDE ,A.SUTL_RGTR_TITL_NM ,A.CRCT_IND ,CASE A.SUTL_RGTR_STS_DT WHEN '0001-01-01' THEN '1' END AS RSDT ,CASE A.STRG_ANN_INCM_DT WHEN '0001-01-01' THEN '1' END AS AIDT ,CASE A.STRG_NET_WRT...

ERROR: CLI describe error: [IBM][CLI Driver][DB2/LINUXX8664] SQL0206N
I am kind of stuck to this... Has anyone experienced this previously.... Following is my code... PROC SQL; CONNECT TO DB2(DB=DOACD011 SCHEMA='MEMBER' USER=&UID PASSWORD=&PWD); CREATE TABLE ODS_ALL_RECORDS AS SELECT * FROM CONNECTION TO DB2 ( SELECT A.SUTL_RGTR_ID ,A.SUTL_RGTR_TYP_CDE ,A.SUTL_RGTR_TITL_NM ,A.CRCT_IND ,CASE A.SUTL_RGTR_STS_DT WHEN '0001-01-01' THEN '1' END AS RSDT ,CASE A.STRG_ANN_INCM_DT WHEN '0001-01-01' THEN '1' END AS AIDT ,CASE A.STRG_NET_WRT...

COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL30081N communication error on DB2/POrtal on AIX
Hi, I have installed WebSphere Portal on AIX and connected to DB2 on a remote machine, Getting the followin errors when trying to get the values from database thru applications installed on Portal. Any Help Appreciated. Thanks in advance. Praveen Singh IBM Workplace, India COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "9.33.12.221". Communication function detectin...

Error: [IBM][CLI Driver] CLI0125E Function sequence error. SQLSTATE=S1010 while using ADO
Hi All, Thanks for your attention..I appreciate that. -----Problem description -----------Start---------------------- Database : DB2 UDB 8.2 on Windows 2003 Client: VB6/ADO 2.7 on Windows 2003 1) I am opening a ADO 2.7 recordset with following settings SQL Source : "select * from <<sometable>>" // <<sometable>> has a PK CursorLocation : adUseClient CursorType : KeySet LockType : BatchOptimistic or Optimistic UpdateMethod : Update() or UpdateBatch() 2) After...

Re: SAS Libname CLI error
I'm going to guess environment problem of some kind, or a bad db2 client install. I would send that error to your DBA & see what s/he has to say about it. -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Shounak Adgaonkar Sent: Friday, July 10, 2009 12:02 PM To: SAS-L@LISTSERV.UGA.EDU Subject: SAS Libname CLI error While executing the sas job with a libname statement on a db2 server i get CLI error... i am running out of all the ideas...please help me out with this.... LIBNAME dashbrd DB2 Datasrc=&DB2DATABASE SCHEMA=DASHBRD USE...

Re: ERROR: CLI execute error:(SQL0206N or SQL0408N) . Neither way
Smells like your sql is getting mangled. First, try it by hardcoding your values, just to see if you can connect and execute (confirm permissions and references). If that works, then insert some print steps in your code, to see what your macro vars are resolving to. Hopefully your problem will become obvious. CH On Fri, 6 Mar 2009 12:52:08 -0800, Irin later <irinfigvam@YAHOO.COM> wrote: >I know it is Friday ...end of the day, but....I am running code through SAS environment (IN data mart implemented in DB2), trying to get unique members with at least 2 claims >on different da...

Re: ERROR: CLI execute error:(SQL0206N or SQL0408N) . Neither way #2
Your code came across with lots of extra characters in it- but hopefully that has nothing to do with the problem. The problem is that you are mixing SAS SQL code and Pass-through SQL code- and you can't do that. The value not compatible has to do with attempting to convert the integer to a date- in pass-through DB2 SQL you'd have to convert it to a date using the DB2 DATE function. But with pass-through SQL you can't select from a SAS table- only from a DB2 table, thus you need insert statements, not SAS SQL. But can you define a libname instead for the DB2 data mart? Then ...

Re: ERROR: CLI execute error:(SQL0206N or SQL0408N) . Neither way #4
I think the problem is that the column clms_cnt in your target table is defined as "smallint". The result of the COUNT function is large integer. Change your "create table" to the following and see if it works: EXECUTE( create table &tmpschema..ckd ( Id char(29) , clms_cnt integer ) in "&twotblspc" not logged initially ) by HDMconnect; -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Irin later ...

Re: ERROR: CLI execute error:(SQL0206N or SQL0408N) . Neither way #3
Were I the db2 SQL compiler .... >> EXECUTE( 3602 insert into &tmpschema..ckd 3603 select distinct 3604 Id 3605 ,Count(distinct Srv_Dt) as clms_cnt 3606 from &tmpschema..ckd_clm 3607 Group by Hedis_id 3608 having clms_cnt >= 2 3609 3610 ) by Hconnect; >> I'd check the scheme of ckd to make sure that it has only two columns, and that each matches up on data type (and possibly name) to the ID,ckd_clm header of ckd. INSERT has to know what to insert where. I'd also verif...

Re: Segmentation error: was: SAS Error Message
Short answer: this probably is not a problem with SAS. Segmentation errors usually arise when there is a bug in the program. Have you run the shell script from an interactive session to verify it works? Are you either writing the shell script, or writing a parameter file for the shell script from within your SAS session? If so, look again at the syntax of the created script or inclusion file. Usually, these errors occur where array references are out of bounds or use pointers that are corrupt or uninitialised. Modifying your shell script with a series of PrintF() statements will help y...

SAS Libname CLI error
While executing the sas job with a libname statement on a db2 server i get CLI error... i am running out of all the ideas...please help me out with this.... LIBNAME dashbrd DB2 Datasrc=&DB2DATABASE SCHEMA=DASHBRD USER=sas1 PASSWORD="&sas1passwd" ; *ERROR: CLI error trying to establish connection: [IBM][CLI Driver] SQL10007N Message "0" could not be retrieved. Reason code: "3". * Any ideas/ suggestions would be highly appreciated -- Thanks and Regards shaun Hi shaun, I think DB2 catalog is not installed in your sas server. or trying using this sy...

Re: CLI cursor fetch error
On Fri, 14 Sep 2007 09:29:50 -0700, Wade Pan <wade_pan@YAHOO.COM> wrote: > Morning, guys, > > When I remote submit a SAS program (in which I connect to DB2 tables), an error comes out for one dataset I try to create. It doesn't happen everytime, but it got me so frustrated. Please advise. Thanks, > > Wade > > ERROR: CLI cursor fetch error: [IBM][CLI Driver] A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "IP address...

error or not an error ...
I was just testing out the R4 REXX thingy, and it found an error in the following program. My question is this, is it an error or not? My PC/REXX and Regina don't barf on it, but I thought they should've. _____________________________________________ /**/ ?.='' ?.z='batman' trace i if ?.z\==''then do; say '?.z=' ?.z; end ______________________________________________ Note that there is space before the THEN. I'm not sure of the exact rules for parsing an IF statement, I know that THEN is a "reserved" keyword when an IF statement is...

Re: CI Path Errors (was Re: Errors)
bill@wcschmidt.com meant to reply to this on 04/07/2006 11:34:04 AM: During heavy loads, the keep alive timer complains and will log errors, have you logged into the HSJ's to make sure there isn't a problem there, check out the last error message code. Hoff Hoffman <hoff-remove-this@hp.com> wrote on 04/07/2006 10:29:41 AM: > Leigh wrote: > > > The VAX has whinged a couple of times over a month about device PAA0: > > and says that it has gone from GOOD to BAD once for node 6 and once for > > node 7. > > The CI is a dual-path device, so this i...

Web resources about - Re: ERROR: CLI describe error: [IBM][CLI Driver][DB2/LINUXX8664] - comp.soft-sys.sas

Resources last updated: 2/2/2016 9:42:52 PM