Hey everyone! I'm pretty new to this and still learning as an apprentice. My current task involves figuring out how to create a more user-friendly interface using JD Edwards (JDE) on the AS400/IBM i system. I've managed to connect to the JDE database via ODBC using Linux, and I'm running some PHP scripts for testing.
I need some help with my findings so far:
- Some string fields return readable values while others come back as unreadable characters like '@@@' or appear empty. After looking into it, it seems fields with CCSID 65535 aren't converting well.
- I'm unsure if it's normal for some columns to be unreadable, and whether it's due to binary formats, or incorrectly defined text fields. Is there a way to convert these CCSID 65535 fields to text?
- I'm also curious about best practices for handling CCSID 65535 on the database side. Should I correct these columns or is it better to leave them as binary?
- Lastly, any thoughts on how to structure the ODBC settings and whether I can force conversions without breaking anything would be great.
I appreciate any advice, experience, or best practices regarding JDE, AS400, CCSID, and ODBC on Linux! Thanks!
3 Answers
I came across some similar issues with CCSID 65535. You might want to check the schema definition to see how your fields are set up. Often, those fields won't directly convert without some backend support. And just a heads up: fixing CCSIDs on the AS400 side can be complicated but is essential. Look into identifying critical text columns that need proper CCSIDs first, then address the rest.
It sounds like you're on the right track! For ODBC, consider adding `DateFormat=5; TranslateBinary=1; ConvertCCSID65535=1` to your config. Those settings can help with decoding readable text fields during queries. Just remember that the `@@@` output likely indicates packed or zoned decimals, which means those fields are not just text. You might need to do some manual decoding for those extra tricky fields.
From what I know about JDE, the output you're getting can happen if the data was stored as non-text or binary in the database. You may want to document what you've found so far in case it helps others with similar issues. For a modern web app later, make sure you fix the essential text fields to proper CCSIDs and handle packed/zoned fields manually in your PHP app.
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically