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



According to DDS Reference, '£' is not valid for a field name.  
http://publib.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/QB3AUI03/1.2.2?SHELF=&DT=19990811160340&CASE=
The DDS syntax rules for record and field names are: 

Names must be 10 characters or less. 

Names must begin with an alphabetic character (A through Z, @, $, and #). 
All subsequent characters can be alphanumeric (A through Z, 0 through 9, 
@, $, #, and _ (underscore)). There can be no embedded blanks. 

I also tried to create a display file containing the code including '£' in 
customer's email below.  In the 5250 edit mode, an error is shown to 
indicate that '£' is not valid in the field name (Character after first 
character of name not valid). 

If the display file is saved anyway, compiling it will throw the same 
CPD7425 error again.

So I think in the your maybe you were using a different language (CCSID) 
so that '£' was mapped to a valid character for field name, eg, @, $, or # 
?   To convert the display file properly you may need to change the 
iSeries user locale and current locale on PC to use the right language. 

Now, I seem to recall somewhere that the codepoint used for '$' in NA is 
used for '£' in the UK ?  So following the above it could be that the 
iSeries is set to a UK-English locale and the PC set to a US-English 
locale or some such.

Mike


Mike Hockings, P.Eng.
WebSphere Development Tools for AS/400  -  CODE/Designer & WebFacing !
IBM Canada Ltd. Laboratory 
hockings@xxxxxxxxxx 





"Steve Lakin (Ramesys - Nottingham)" <Steve.Lakin@xxxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
01/13/2005 12:22 PM
Please respond to
Websphere Development Studio Client for iSeries 


To
"'Websphere Development Studio Client for iSeries'" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
RE: [WDSCI-L] Problem with conditioned fields






I have managed to establish that this is a problem with the £ in the
fieldname. I changed the field to WXTOVL and reconverted and it worked 
fine.
Does anyone know if this is a known issue and whether theres a fix for it? 
I
really hope there is as this could potentially put our project on hold as 
we
use £'s for all value fieldnames.

Regards,
 
Steve Lakin
ERP Analyst Programmer
Ramesys
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] 
On
Behalf Of Steve Lakin (Ramesys - Nottingham)
Sent: 13 January 2005 09:55
To: 'Websphere Development Studio Client for iSeries'
Subject: [WDSCI-L] Problem with conditioned fields

I am trying to webface a DDS member containing the following piece of 
code:

A N91        W£TOVL    R        O  5 62EDTCDE(L)

A  91        WCTOVL    R        O  5 62EDTCDE(L)


When I run the application this screen crashes saying that it expected to
receive 17 fields but it actually received 18. In the error message the 
list
of fields only contains WCTOVL. If I comment out W£TOVL and recompile the
DDS the application runs fine. Is this a known bug with the conversion
process? It's a pretty major one if it is. We have code like this all over
our application and I dare say so do a lot of people.

Regards,
 
Steve Lakin
ERP Analyst Programmer
Ramesys



**********************************************************************
This communication contains information that is confidential and may also 
be
privileged.  Any offers and/or commitments made within this document are
subject to contract and without prejudice.  It is for the exclusive use of
the intended recipient(s).  If you are not the intended recipient(s) 
please
note that any form of distribution, copying or use of this communication 
or
the information within it is strictly prohibited and may be unlawful.
If you have received this communication in error, please return it with 
the
subject line "received in error" to it.security@xxxxxxxxxxx then delete 
the
mail and destroy any copies of it.

www.ramesys.com
**********************************************************************

-- 
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


**********************************************************************
This communication contains information that is confidential and may also 
be
privileged.  Any offers and/or commitments made within this document are
subject to contract and without prejudice.  It is for the exclusive use of
the intended recipient(s).  If you are not the intended recipient(s) 
please
note that any form of distribution, copying or use of this communication 
or
the information within it is strictly prohibited and may be unlawful.
If you have received this communication in error, please return it with 
the
subject line "received in error" to it.security@xxxxxxxxxxx then delete 
the
mail and destroy any copies of it.

www.ramesys.com
**********************************************************************

-- 
This is the Websphere Development Studio Client for iSeries  (WDSCI-L) 
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.