IFS STMF with ccsid 37 #480
Replies: 2 comments 8 replies
-
@ToshBimbra Good point. In general, VS Code only supports UTF-x, so any source other than UTF-x would need to be converted to UTF-8. We don't currently look at the source ccsid and convert as needed for streamfiles. We already do this for source members as you probably know. I am curious: what is your use case with streamfiles in 37 instead of 1208? @ThePrez what's the status of |
Beta Was this translation helpful? Give feedback.
-
@worksofliam do you just need an SQL Function that retrieves the CCSID for IFS files? I have one I can donate. But I suppose the bigger issue is reading code from the IFS in native CCSID, and converting it to UTF-8 and then reversing the process back. IBM SQL Table functions can automatically convert to the job CCSID or to a specific CCSID, such as 1208. They do now provide an IFS_READ interface (like I didn't in SQL Tools for a while) but saving it back in the target file's CCSID might require some C/++ code on the IBM i side of things. (I assume you're using SQL to get/put the data from the IBM i.) |
Beta Was this translation helpful? Give feedback.
-
Since there is no visual indicator shown in IFS explorer to indicate if a stmf has ccsid 37 or not then it is frustrating to open the stmf and find the stmf opens with illegible chars.
Not sure if this topic has been brought up before or not.
Any comments or thoughts about my post?
Thx. Tosh.
Beta Was this translation helpful? Give feedback.
All reactions