Re: Time constant

Okay, I upgraded and the error went away.

I did have a weird occurrence in that now it seems to want to parse every member that I have open, which means contacting every machine for which I might have a member open.  This gets problematic when they're on VPNs to which I'm not currently connected.  Not the end of the world, by any means, but it was interesting.

I'll probably have to amend my current practice of having lots of member open.

But anyway, my original issue is gone.  Yay!

Thanks, Vern.

I went back and checked on 9.5 and it works there as well.

I've held back on upgrading because of the issues with 9.6.0.2, but it looks like it's time to go up to 9.6.0.3.

Hardest thing to find is the thing that is not there! This both verified and compiled just fine for me - 7.3 of i5/OS and 9.6.0.3 of RDi.

I also added DSPLY C_SHUTDOWNTIME; and it compiled and ran fine.

Cheers
Vern

On 6/3/2018 10:29 AM, Joe Pluta wrote:

Here's a fun one.  I cannot figure out how to define a time constant in free-form RPG in RDi.  I'm at version 9.6.0.1:

Literally, this three-line program will not verify:

       ctl-opt actgrp(*new) option(*srcstmt:*nodebugio);
       dcl-c C_SHUTDOWNTIME t'23.50.00';
       return;

No matter what I try, I get RNF0306E saying the format is not valid.  I tried adding TIMFMT(*ISO) to the ctl-opt specification (didn't change the error) and to the dcl-c (keyword not allowed).

I save the member and it compiles correctly, but this specification won't pass muster.

Anybody else?