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



If you move 123456 into your key field, then do a START FILE-NAME KEY NOT < KEY-NAME that will position the record pointer to the first record. As you execute your READ FILE-NAME NEXT RECORD statements, check to see if the key field = 123456

----- Original Message ----- From: "Joe Folorunso" <jfolorunso@xxxxxxxxx>
To: <COBOL400-L@xxxxxxxxxxxx>
Sent: Sunday, June 04, 2006 9:28 PM
Subject: [COBOL400-L] Wild Card Processing


 How do one process wild cards using COBOL/400  for example if I
have a field that   partial information is provided and I have to process
all records with same information. For example if the user only supplies me with this type of value for this field that contain 20 characters but only provides me with 6 characters like this 123456* do I use an embedded SQL or make the field a partial list of a key in order to process this records. Thanks.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list
To post a message email: COBOL400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/cobol400-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.