Date: Thu, 29 Mar 2001 20:55:24 -0000
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Paul Dorfman <paul_dorfman@HOTMAIL.COM>
Subject: Re: ERROR: Cannot connect to DB2 subsystem DB2, rc = 12,
reason code =00F30006.
Content-Type: text/plain; format=flowed
In your LIBNAME statement, you have omitted the specification for the DB2
subsystem ID (SSID=). That means that you are using the default subsystem
specified in DB2SSID= system option. It might or might not be what you want.
Moreover, many different subsystems can exist on your machine, so specifying
SSID= is almost a must. Find out from your DBA (or a fellow programmer) in
which subsystem the tables you need to access really resides. Say, you
SSID=DB2X, and you want to access tables owned by (or whose creator is) XXX;
then it would make sense to connect to DB2 like this:
libname xxx db2 ssid=db2j authid=xxx;
Having done that, you would view a DB2 table XXX.YYYY logicaly just as if it
were a SAS data file xxx.yyyy. (I find it quite helpful, BTW, to run PROC
CONTENTS against the entire 'library' - it tells a lot of useful stuff about
the tables and their columns.)
SCHEMA= you are using puzzles me. Frankly, I am not aware of the option
SCHEMA= as related to DB2. May someone on the list help me understand what
it is for.
Paul M. Dorfman
>From: "Paula M. Adkins" <PAdkins@CHECKFREE.COM>
>SAS-L LISTSERV experts: I have edited a previous job that was pulling data
>from a flat file and commented out the DD statement and have added code so
>it will get the data directly from SAS ACCESS. I'm getting this error:
>ERROR: Cannot connect to DB2 subsystem DB2, rc = 12, reason code =00F30006.
>Refer to the Call Attach Facility documentation for an explanation.
>Here's my libname statement that I used yesterday successfully: LIBNAME
>TEST DB2 SCHEMA=CKFDWHS;
>I do have other files in the JCL DD statements and they are in the program
>in another DATA step.
> DATA FINAL2 (KEEP=SOURCE
> SET TEST.SBSR_BLG_PROF;
> IF SOURCE='1234' AND SBSR_BLG_CLASS_NUM=123;
Get your FREE download of MSN Explorer at http://explorer.msn.com