|
Hi Darryl
Heres a suggestion - don't know if this will give you what you want -
using SST
You can create a logical over the physical
Here is an example of a logical
*************** Beginning of data ****************************************
A R CALNDARR PFILE(CALENDAR)
A CALNDATE
A CALNDTMM 2 I SST(CALNDATE 1 2)
A CALNDTDD 2 I SST(CALNDATE 3 2)
A CALNDTYY 2 I SST(CALNDATE 5 2)
A CALNTELUPD
A CALNSBMDT
A CALNSBMTM
A K CALNDTYY
A K CALNDTMM
A K CALNDTDD
****************** End of data *******************************************
Here is the physical
*************** Beginning of data ******************************
******************
A R CALNDARR
A CALNDATE 6S 0 TEXT('Date')
A CALNTELUPD 1 TEXT('TELUPD today?')
A CALNSBMDT 6S 0 TEXT('Date Next TELUPD
submission')
A CALNSBMTM 6S 0 TEXT('Time Next TELUPD
submission')
****************** End of data ******************************
*********************
Ive never used it to redefine a character field into a numeric field though
What happens if the field contains other than numeric?
Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
a4g atl
Sent: Wednesday, October 18, 2017 11:48 AM
To: midrange-l@xxxxxxxxxxxx
Subject: is there a way using DDS in a LF to test if a field contains
alpha, numeric or blanks?
I have an issue where we have a PF with a field (door number, 5A) that
needs to be defined as a numeric field.
I have been asked to not use a SQL View which I have used using a CASE
statement to test for alpha, numeric or blanks. This works.
The manager wants it done in DDS in a logical file. As far as I can
remember this is not possible, but I want to verify before I take up the
subject with management.
TIA
Darryl Freinkel
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:
MIDRANGE-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list
options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@
midrange.com> Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any
subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
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.