Bryan Dietz wrote:
here is a simple CL
Thanks for that ... I tried it, but it didn't help solve my problem.
Let me try a different tact ...
I've got a job that needs to manage CCSID's on files. Even though it's
running in CCSID 5035, it needs to switch to CCSID 5026 to perform
various file operations.
In the job log I see the job starts out with CCSID 5035, switches to
5026, back to 5035, and repeats the switch two more times. The last
chgjob command I see logged is 'CHGJOB CCSID(5035)'.
Problem is, the job ends up in CCSID 5026... and I can't see where it
switched to 5026.
I've tried tracing the job, but couldn't make heads or tails of what was
happening.
Any suggestions?
Thanks!
david
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.