|
Hmm... I tried creating an image of the original file using DDS. The file as a whole had a CCSID of 37. I tried copying it and got the same error. I also tried a small production file with CCSID 37 with the same results. Does *PCASCII have something to do with it? > -----Original Message----- > From: Joel Fritz > Sent: Wednesday, July 10, 2002 10:09 AM > To: 'midrange-l@midrange.com' > Subject: RE: cpytoimpf to qntc failing under v5r1 > > > Sorry, there are field level CCSIDS in WEBORDHDR. Some of > the fields are > 65535 and some are 37. Is this a result of the file being > generated by > Query400? Can I fix this by creating DDS and using the replace member > option on the output file? > > > -----Original Message----- > > From: Joel Fritz > > Sent: Wednesday, July 10, 2002 9:32 AM > > To: 'midrange-l@midrange.com' > > Subject: RE: cpytoimpf to qntc failing under v5r1 > > > > > > WEBORDHDR is ccsid 65535. It's created by Query400. I'm not > > sure about > > webordhdr.txt. It's an NT 4.0 text file so it's ASCII or > > ANSI with the out > > of the box US English code page. > > > > Somehow I don't get a warm feeling about CCSID 65535. > > > > > -----Original Message----- > > > From: Bruce Vining [mailto:bvining@us.ibm.com] > > > Sent: Wednesday, July 10, 2002 6:43 AM > > > To: midrange-l@midrange.com > > > Subject: Re: cpytoimpf to qntc failing under v5r1 > > > > > > > > > > > > Joel, > > > > > > What is the CCSID of EPMSTAGE/WEBORDHDR and of webordhdr.txt? > > > > > > > > > > > > > > > > > > Joel Fritz > > > <JFritz@sharperima To: > > > "MIDRANGE-L@midrange. com (E-mail)" <MIDRANGE-L@midrange.com> > > > ge.com> cc: > > > Sent by: Subject: > > > cpytoimpf to qntc failing under v5r1 > > > midrange-l-admin@m > > > idrange.com > > > > > > > > > 07/09/2002 12:25 > > > PM > > > Please respond to > > > midrange-l > > > > > > > > > > > > > > > > > > I'd be real grateful if anyone knows the answer to this one. > > > (I may draw > > > the line at house painting, but...) > > > > > > We have a job that has been doing a cpytoimpf to an NT server > > > set up as a > > > QNTC share. The job was submitted under a user profile that > > > has access to > > > both machines. It worked fine under v4r5. First time out > > > under v5r1 it > > > failed with the following error message: > > > > > > CPDA09B Diagnostic 30 07/08/02 21:22:00 > > > QP0LCCMN > > > QSYS *STMT QC2SYS QSYS *STMT > > > From module . . . . . . . . : > > > QP0LCCMN > > > From procedure . . . . . . : > > > send_STMF_DBF_msg__FPcT1iT1T3PV22qp0l_STMF_DBF > > > _commarea > > > > > > Statement . . . . . . . > > > . . : 1080 > > > > > > To module . . . . . . . > > > . . : QC2SYS > > > > > > To procedure . . . . . > > > . . : system > > > > > > Statement . . . . . . > > . . . : 6 > > > > > > Message . . . . : > > > CCSID conversion > > > could not be performed. > > > Cause . . . . . : The coded > > > character > > > set identifier (CCSID) conversion could not be performed > > > because the input > > > data is not valid or can not be > > > identified by the specified code set. Recovery . . . : Do > > > one or all of > > > the following: -- Change the codepage or CCSID value. -- > > > Change the input > > > data in the file to be valid. Submit the command again. > > > > > > > > > The command string was: > > > > > > > > > CPYTOIMPF FROMFILE(EPMSTAGE/WEBORDHDR) + > > > > > TOSTMF('/qntc/bb-analytics/as400_source/web+ > > > ordhdr.txt') MBROPT(*REPLACE) + > > > RCDDLM(*CRLF) STRDLM('"') FLDDLM(',') + > > > STMFCODPAG(*PCASCII) > > > > > > > > > NOTICE: > > > All e-mail sent to or from this e-mail address will be received or > > > otherwise > > > recorded by The Sharper Image corporate e-mail system and is > > > subject to > > > archival, monitoring, review by and/or disclosure to Sharper > > > Image security > > > and other management. This message is intended only for the > > use of the > > > addressee and may contain information that is privileged and > > > confidential. > > > If you are not the intended recipient, dissemination of this > > > communication > > > is prohibited. > > > > > > _______________________________________________ > > > This is the Midrange Systems Technical Discussion > > > (MIDRANGE-L) mailing list > > > To post a message email: MIDRANGE-L@midrange.com > > > To subscribe, unsubscribe, or change list options, > > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > > > or email: MIDRANGE-L-request@midrange.com > > > 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@midrange.com > > > To subscribe, unsubscribe, or change list options, > > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > > > or email: MIDRANGE-L-request@midrange.com > > > Before posting, please take a moment to review the archives > > > at http://archive.midrange.com/midrange-l. > > > > > NOTICE: > > All e-mail sent to or from this e-mail address will be > > received or otherwise > > recorded by The Sharper Image corporate e-mail system and is > > subject to > > archival, monitoring, review by and/or disclosure to Sharper > > Image security > > and other management. This message is intended only for the > use of the > > addressee and may contain information that is privileged and > > confidential. > > If you are not the intended recipient, dissemination of this > > communication > > is prohibited. > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion > > (MIDRANGE-L) mailing list > > To post a message email: MIDRANGE-L@midrange.com > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > > or email: MIDRANGE-L-request@midrange.com > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > > NOTICE: > All e-mail sent to or from this e-mail address will be > received or otherwise > recorded by The Sharper Image corporate e-mail system and is > subject to > archival, monitoring, review by and/or disclosure to Sharper > Image security > and other management. This message is intended only for the use of the > addressee and may contain information that is privileged and > confidential. > If you are not the intended recipient, dissemination of this > communication > is prohibited. > > _______________________________________________ > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > NOTICE: All e-mail sent to or from this e-mail address will be received or otherwise recorded by The Sharper Image corporate e-mail system and is subject to archival, monitoring, review by and/or disclosure to Sharper Image security and other management. This message is intended only for the use of the addressee and may contain information that is privileged and confidential. If you are not the intended recipient, dissemination of this communication is prohibited.
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.