DDM architecture-related restrictions
The items listed in this topic are DDM architecture-related restrictions. Therefore, application programs that use these items might have to be changed and recompiled before they can access remote files.
- The DDM architecture does not support iSeries™ multi-format logical files. However, because multi-format logical files are supported as an System/38™ extension to the DDM architecture, they can be used with DDM, but only if the source and target servers are iSeries servers or System/38s.
- Externally described data (using data description specifications [DDS] on an iSeries server) is not supported by the DDM architecture. However, DDS can still be used, especially if both systems are iSeries servers or System/38s. If the target server is an iSeries server or a System/38, most of the DDS support can be used as though the remote file is a local file.
- To access folder management services objects, the source server must support Level 2.0 or Level 3.0 of the DDM architecture for stream files and the stream access method. The following restrictions for the byte stream model apply:
- WAIT time is not supported by the folder management services on the Lock Data Stream (LCKSTR) command. The user must handle the waiting function on the source server.
- The Copy File (CPYFIL) command used to copy a document on an iSeries server is supported with the restrictions. Only the header information is copied; no data is copied.
- The DELDRCOP (DRCALL) parameter is not supported on the Delete Directory (DELDRC) command.
- Personal computer generic names are not allowed when performing operations on data management objects such as files, libraries, or members. However, generic names are allowed when performing operations on folder management services objects such as documents and folders. Generic names are supported where the personal computer supports the operation and in the manner that the personal computer supports the operation. For example, generic names are not supported for folders using the rename and delete commands because the personal computer does not support them.
Parent topic:
Program modification requirements for DDM
Related reference
Commitment control support for DDM
Data description specifications considerations for DDM
DDM commands and parameters