Re: Another CPYTOIMPF question - Someone please put me out ofmymisery!

Bruce - SI03758 did the trick.  Thanks for the suggestion!  Now I guess I
need to see what other PTF's I may need...

Steve Landess
Austin, Texas
(412) 423-0935

----- Original Message -----
From: "Bruce Vining" <bvining@us.ibm.com>
To: "Midrange Systems Technical Discussion" <midrange-l@midrange.com>
Sent: Friday, January 24, 2003 11:46 AM
Subject: RE: Another CPYTOIMPF question - Someone please put me out of
mymisery!


>
> SI03758 might be the one you're thinking of.  It does fix a problem with
> CPDA09B and QNTC for V5R1 (now whether it's this problem or not...).
>
>
>
>
>                       Joel Fritz
>                       <JFritz@sharperimage        To:       "'Midrange
Systems Technical Discussion'" <midrange-l@midrange.com>
>                       .com>                       cc:
>                       Sent by:                    Subject:  RE: Another
CPYTOIMPF question - Someone please put me out of my
>                       midrange-l-bounces@m         misery!
>                       idrange.com
>
>
>                       01/23/2003 04:28 PM
>                       Please respond to
>                       Midrange Systems
>                       Technical Discussion
>
>
>
>
>
>
> Sorry to be vague, but I think there's a PTF for the CCSID message.  When
> you copy the file to the IFS directory, does the target file already
exist?
> If it was created by the CPYTOIMPF, the command with the parms you showed
> will result in an EBCDIC text file.  If that's the case, you might try
> deleting the IFS file, then use the *PCASCII parm on the CPYTOIMPF, and
> skip
> the code page conversion on the CPY.
>
> > -----Original Message-----
> > From: Steve Landess [mailto:steve_landess@hotmail.com]
> > Sent: Thursday, January 23, 2003 2:00 PM
> > To: midrange-l@midrange.com
> > Subject: Another CPYTOIMPF question - Someone please put me out of my
> > misery!
> >
> >
> > Folks -This is driving me nuts!  I have been playing around
> > with the CPYTOIMPF command, trying to familiarize myself with its use.
> >
> > My AS/400 system is a 170, V5R1M0, TL02134.  The CCSID of the
> > system (QCCSID) is 37.  The CCSID of the CUSMST file is 37.
> > The CCSID of all character fields within CUSMST is 37.
> >
> > I have been trying to use the CPYTOIMPF command to copy the
> > CUSMST file directly to a folder on my W2K server, like this:
> >
> > CPYTOIMPF FROMFILE(SJL001/CUSMST)
> > TOSTMF('/QNTC/w2kserver/w2ksvr/Downloads/BUBBA/CUSMST')
> > STMFCODPAG(*PCASCII) RCDDLM(*CRLF)
> >
> > This fails....
> >
> > Here are the mesages in the job log:
> >
> > Ownership of object QCPEXTEMPS in QTEMP type *USRSPC changed.
> >
> > File QACP007985 created in library QTEMP.
> >
> > Member QACP007985 added to file QACP007985 in QTEMP.
> >
> > Ownership of object QACP007985 in QTEMP type *USRSPC changed.
> >
> > Ownership of object QACEXFLD12 in QTEMP type *USRSPC changed.
> >
> > CCSID conversion could not be performed.
> >
> > No records copied from file CUSMST in SJL001.
> >
> > Object QACP007985 in QTEMP type *FILE deleted.
> >
> > Copy command ended because of error.
> >
> >
> >
> > If I do this:
> >
> > CPYTOIMPF FROMFILE(SJL001/CUSMST) TOSTMF('/SERVERS/CUSMST')
> > MBROPT(*REPLACE)
> > RCDDLM(*CRLF)
> >
> > (where /SERVERS is a folder in the IFS)
> >
> > Then do this:
> >
> > CPY OBJ('/SERVERS/CUSMST')
> > TODIR('/QNTC/w2kserver/w2ksvr/Downloads/BUBBA') FROMCCSID(1252)
> > TOCCSID(*CALC) REPLACE(*YES)
> >
> > It copies the file to the target directory, but when I view
> > it (at least from the AS/400 by browsing it thru the IFS) it
> > looks like garbage...
> >
> > What am I doing wrong?  Can I _not_ copy the file directly
> > from the AS/400 to the Windows folder?
> >
> > I have spent way too much time trying to figure this
> > out...and I have searched both on Google and in Midrange-L,
> > but haven't found any solutions...
> >
> > Steve Landess
> > Austin, Texas
> > (512) 423-0935
> > _______________________________________________
> > 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/mailman/listinfo.cgi/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.
> The contents of this message may contain personal views which are not the
> views of The Sharper Image. 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/mailman/listinfo.cgi/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/mailman/listinfo.cgi/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.
>