CCSID on V5R4 to be set when connecting to an external db2 luw: CLOSED

Dear Colleagues,
dear Dan Kimmel and dear CRPence,
many thanks for your responses, that have addressed to me on what to do.
Here a little description of my analysis and the corresponding actions.
1 - access from iSeries to a remote DB2 via SQL involves following the DRDA architecture (iSeries Information Center, Version 5 Release 4 -> Distributed relational database on i5/OS)
2 - importance of moving from code 63365 (that means "no translation") to CCSID = 500 as suggested by you and described in the iSeries Information Center, Version 5 Release 4 -> CCSID considerations for SQL, that I did'nt read;
3 - such a setup activates the authomatic translation of characters therefore I succeeded into connecting;
4 - after that way I used the interactive SQL, as a client, and run queries in front of my customer;
5 - it was a demo, first executed on test machines, then on production ones;
6 - without this setup I had troubles in that connection that was refused for wrong codepage.

Here my commands:
- WRKRDBDIRE, to set the remote db name + tcp address
- CHGJOB CCSID(500), to change the CCSID for that work only;
- To connect by strsql
- and then to execute query etc. (here you can write qualified name of db2 objects as in syscat.tables, exactly as in DB2 Linux).

Thanks to everybody for the cooperation, and best regards.
carlo lunghi