Troubleshooting
Problem
This document explains how IBM i NetServer interacts with Coded Character Set Identifiers on the IBM i and on the PC.
Resolving The Problem
Most information exchanged between a Microsoft Windows PC and IBM i NetServer is sent in unicode. This includes information such as all path names, file names and so on. Other types of information, however, require that the NetServer know the ASCII CCSID used by the clients. This information includes things such as:
|
o | File CCSID The IBM i Integrated File System tracks a CCSID file attribute. This CCSID represents the CCSID that the file was created with. When a file is created through NetServer, the CCSID of the file is the CCSID of the share or, if not provided, the CCSID of the server. |
| o | Text Conversion When text conversion is configured for a share, the conversion is between the CCSID of the file and the CCSID of the share (which defaults to the CCSID of the server). |
| o | Other Data Some data such as share names and server information is sent in ASCII. Typically this type of information is restricted to the invariant character set to prevent possible conversion problems. When working with Windows clients that do not support unicode, the server CCSID must reflect the CCSID of the clients. |
Additional Note - added for searchability:
The name i5/OS NetServer may be used interchangeably with IBM i NetServer, System i NetServer, iSeries NetServer, OS/400 NetServer, or (older) AS/400 NetServer or AS400 NetServer.
[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.1.0"}]
Historical Number
23405822
Was this topic helpful?
Document Information
Modified date:
18 December 2019
UID
nas8N1017350