CL Command Reference - CVTDLSNAM
CL Command List > CVTDLSNAM Reference
Description:
The Convert Document Library Services Name (CVTDLSNAM) command is used before or after a change in the CCSID assumed for EBCDIC object names by QDLS (the document library services file system). The command can help identify QDLS object names that may be different because of the CCSID change, and it can rename QDLS objects so they retain their original names. It can also correct the names of objects whose names changed when they were copied between QDLS and another file system. The command prints a report with the job¡¯s spooled output that lists selected objects and any actions taken on those objects.
When converting object names to or from EBCDIC, QDLS uses the job default CCSID unless data area QUSRSYS/QODEC500 exists, in which case QDLS uses CCSID 500 (the data area allows reversion to the behavior of early versions of QDLS). The CCSID used by QDLS is therefore changed by creating or deleting the data area, or by changing the job default CCSID when the data area does not exist.
The CCSID affects the view of QDLS object names by integrated file system clients of QDLS, which must convert object names to and from EBCDIC. Those clients include:
. Integrated file system commands such as DSPLNK, CPY, MOV, and RNM
. UNIX-type APIs provided by the integrated file system, such as access, open, rename, and unlink
. IBM eServer iSeries Access for Windows
The CCSID does not affect clients of QDLS that work directly with EBCDIC object names, which include:
. Document and folder commands, such as CRTDOC, CPYDOC, WRKDOC, CRTFLR, WRKFLR, DLTDLO, and RNMDLO
. Hierarchical file system (HFS) APIs, such as QHFDLTSF, QHFOPNDR, QHFOPNSF, and QHFRNMSF
Even for integrated file system clients of QDLS, the CCSID doesn¡¯t matter except for objects that are also used by EBCDIC clients. In that case, QDLS object names may appear different to the clients if the names contain variant characters and the clients are using different CCSIDs (integrated file system clients use the CCSID as described earlier, and EBCDIC clients likely use the job default CCSID).
Restrictions:
. You must have read (*R) authority to the directory containing the object links and execute (*X) to the other directories in the path.
. The additional authority restrictions from the RNM command apply when renaming objects.
Examples:
Example 1: List QDLS Objects Affected by a CCSID Change
A new release of the operating system is installed and QDLS now assumes the job default CCSID instead of CCSID 500 for EBCDIC object names. The job CCSID is currently set to 37. The following command is used to identify the objects that effectively have new names for integrated file system clients of QDLS. Note that the ACTION, FROMCCSID, and TOCCSID parameters could all have been omitted from the command, since they specify the default values in this case.
CVTDLSNAM OBJ(¡¯/QDLS¡¯) SUBTREE(*ALL) ACTION(*LIST)
FROMCCSID(500) TOCCSID(37)
Output similar to this might be produced:
/QDLS/FLRA/X] --> X!
/QDLS/FLRB/X! --> X|
Each line shows two names for an object, as it would be seen by clients using CCSID 500 and CCSID 37 (the second name won¡¯t be shown if TOCCSID is *HEX). The output shows that two objects are affected by the change of the assumed CCSID. The object known before the change as X] by integrated file system clients is known as X! afterward, and X! is renamed to X|.
The name X! seems more reasonable than either X] or X|, so we assume X! is the correct name in both cases. In the first case the new name is desirable; we surmise the object was created as X! by a client using CCSID 37. In the second case the new name is undesirable; the object was presumably created by a client using CCSID 500.
Example 2: Rename QDLS Object to Adjust for a CCSID Change
The second object name from the example above is corrected using the following command. For this example the job CCSID is 500 (necessary to guarantee correct recognition of the object name X!). It is likely that a generic name (such as * or X? instead of X!) would be used in similar situations, eliminating the need to adjust the job CCSID.
CVTDLSNAM OBJ(¡¯/QDLS/FLRB/X!¡¯) ACTION(*RENAME)
FROMCCSID(500) TOCCSID(37)
This output might be produced:
/QDLS/FLRB/X! --> X]
Each line again shows two names for an object, but this time both names are what a CCSID 500 client would see. The output indicates that X! is renamed to X]. The new name may appear incorrect to a CCSID 500 client (X]), but it will appear as desired to a CCSID 37 client (X!).