|
Display System Value
System value . . . . . : QDATFMT
Description . . . . . : Date format
Date format . . . . . : MDY YMD, MDY, DMY, JUL
===========================================================
Display System Value
System value . . . . . : QDATE
Description . . . . . : System date
Date . . . . . . . . . : 05/23/00 MM/DD/YY
============================================================
Is this what you are talking about when you write, "is your system default set
at YYYYMMDD as a
default?".
TIA,
|--------+------------------------>
| | boothm@earth.G|
| | oddard.edu |
| | |
| | 05/22/2000 |
| | 08:38 PM |
| | Please respond|
| | to RPG400-L |
| | |
|--------+------------------------>
>--------------------------------------------------------|
| |
| To: RPG400-L@midrange.com |
| cc: (bcc: Darlene H Bryant/Banpharm) |
| Subject: Re: *MDY (Factor 1) for Version 4r4 |
>--------------------------------------------------------|
I've not tried using edit code Z on a date field on the screen. I use
edit code Y. Would that make a difference? (I also find the users like
the EDTCDE(Y) a lot better too as they can enter their dates successfully
in a number of ways.)
So far as the rest goes, is your system default set at YYYYMMDD as a
default? I am used to seeing date fields in the D Specs defined as "D"
fields, not "S" fields. I'm also used to date fields not otherwise
defined being stored as mmddyy.
_______________________
Booth Martin
booth@martinvt.com
http://www.MartinVT.com
_______________________
dbryant@banpharm.com
Sent by: owner-rpg400-l@midrange.com
05/22/2000 08:47 AM
Please respond to RPG400-L
To: RPG400-L@midrange.com
cc:
Subject: *MDY (Factor 1) for Version 4r4
We converted our OS/400 from V4R3 to V4R4 a few weeks ago. I am having
some
difficulties with the *MDY with the "Move" Operator. These calculations
were
working fine in v4r3..
#BEGDAT is defined within the Screen DDS as a (6,0) Numeric field. The
user will
key in the MMDDYY.
A #BEGDT 6Y 0B 13 37COLOR(WHT)
A EDTCDE(Z)
PXBEGDT is defined within the File DDS as a Date Field (CCYYMMDD)....
A PXBEGD L TEXT('Date')
C *MDY move #BEGDT PXBEGD
In V4R3 we compiled all programs using CVTOPT(*DATETIME), but now in V4R4
is
will not compile with the CvtOpt option of *DATETIME, I have to use *NONE
for
this parameter or it will not compile.
Also, now I cannot use the INZ on a program defined Date Field. **I tried
to
use INZ(d'0001-01-01')** as well, but the compiler didn't like that
either.
What's the buzz??
D LowDate S LIKE(PXBEGD) INZ('0001-01-01')
D HighDate S Like(PXENDD) INZ('2040-12-31')
*RNF3430 20 68 006501 Initial value '0001-0... does not match data
type of
field
LOWDATE. Initial value is ignored.
If I wanted to initialize the Program Defined Date Field in the "D" Spec,
how
would I code It??
TIA,
Darlene Bryant
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.