numcheckpointstats does not work

Posted by Dmitri Levin on 26-Apr-2018 07:58

Every time I try something new Progress bites me back.

This time I tried a new parameter -numcheckpointstats

Since it is not in 11.6 documentation and it is in 11.7 documentation, I assume it is a brand new one.

When starting sports database with -numcheckpointstats 64 I am getting the following error and sports database does not start.

$ proserve -pf sports.pf

OpenEdge Release 11.7.1 as of Wed Jun 14 19:00:30 EDT 2017
08:39:55 SERVER : ** Could not recognize argument: -umcheckpointstats. (301)

It does not work without -pf file, on a command line also

$ proserve -pf sports.pf -numcheckpointstats 64

OpenEdge Release 11.7.1 as of Wed Jun 14 19:00:30 EDT 2017
08:51:25 SERVER : ** Could not recognize argument: -umcheckpointstats. (301)

Use Number of checkpoint statistics (-numcheckpointstats) to specify the number of rows maintained in

the_Checkpoint VST. 

Multi-user default is 32

OpenEdge 11.7.1 on IBM AIX 7.1

Posted by meehan on 26-Apr-2018 08:06

 
 
Please try it this way:
 
 
    -numCheckpointStats
 
 
 
 

Posted by Rob Fitzpatrick on 26-Apr-2018 08:07

Dmitri, this is a doc bug.  Try "-numCheckpointStats".  

All Replies

Posted by meehan on 26-Apr-2018 08:06

 
 
Please try it this way:
 
 
    -numCheckpointStats
 
 
 
 

Posted by Rob Fitzpatrick on 26-Apr-2018 08:07

Dmitri, this is a doc bug.  Try "-numCheckpointStats".  

Posted by n.lewers on 26-Apr-2018 08:09

Is just me or is there something wrong with the error as well, -umcheckpointstats. (301)  (NO N at the beginning).  perhaps try starting with what the error is using -umcheckpointstats

Posted by Dmitri Levin on 26-Apr-2018 08:12

Thank you. -numCheckpointStats works fine. Doc need to be fixed.

Posted by Rob Fitzpatrick on 26-Apr-2018 08:12

> Is just me or is there something wrong with the error as well, -umcheckpointstats. (301)  (NO N at the beginning).

The problem is not particular to this parameter.  It's a limitation in the parameter-parsing logic that it often gives error messages that don't make sense when dealing with misspelled parameters.

Posted by Rob Fitzpatrick on 26-Apr-2018 08:20

Examples:

proserve sports -prefetchfactor

You have not supplied a parameter for argument -p. (1403)

proserve sports -prefetchfactor 100

You have not supplied a parameter for argument -e. (1403)

Posted by meehan on 26-Apr-2018 09:46

 
 
I opened new doc issue for this:
 
Issue:PSC00365117
 
 
 

Posted by Dmitri Levin on 26-Apr-2018 10:40

Thank you Ken

This thread is closed