|
I may be speaking out of turn here, but isnt 65535 the ccsid for windows? I am thinking it is because we are doing some XML through IFS (if that is the right term) to a Windows file with an embedded pdf and we needed to put ccsid of 65535 (and back to 37 for other program parts) in some of the coding. --- rob@xxxxxxxxx wrote: > We did a CHGSYSVAL QCCSID and changed ours to 37. > Actually I did that > midday on a busy 570 and really didn't notice any > negative ramifications. > Sure cleaned up a lot of stuff. Does IBM even ship > new systems with > QCCSID set to 65535 anymore? > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com > > > > > > "Burns, Bryan" <burnsbm@xxxxxxxxxxxxxxxxxxxx> > Sent by: midrange-l-bounces@xxxxxxxxxxxx > 09/15/2005 11:30 AM > Please respond to > Midrange Systems Technical Discussion > <midrange-l@xxxxxxxxxxxx> > > > To > Midrange Systems Technical Discussion > <midrange-l@xxxxxxxxxxxx> > cc > > Subject > RE: Cleanup IFS? > > > > > > > Rob, > > Thanks for informing me about RTVDIRINF and > PRTDIRINF. However, when I try > RTVDIRINF I get the message "Job CCSID is 65535." > It's followed by "Error > occurred retrieving directory information." > > Any suggestions? > > Bryan Burns > ECHO, Inc. > > -----Original Message----- > From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx] > Sent: Thursday, September 15, 2005 11:17 AM > To: Midrange Systems Technical Discussion > Subject: Re: Cleanup IFS? > > > For more traditional stuff there is RTVDSKINF and > PRTDSKINF. Starting > with PRTDSKINF *SYS. > > In V5R3 they've added RTVDIRINF and PRTDIRINF for > IFS stuff. Now, there > are some serious issues with these two new commands. > Most of my boxes are > > cool with them, but one takes literally DAYS to run > when most other jobs > are faster than greased lightning. > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com > > > > -- > 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. > > > -- > 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-2024 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.