You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some codepages contain characters that cannot be represented in Extended ASCII and are stored in EBCDIC on the mainframe (such as datasets in codepage 939). With the current implementation, it is not possible to download a dataset to a local machine over FTP and have it appear with special (Japanese) characters. However, z/OS FTP supports sending these files by first converting them into UCS-2 using TYPE U 2 and SITE UCSHOSTCS=(codepage). It would be nice to have similar functionality in zos-node-accessor.
The text was updated successfully, but these errors were encountered:
The site() method is provided in zos-node-accessor, allowing you to send any site parameters. The downloadDataset() in master and getDataset() in 1.0.x accept site parameters as well.
Let us know please, if the above cannot work in your scenario. Thanks!
Some codepages contain characters that cannot be represented in Extended ASCII and are stored in EBCDIC on the mainframe (such as datasets in codepage 939). With the current implementation, it is not possible to download a dataset to a local machine over FTP and have it appear with special (Japanese) characters. However, z/OS FTP supports sending these files by first converting them into UCS-2 using
TYPE U 2
andSITE UCSHOSTCS=(codepage)
. It would be nice to have similar functionality in zos-node-accessor.The text was updated successfully, but these errors were encountered: