RE: Unusual date / time stamp error when EXFMT is run

It sounds like you has F12 defined as CF12 which processes the screen
(checks for the dates to be valid) prior to sending control back to your
program.  Use CA12 instead, the system will not check the date values
prior to returning control back to your program.

Michael Tobey
Applications Analyst
Foremost Farms USA (Consumer Products)
mike.tobey@xxxxxxxxxxxxxxxxx


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Douglas W. Palme
Sent: Tuesday, October 25, 2005 3:25 PM
To: RPG Group
Subject: Unusual date / time stamp error when EXFMT is run

I have a DSPF wherein the user can either enter in some information for
a report, IE: start date, end date, class and cat of freight.  when they
hit the enter key the program will process the data and then submit the
report to batch.

The DSPF has two date fields which are defined as type L, DSTARTDATE and
DENDDATE, with a DATFMT(*USA) parameter.

If the user wishes to exit the program they simply strike the F12 key
which in turn turns on *IN12 which is used to exit the program.

I set it up this way to allow the user to submit more than one report to
batch....it loops until the *IN12 is turned on.  However if a user
starts the program and then decides before entering any dates to F12
out, it generates an error when it tries to read the DSPF.....is there
any way to avoid this problem?



If you bought it, it was hauled by a truck - somewhere, sometime.

--
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.