RE: Authority on IFS files created with CPYTOIMPF

OK, that solved the authority issue.

Now the QMSF job claims it can't parse the data.
Something about the CRLF characters.

When I look at the IFS file in Hex, and compare it to the one CPYTOPCD
makes, it seems the CPYTOIMPF version was using the EBCDID "25" for the
line feed, whereas the CPYTOPCD version used the ASCII "0A".  

So I changed the stream file code page parameter to *PCASCII.
Now my CRLF is a proper "0D0A" like it should be, but the difference I
see now is that the PCD version seems to put its CRLF right at the end
of my text, whereas the IMPF version puts in a whole string of spaces
first (hex "20"), to fill up the record.  

My guess is that this is what's making the QMSF job gag and retch.  

Any ideas what how to keep the spaces out of there?  I also tried
*STDASCII, with the same result.  

Thanks Again

Greg

>-----Original Message-----
>From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
>bounces@xxxxxxxxxxxx] On Behalf Of Chris Bipes
>Sent: Thursday, November 17, 2005 10:56 AM
>To: Midrange Systems Technical Discussion
>Subject: RE: Authority on IFS files created with CPYTOIMPF
>
>Right after you create it, execute CHGAUT command. Not what you are
>looking for, but the only way I have found.
>
>
>Chris Bipes
>Information Services Director
>CrossCheck, Inc.
>
>-----Original Message-----
>From: midrange-l-bounces@xxxxxxxxxxxx
>[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Fleming, Greg
(ED)
>Sent: Thursday, November 17, 2005 7:49 AM
>To: midrange-L@xxxxxxxxxxxx
>Subject: Authority on IFS files created with CPYTOIMPF
>
>When I use CPYTOIMPF to copy a file to the IFS, it sets the Public
>authority to *None.
>
>
>When I use CPYTOPCD it defaults to *RWX, which is what I want, but I'm
>trying to get away from CYPTOPCD, as I understand it is an Office Vison
>command, which is or will soon not be supported, and might just
>disappear in some future OS400 release.
>
>Is there a way to set the authority on the output file using CPYTOIMPF
?
>
>--
>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.