Importing a Progress Database table definition

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
smoffa
Premium Member
Premium Member
Posts: 40
Joined: Wed Jun 30, 2004 6:00 am
Location: Orlando, FL
Contact:

Importing a Progress Database table definition

Post by smoffa »

I am trying to import a Progress table definition from DataStage Manager using the the import table definition ODBC table definitions. I have the Progress ODBC drivers installed on my DataStage server. I have also, added the necessary DSN, services, and host definitions entries. I get the following error message when I try in import:

DSR.MetaGeta(GET.TABLES)(SQLConnect('trhead','dstage')): BCI Error:
SQLSTATE=S1000,CODE=0,[DataStage][SQL Client][ODBC][INTERSOLV][ODBC PROGRESS driver]msgOpen: unable to open message file: PROMSGS

Anyone have any ideas what the problem might be?
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Does the user ID you're using have privileges sufficient to SELECT the system tables in the Progress database?
What are the permissions on the PROMSGS file?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
ketfos
Participant
Posts: 562
Joined: Mon May 03, 2004 8:58 pm
Location: san francisco
Contact:

Post by ketfos »

Hi,
It could be PROPATH problem or file permissions.
Make sure file is in PROPATH and is readable to the application under the enviornment it is run.

Ketfos
smoffa
Premium Member
Premium Member
Posts: 40
Joined: Wed Jun 30, 2004 6:00 am
Location: Orlando, FL
Contact:

Post by smoffa »

I have all the permissions that Ray and Ketfos suggested.

Someone told me last night that I needed the Progress database installed on the DataStage server. Can someone confirm this?
1stpoint
Participant
Posts: 165
Joined: Thu Nov 13, 2003 2:10 pm
Contact:

yes and no

Post by 1stpoint »

you will need to install Progress client (networking) and also the odbc driver.
smoffa
Premium Member
Premium Member
Posts: 40
Joined: Wed Jun 30, 2004 6:00 am
Location: Orlando, FL
Contact:

Post by smoffa »

Thanks 1stpoint.

I had the odbc drivers installed already. But I didn't know that I needed the Progress Client installed as well. It doesn't make sense to me.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Unless they are 'wire' drivers, ODBC typically (always?) needs the client to piggy-back over - regardless of database.
-craig

"You can never have too many knives" -- Logan Nine Fingers
smoffa
Premium Member
Premium Member
Posts: 40
Joined: Wed Jun 30, 2004 6:00 am
Location: Orlando, FL
Contact:

Post by smoffa »

I'm not familiar with the term 'wire' driver. I've been a UniVerse/Unidata programmer for 15 years and all this Database stuff is new to me. Is SQL Server a 'wire' driver? I've been importing table definitions from it for a while without installing the client.

Thanks again for your responses.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

It doesn't have anything to do with the database iteself. :wink: Wire Drivers are a type of ODBC connection that do not require client libaries. DataDirect has a nice little page here that should help explain the difference.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply