× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. January 2016

Re: RPG Free qualified DS RNF008 error V7R1

Since this was generated code from a wsdl, it was the wsdl <part name =
"in" that caused this.
I will pursue my timestamp issues in a new thread.
thx to all
Jim

On Tue, Jan 19, 2016 at 1:50 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

Yeah, the message saying "Factor 1..." - Factor 1 is a vestige of fixed
format RPG, I believe.

Here's the 2nd-level text for the RNF5008 message from message file
QRPGLEMSG in QDEVTOOLS -

The Factor 1 operand is not valid. The Factor 1 operand must be blank or a
valid name, literal, constant, special word, or format code.

Weird in free-form, but suggests maybe an invalid name, as you say -

One thing - in is a operation in RPG - for bringing IN the contents of a
data area - probably can't be used as anything related to a variable name.

Good luck!
Vern


On 1/19/2016 12:30 PM, Jim Franz wrote:

same error
000105 in.StartDate =
%timestamp('2015-12-08-14.26.46');
======> a
b
*RNF5008 20 a 000105 Factor 1 operand is not valid; defaults to
blanks.
*RNF5507 30 b 000105 A semi-colon is not specified at the end of a
free-format

specification.
000106 in.EndDate =
%timestamp('2015-12-16-00.00.00');
======> a
b
*RNF5008 20 a 000106 Factor 1 operand is not valid; defaults to
blanks.
*RNF5507 30 b 000106 A semi-colon is not specified at the end of a
free-format

specification.


exact same error if eval is a timestamp field

000109 in.StartDate =
xstamp;
======> a
b
*RNF5008 20 a 000109 Factor 1 operand is not valid; defaults to
blanks.
*RNF5507 30 b 000109 A semi-colon is not specified at the end of a
free-format

specification.

I am certain this error has nothing to do with "timestamps" (although I
appreciate the format corrections
Working my way through the 250 page compile listing, but looks to be
related to "in." not being a data area..
Jim



On Tue, Jan 19, 2016 at 1:07 PM, Glenn Gundermann <
glenn.gundermann@xxxxxxxxx> wrote:

Replace the colons with periods. As in hh.mm.ss

Yours truly,

Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Work: (416) 675-9200 ext. 89224
Cell: (416) 317-3144


On 19 January 2016 at 12:50, Jim Franz <franz9000@xxxxxxxxx> wrote:

The timestamp itself is something I'm looking at, but I think is not what
is causing the error.
This fails (and also with z'2015...)

000105 in.StartDate =
%timestamp('2015-12-08-14:26:46');
======> a
b
*RNF5008 20 a 000105 Factor 1 operand is not valid; defaults to
blanks.
*RNF5507 30 b 000105 A semi-colon is not specified at the end of a
free-format

specification.
000106 in.EndDate =
%timestamp('2015-12-16-00:00:00');
======> a
b
*RNF5008 20 a 000106 Factor 1 operand is not valid; defaults to
blanks.
*RNF5507 30 b 000106 A semi-colon is not specified at the end of a
free-format

specification.

I assumed it is complaining about in. - the qualified data
structure
Am ignoring the green screen source edit :
Message ID . . . . . . : RNF5008 Severity . . . . . . . : 20
Message type . . . . . : Diagnostic

Message . . . . : Factor 1 operand is not valid; defaults to blanks.
Cause . . . . . : The Factor 1 operand is not valid. The Factor 1

operand

must be blank or a valid name, literal, constant, special word, or

format

code.
Recovery . . . : Correct the Factor 1 operand. Compile again.

Even this fails the screen edit: in.StartDate = StartDT;

But I do have to work out the timestamp format issues - this is a web
service program to a unix DB2 system,
and it is expecting this for a timestamp
'2015-12-08T14:26:46' without additional zeros at end (fails

with

them)

Jim Franz


On Tue, Jan 19, 2016 at 12:13 PM, Vernon Hamberg <

vhamberg@xxxxxxxxxxxxxxx

wrote:

Hi Jim

Your timestamp format is invalid, I think - that is the format SQL

Server

wants, maybe it's an ODBC ISO format.

Here from the RPG reference on timestamp literals -

Timestamp literals have the form Z'yyyy-mm-dd-hh.mm.ss', optionally
followed by a period followed by zero to twelve fractional seconds,
Z'yyyy-mm-dd-hh.mm.ss.frac'

But in the %timestamp() built-in-function, I think you don't need the
leading Z.

HTH
Vern


On 1/19/2016 10:59 AM, Jim Franz wrote:

Getting a compiler error from CRTRPGMOD

000105 in.StartDate =
%timestamp('2015-12-08T14:26:46');
======> a
b
*RNF5008 20 a 000105 Factor 1 operand is not valid; defaults to
blanks.
*RNF5507 30 b 000105 A semi-colon is not specified at the end

of a

free-format

specification.
000106 in.EndDate =
%timestamp('2015-12-16T00:00:00');
======> a
b
*RNF5008 20 a 000106 Factor 1 operand is not valid; defaults to
blanks.
*RNF5507 30 b 000106 A semi-colon is not specified at the end

of a

free-format

specification.

same error if statement in.StartDate = StartDT;

statement starts in column 10, so not the ptf issue with /free code in
column 1 - 6
5770WDS SI51094 is applied.

Many other ptfs for WDS in google - hoping to narrow this down.
Not an option to load cume (that requires a month of testing ...)

This is code generated from WSDL2RPG but all I see says this should

work.

This is most of the parms for CRTRPGMOD
CRTRPGMOD MODULE(FRANZJI/WS0001R) SRCFILE(*LIBL/QRPGLESRC)

SRCMBR(WS0001R)

GENLVL(10) DBGVIEW(*LIST) OPTIMIZE(*NONE) INDENT(*NONE)

CVTOPT(*NONE)

TRUNCNBR(
*NO) FIXNBR(*NONE) TGTRLS(*CURRENT) ALWNULL(*NO) DEFINE(*NONE)
BNDDIR(*NONE)

Jim Franz

--
This is the RPG programming on the IBM i (AS/400 and iSeries)

(RPG400-L)

mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.