Hello,
------------------------------ OpenEdge Release 10.2B08 CentOS release 6.5 (Final) uname -a Linux fin-uni 2.6.32-431.29.2.el6.x86_64 #1 SMP Tue Sep 9 21:36:05 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ------------------------------
I encountered with a strange behavior of the prolib utility.
When I try to get the contents of the library:
prolib prolib-test.pl -list
I get some warnings:
Code page conversion table for IBM866 to ISO8859-1 was not found in convmap.cp. (6063)
You are using -cpinternal iso8859-1 and the code page of the library prolib-test.pl is ibm866. (4307)
The table to convert iso8859-1 to ibm866 was not found in convmap.cp. (4308)
The library contents may not be displayed correctly. (4310)
This library was created with the following command:
prolib prolib-test.pl –create –add _*.r -cpcase Basic –cpcoll Russian -cpinternal ibm866 -cpstream ibm866 -verbose
At the same time, code page in startup.pf defined correctly :
$DLC/startup.pf -cpinternal ibm866 -cpstream ibm866 -cpcoll Russian -cpcase Basic -d dmy -numsep 44 -numdec 46
I see that the utility prolib not use the parameters defined in the $DLC/startup.pf?
Is this normal?
I tried to find information about this in the documentation or in the knowledge base, but could not find anything.
Regards,
Valeriy
prolib doesn't read startup.pf or any .pf files. It has its own code to handle startup parameters and doesn't recognize the complete set of client parameters.
prolib *does* read .pf file:
proenv>prolib p-test.pl -create -add *.r
proenv>prolib p-test.pl -list
Listing of library 'p-test.pl'
Library code page is iso8859-1. (4309)
--> note iso8859-1
proenv> del p-test.pl
proenv>prolib p-test.pl -create -add *.r -pf prolib.pf
proenv>prolib p-test.pl -list
Code page conversion table for IBM866 to ISO8859-1 was not found in convmap.cp.(6063)
You are using -cpinternal iso8859-1 and the code page of the library p-test.pl is ibm866. (4307)
The table to convert iso8859-1 to ibm866 was not found in convmap.cp. (4308)
The library contents may not be displayed correctly. (4310)
Listing of library 'p-test.pl'
Library code page is ibm866. (4309)
--> note ibm866 and the conversion errors
proenv>prolib p-test.pl -list -pf prolib.pf
Listing of library 'p-test.pl'
Library code page is ibm866. (4309)
--> note no conversion errors
proenv>more prolib.pf
-cpcase Basic
-cpinternal ibm866
-cpstream ibm866
-cpcoll Russian
Enhancement Request (PSC00317597) was created to capture the notion that prolib should support startup.pf.
prolib doesn't read startup.pf or any .pf files. It has its own code to handle startup parameters and doesn't recognize the complete set of client parameters.
It is as I expected.
It would be nice if it somehow was noted in the documentation ;-)
Thanks Matt!
Regards,
Valeriy
prolib *does* read .pf file:
proenv>prolib p-test.pl -create -add *.r
proenv>prolib p-test.pl -list
Listing of library 'p-test.pl'
Library code page is iso8859-1. (4309)
--> note iso8859-1
proenv> del p-test.pl
proenv>prolib p-test.pl -create -add *.r -pf prolib.pf
proenv>prolib p-test.pl -list
Code page conversion table for IBM866 to ISO8859-1 was not found in convmap.cp.(6063)
You are using -cpinternal iso8859-1 and the code page of the library p-test.pl is ibm866. (4307)
The table to convert iso8859-1 to ibm866 was not found in convmap.cp. (4308)
The library contents may not be displayed correctly. (4310)
Listing of library 'p-test.pl'
Library code page is ibm866. (4309)
--> note ibm866 and the conversion errors
proenv>prolib p-test.pl -list -pf prolib.pf
Listing of library 'p-test.pl'
Library code page is ibm866. (4309)
--> note no conversion errors
proenv>more prolib.pf
-cpcase Basic
-cpinternal ibm866
-cpstream ibm866
-cpcoll Russian
Libor is right. I verified that prolib doesn't read startup.pf and that it doesn't use the client's code to handle parameters but then I made the incorrect conclusion that prolib doesn't handle any .pf files. As Libor pointed out, it will read .pf files which are explicitly loaded with -pf.
Thanks Libor and Matt!
As I write above "It would be nice if it somehow was noted in the documentation".
Regrads,
Valeriy
Ø As I write above "It would be nice if it somehow was noted in the documentation".
[quote user="Libor Laubacher"]
Ø As I write above "It would be nice if it somehow was noted in the documentation".
[/quote]
Except the prolib utility - so it's mean that it is a bug in prolib?
Enhancement Request (PSC00317597) was created to capture the notion that prolib should support startup.pf.
[quote user="Evan Bleicher"]
Enhancement Request (PSC00317597) was created to capture the notion that prolib should support startup.pf.