RE: cpytoimpf to qntc failing under v5r1

[Joel Fritz <JFritz@xxxxxxxxxxxxxxxx>]

Thanks.  Not the answer I was hoping for. <g> Sounds like a bug to me.

We're also having problems with runrmtcmd.

> -----Original Message-----
> From: Patrick Townsend [mailto:patownsend@patownsend.com]
> Sent: Tuesday, July 09, 2002 11:00 PM
> To: midrange-l@midrange.com
> Subject: Re: cpytoimpf to qntc failing under v5r1
>
>
> We found that CPYFRMSTMF has a similar problem on V5 that we did not
> encounter on V4. We solved it by using a table instead of the *PCASCII
> option. CPYTOIMPF doesn't have the table option, but maybe
> you can get it
> into the format you want and then use CPYTOSTMF?
>
> Patrick
> ----- Original Message -----
> From: "Joel Fritz" <JFritz@sharperimage.com>
> To: "MIDRANGE-L@midrange. com (E-mail)" <MIDRANGE-L@midrange.com>
> Sent: Tuesday, July 09, 2002 10:25 AM
> Subject: cpytoimpf to qntc failing under v5r1
>
>
> > 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:
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.