RE: cpytostmf file layout problem -- MIDRANGE-L

Hmm! Does VI show the break at 132 as well?

I think you could try the CPY command with *TEXT for formatting (that'll convert to ASCII). This is a raw copy, nothing fancy. The only issue comes when there are packed fields, but this does not appear to be the case.

The other option is to use FTP locally from the library to the directory.

Vern

At 11:25 AM 10/25/2004, you wrote:

Thanks Vern,

1. you are correct I get the 132 record length when I do a wrklnk.  I also
get the same file size when I use VI in linux.  Shouldn't VI be the best app
to look at this in.  I always understood that VI was the best because it
ignores any formating.

2.  Basically I would like to see the same format with the 8219 record
length on the Linux Mounted drive that I see in the AS/400 library.  The
flat file has certain fields that end and begin at certain positions for
example claim number may be in position 1-6 then social security number may
be in position 9-18 so on and so forth til we reach record 8219. Each line
is a record. What happens is the file reaches record 132 and goes to the
next line.  I do have a carraige return line feed in the doc at the end of
each record but that does not matter with the crlf end of line function.

3.  I am not to sure about this one can't I just copy the exact same thing I
see on the 400 lib to a 400 dir?  I understand the file is specific to the
app you view it in like if I open it in word it will be formated.

Thanks for your help

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Vernon Hamberg
Sent: Monday, October 25, 2004 11:29 AM
To: Midrange Systems Technical Discussion
Subject: Re: cpytostmf file layout problem


A couple questions/comments -

1. Where are you getting the 132 record length? Can I assume it is when you
take option 5 in WRKLNK? Often you are better off looking at IFS files with
a Windows app like TextPad

2. I'm not sure what you mean by preserving the format - can you say more
about what you expect or hope to see?

3. Remember that IFS stream files are not record-based. You CAN specify a
record-delimiter that is appropriate for Windows or Unix, however, but this
will be honored only in an app on the respective OS.

Thanks
Vern

At 09:41 AM 10/25/2004, you wrote:
>I have a flat file with a record lenghth of 8219 in an AS/400 library
>(MCOLIB) I want to copy to a stream file in the directory /QOpenSys/.  When
>ever I try using the cpytostmf or cpytoimpf I copies the file to the
>directory and then uses a record length of 132 and does not preserve the
>format.  I have tried using default perameters and different ccid's for
>qascii and all that seems to work is a record length of 132.  Please help
>thanks
>
>--
>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.

--
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.