using LIKE() for data length and changing data type -- RPG400-L

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

Subject: using LIKE() for data length and changing data type
From: Dan <dbcerpg@xxxxxxxxx>
Date: Tue, 18 Feb 2003 12:21:51 -0800 (PST)
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>,<mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>,<mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

I thought this was possible, but am getting stumble-blocked.

I want to define a stand-alone variable in RPG-IV (v4r5) that is character with 
the same length as
the data length of a database field that is a packed numeric.  So, if field 
CustNumber in a file
is defined as 8,0 packed, I want a standalone field CustNumberAlpha to be 
defined as 8 character. 
Without having to hardcode the 8.

A data type entry is not allowed on a D-spec when the LIKE keyword is being 
used.

Is there a way to do this in v4r5?  If not, how about v5r2?

TIA, Dan

__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: using LIKE() for data length and changing data type , Barbara Morris
Re: using LIKE() for data length and changing data type , rob

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.