Basically, the feature delivered with PR: Set CCSID of deployed files to 1208 if needed #2015 causes the CCSID of every file in the deployment path (including subdirectories) to be changed to 1208.
I have a use case where some files in the deploy hierarchy must maintain specific CCSIDs.
Describe the solution you'd like
I would like to have a new connection-based configuration option that toggles the automatic CCSID manipulation.
Describe alternatives you've considered
Restructure legacy project to avoid issues (not possible)
Is your feature request related to a problem? Please describe. This request is related to an issue I encountered and reported in: All files in stream file deployment path blindly set to CCSID 1208 after deploy #2126.
Basically, the feature delivered with PR: Set CCSID of deployed files to 1208 if needed #2015 causes the CCSID of every file in the deployment path (including subdirectories) to be changed to 1208. I have a use case where some files in the deploy hierarchy must maintain specific CCSIDs.
Describe the solution you'd like I would like to have a new connection-based configuration option that toggles the automatic CCSID manipulation.
Describe alternatives you've considered
Additional context Steps to reproduce the issue are provided in the original issue: All files in stream file deployment path blindly set to CCSID 1208 after deploy #2126