The funny thing is that when I take the Options( *NullInd ) off the 2nd
prototype, I get an informational message for the date field parameter:
The parameter has a null byte map, but OPTIONS(*NULLIND) is not
specified on the prototype.
Kurt Anderson
Application Developer
Highsmith Inc
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Kurt Anderson
Sent: Tuesday, September 04, 2007 9:10 AM
To: RPG programming on the AS400 / iSeries
Subject: Options(*nullind)
Hi,
I have a date field in a file defined with the AlwNull keyword. When I
pass this date to a prototype, I'm specifying Options(*nullind) so it
passes the null indicator. However, once I try to pass that date onto
another subprocedure, it's telling me:
RNF7355: Parameter 1 is not valid for the OPTIONS(*NULLIND) parameter.
The date field is the 1st parameter.
1st prototype
// Process the Order Detail
D PrcOrdDtl PR
D Order Const Like( OHNum )
D Type 1a Const
D ExpShipDate d Const Options( *NullInd )
2nd prototype
// Validate the Expected Ship Date
D vldExpShpDate PR n
D ExpShpDate d Const Options( *NullInd )
What am I doing wrong here? I tried changing the Ship Date parameters
to be Like() the date from a file.
Kurt Anderson
Application Developer
Highsmith Inc.
W5527 State Road 106, P.O. Box 800
Fort Atkinson, WI 53538-0800
TEL (920) 563-9571 FAX (920) 563-7395
EMAIL kjanderson@xxxxxxxxxxxxx
--
This is the RPG programming on the AS400 / 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.
midrange.com
