loading df file in progress using cmd prompt(load_df.p)

[sudipta]

Hi All,

I am new to this community.

I am trying to load df file wiithout using GUI.

I did the following steps.

1) Run the command extractpl prodict.pl
2) Run the command extractpl adecomm.pl
3) It created the prodict and adecomm folder.
4. My db name is remdb.I made changes in load_df file, but not able to run the load_df.p. It's throwing the below error.

1. Not able to find the environment variable.
2. _db is not found.
3. _File is not found.

Can any one help me

 

[TomBascom]

The messages that you are getting are indicating that you are not connected to the database that you want to load the df file into. So either CONNECT in your program or specify a db on your command line.

 

[sudipta]

Thanks Tom.

I have added the following code in the file load_df.p:

DEFINE BUFFER file1 FOR remdb._File.
DEFINE BUFFER field1 FOR remdb._Field.

The above error got corrected

A new error is encountered now. It is as follows:

** "prodict/dump/_lodv5df.p" was not found. (293)


I am breifing the steps performed below:

1) proenv
2) Run the command extractpl prodict.pl
3) Run the command extractpl adecomm.pl
4) It created the prodict and adecomm folder.
5) Executed the following command:

C:\PROGRA~1\PROGRESS\bin>proserve -db C:\Rem\db\remdb.db -S 5559

5) Executed the below command.

C:\PROGRA~1\PROGRESS\src\prodict>mpro -db C:\Rem\db\remdb.db -b -p load_df.drv>load_df.txt

6) The load_df.drv is as follows:
RUN "C:\Program Files\PROGRESS\src\prodict\load_df.p" (INPUT "C:\Rem\db\Pos_df.df")

( The Pos_df.df file is created using Data Administrator Tool )

We are using Progress9.1D database in Windows XP enviroment.

The load_df.txt contained below error message:
** "prodict/dump/_lodv5df.p" was not found. (293)

Can any one help me...

 

[TomBascom]

Don't extract and modify load_df.p that's just asking for trouble. Instead write a simple program to call it:

/* loaddf.p */

run prodict/load_df ( input session:parameter ).

return.

Then just use something like this from your proenv command prompt:

mpro dbname -p loaddf.p -param file.df

 

[sudipta]

We are using Progress 9.1D on Windows XP environment.

The paths included in the load_df contains forward slash ( as for Linux / Unix environment).

Shall we modify that path... Else below error message are encountered..

** "prodict/user/uservar.i" was not found. (293)
** C:\Program Files\PROGRESS\src\prodict\load_df.p Could not understand line 59. (193)
** "prodict/dictvar.i" was not found. (293)
** C:\Program Files\PROGRESS\src\prodict\load_df.p Could not understand line 60. (193)

Please suggest

 

[TomBascom]

Do as a I suggest.

Do not attempt to modify load_df.p. Instead call it from a simple wrapper.

Forward slashes are not a problem. Progress understands them. There is no need to change them.

 

[sudipta]

Thanks tom,

I have tested it successfully in uat,

My test scenario is below.

1. Created one table
2. Dump the table
3. Drop the table
4. Import the table using mpro.

It's imported.

I will test the same in my live env with the live db.

I will take your help if any error found.

Thanks

 

[sudipta]

Hi Tom,

While running mpro for 1 st time I am getting below error

C:\Program Files\PROGRESS\src>mpro -db C:\Rem\db\pos.db -p loaddf.p>load_df.txt

Error: Files\PROGRESS\bin\icu\data\\""=="" was unexpected at this time.

Second time if I run the same mpro command error is not coming.

Can u help me...

Also please help us how to describe a table structure using command prompt.

 

[TomBascom]

1) I have no idea what the "==" error is about. Are there other parts to the error message? Did you manually modify the .df file?

2) Are you asking how to dump a .df file for a table from the command line?

 

[Casper]

could it be that Progress doesn't like spaces in the directory path?
(Progress seems to be installed under "Program Files" )

Casper.

 

[comatt1]

could it be that Progress doesn't like spaces in the directory path?
(Progress seems to be installed under "Program Files" )

Casper.

I agree, I think that the space would be the issue.

I would stick with "Progra~1"

However, if you have the proenv and %DLC% variable set, I don't see the need for the full path to mpro. Also, aren't you attempting to run this as a batch?

If you are running in a batch mode passing parameters you will need the
"-b" argument at the end, or use mbpro.