|
Changing QCCSID from 65535 to a non-65535 value can have impacts to a system depending on how applications/databases on the system are set up. As an example, since most jobs on the system grab their job CCSID from this system value you may have inadvertently turned on CCSID conversion processing when accessing your database files (which may cause problems if you're really trying to treat the FTP data as hex but don't have it tagged as such though this is just a guess). Making this type of change usually takes some upfront analysis of your system. Bruce Jeff Crosby <jlcrosby@xxxxxxxxxx To: Midrange Mailing List <MIDRANGE-L@xxxxxxxxxxxx> ds.com> cc: Sent by: Subject: Can CCSID cause this? midrange-l-bounces@x idrange.com 05/16/2003 11:24 AM Please respond to Midrange Systems Technical Discussion Yesterday I downloaded the CGIDEV2 from IBM and installed it this morning. As part of the install it said the system value QCCSID could not be 65535 or it wouldn't work. The README said "No impact to existing production." Ours was 65535 so I changed it to 37 and restarted the HTTP server per the instructions. (We have no web site.) About that same time orders that are transmitted from our salespeople stopped being processed properly. What is supposed to happen is the order is FTPed from a W2K Server PC to the iSeries, a REXEC is fired off to process the order, and the results are FTPed back to the W2K Server. What actually happened is the order would be FTPed to the iSeries and not processed. It's as if the REXEC was never fired. But the job _must_ have been fired because there are begin/end entries in the system log, but no job log. And I could fire them off manually at the command line and they would be processed. Finally I just ended the HTTP server, changed the CCSID back to 65535, and rebooted the W2K Server. After that, now all is well. Could my changing the CCSID have caused this? It sure seems like more than coincidence, but I need smarter brains than mine to figure it out. I will be out this afternoon, but checking email throughout the weekend. Thanks. -- Jeff Crosby Dilgard Frozen Foods, Inc. P.O. Box 13369 Ft. Wayne, IN 46868-3369 260-422-7531 The opinions expressed are my own and not necessarily the opinion of my company. Unless I say so. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.