The problem with the sequence current values is that the code still uses static access to the sequences ( compiled on-the-fly ) which means you need to have a developer license of some sort installed in order to be able to dump them. The procedure that does it is called _dmpseqs.p which you can find in src/prodict ( you might need to extract the prodict.pl first ). You can easily adopt the logic that it uses dynamic access to the sequence so that it does not need to be compiled on-the-fly. Have a look on the DYNAMIC-CURRENT-VALUE statement.
Heavy Regards, RealHeavyDude.
Thanks for the reply.
In my progress 11.2 version, I have found prodict/dmpseqvals.p instead prodict/_dmpseqs.p. I am calling this procedure as below,
/** dump_seq.p **/
def var v-dest-dir as char no-undo.
def stream strm.
assign v-dest-dir = os-getenv("DEFAULTDEST").
run prodict/dmpseqvals.p
(input "ALL",
input (v-dest-dir),
input ?).
quit.
/** dump_seq.p **/
When i run this as
# mpro /skp/db/apprules/apprules -b -p /opt/v112/src/dump_seq.p
It is giving below error,
"Procedure /opt/v112/src/dump_seq.p passed parameters to prodict/dmpseqvals.p, which did not expect any. (1005)"
If i remove the parameters its giving error as,
"** Unable to open file: . Errno=2. (98)"
Can you please help me where is the problem?