Override scope for OVRDBF

Hi group,

we have a big legacy application which was mostly written in RPG/400, but
here and there even some OCL still remains, although that has fortunately
been replaced in most environments.

When we write new applications or do major customizations in existing ones,
we create/convert to RPG IV, because it's simply more powerful (and easier
on the eyes).

However, after conversion we frequently have errors about commitment
control.

As a result, we have to trace the entire call flow to ensure that
everywhere the OVRDBF command has OVRSCOPE(*JOB) specified.

My question is:  would it do any harm to OPM programs if we change the
command default of OVRDBF to always use OVRSCOPE(*JOB)?

I don't know whether this is relevant, but we don't use ILE, only the
CRTBNDRPG kind of programs.

Thanks for any input you can provide.

Peter Colpaert
Application Developer

Honda Europe NV
Langerbruggestraat 104
B-9000 GENT
Peter.Colpaert@honda-eu.com
Tel: +32 9 2501 334
Fax: +32 9 2501 231
----------
To know recursion, you must first know recursion.
----------