Re: Oops prevention: is there an easy way to detect if the compilers are disabled?

Hi, James:

Compile any valid source, such as QGPL/QRPGLESRC member PROOF with CRTBNDRPG to test ILE RPG IV compiler, and compile QGPL/QRPGSRC member PROOF with CRTRPGPGM to test the "legacy" (RPG/400) compilers. If you MONMSG these CRTxxx commands (assuming you run this test from within a CL program), those commands should throw an escape message if the license is expired.

You could even generate a minimal source member to compile, in QTEMP, just for such tests, and compile the object(s) into QTEMP.

HTH,

Mark S. Waterbury

> On 5/9/2012 8:06 PM, James Lampert wrote:

Here's the scenario:

Regeneration of an environment for an application.

Files get regenerated with structure changes, RPG programs get
regenerated over the restructured files. All under the automated control
of an environment modification and regeneration utility.

But for some reason, the customer has an expired license on their
development tools, and some poor schmuck didn't think about that before
doing a regen.

Thankfully, when this actually happened, it was on a test environment,
rather than the live one; if it had been the latter, they'd probably not
be happy campers.

Given that scenario, is there any way for this environment modification
and regeneration utility to check to make sure the compilers are
available before it allows regeneration (or any changes requiring
regeneration)?

--
JHHL