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



All, thanks for the help.

Have tried typing the pound sign in lpex saving and viewing in SEU : no problem.
Also, Arco has a different result from me. The fact that I only have the problem when I put the library name in front of the program name suggests a bug rather than ccsid. If do "call mypgm£", I get back the message with mypgm£ in the log.

PC is well above minimum recommendation, but only 1.83GB ram.

Fix pack??? why the hell are IBM giving an unfixed pack as the trial version? When I look I see V 7.6 (7.6.0.20100331_1610) in IBM Installation Manager. Doesn't that mean I have the fixpack 7.6.0.1 ?




-----Message d'origine-----
De : wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx] De la part de Arco Simonse
Envoyé : mercredi 29 septembre 2010 19:21
À : Rational Developer for IBM i / Websphere Development
Studio Client for System i & iSeries
Objet : Re: [WDSCI-L] RDP not working right

Hi David,

Is your pc hardware and memory sufficient? And did you update
your RDP after installation to fixpack 7.6.0.1 ?

I tried your pound token issue, and get the same results as you do:

call mypgm£
Value 'MYPGM£ ' for parameter PGM not a valid name.
Cause . . . . . : Value 'MYPGM£ ' contains characters
that are not
valid in a name or is a single value that was specified as
part of a qualifier. A name must begin with an alphabetic
character followed by alphanumeric characters, or if the
value is a string of characters, it must be enclosed in
quotation marks.

call mylib/mypgm£
Characters in qualifier beginning 'MYPGM£ ' not valid.
Cause . . . . . : The qualifier must be a valid character string, a
numeric or a predefined value.

Best regards,
-Arco

--


2010/9/29 David FOXWELL <David.FOXWELL@xxxxxxxxx>

2nd day into the 60 day trial and RDP7.6 has just locked up on me,
right in the middle of modifying an RPG. I was trying to
check out the
multiple editing screen. When the others find out, this is going to
get the thumbs down. It'll be business as usual, SEU for most, and
back to the Arkansas Chutterbug for me ( my affectionate
name for my WDSCV6).

Is there anything I need to get checked out on the i or my PC?

Also, would someone try this test for me and see what
happens - type a
call to a program with a name ending with the £ character in the
command history view. If I type CALL MYPGM£ all is ok but if I type
CALL MYLIB/MYPGM£ I get the message roughly translated, "the name
beginning with 'MYPGMÂ# ' contains incorrect characters'.

Thanks a lot.
--
This is the Rational Developer for IBM i / Websphere Development
Studio Client for System i & 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 is the Rational Developer for IBM i / Websphere
Development Studio Client for System i & 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 ...

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.