× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



No the file is 800000 records,  too large for excel
 
I might have to try copying and pasting several records at a time into a
new .txt field and then go through excel.   Excel is how I did other
.txt files but this one is too large.


Angela Wawrzaszek
IT Supervisor
awawrzaszek@xxxxxxxxxxxxxxx
(315) 258-4205

-----Original Message-----
From: michael@xxxxxxxxxxxxxxxxxx [mailto:michael@xxxxxxxxxxxxxxxxxx] 
Sent: Wednesday, February 09, 2005 1:24 PM
To: Midrange Systems Technical Discussion
Subject: RE: Restoring a .txt file

I'll bet you could bring it into Excel (using Excel's layout tool thing)
and then upload it to the iSeries.

> -------- Original Message --------
> Subject: RE: Restoring a .txt file
> From: "Angela Wawrzaszek" <awawrzaszek@xxxxxxxxxxxxxxx>
> Date: Wed, February 09, 2005 1:06 pm
> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> 
> Doing that though how do I convert the character representations of
the
> numbers to actual numbers?   Do I have to parse out each position
> looking for numbers,  decimals and blanks?
> 
> 
> Ie.  Of how .txt file looks once copied to a flat file:
> 
> LI361505085      AS          EE11  17.000       .000        .000
> .000         20021007    0                           
>                                                                      
>                                                                      
> Actual specs of 'real' file are
> 
> ID       2    A  
> Item#    5    A
> Lot#    10    A ( blank on many of the records)
> Loc      6    A
> OpenBal  11 3 P
> Issue    11 3 P
> Receipts 11 3 P
> Adjust   11 3 P
> Date      8 0 P
> Extra     1   A 
> 
>                                                                       
> 
> Angela Wawrzaszek
> IT Supervisor
> awawrzaszek@xxxxxxxxxxxxxxx
> (315) 258-4205
> 
> -----Original Message-----
> From: Booth Martin [mailto:booth@xxxxxxxxxxxx] 
> Sent: Wednesday, February 09, 2005 12:52 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: Restoring a .txt file
> 
> Have you considered defining the text file as a program-described
file,
> and
> defining the fields in the I-specs of a small RPG program? 
> 
>  
> 
> ---------------------------------
> 
> Booth Martin
> 
> http://www.martinvt.com
> 
> ---------------------------------
> 
> -------Original Message-------
> 
>  
> 
> From: Midrange Systems Technical Discussion
> 
> Date: 02/09/05 11:41:28
> 
> To: Midrange Systems Technical Discussion
> 
> Subject: Restoring a .txt file
> 
>  
> 
>    Help!
> 
>  
> 
>  
> 
>  
> 
>     I have a .txt file that was saved from an as/400 inventory file.
It
> 
> was saved as a fixed format file.   I now want to bring that .txt file
> 
> back to the as400 to run queries on it.   However since it was fixed
> 
> there is not comma delimiters etc.   So I copied it back to a flat
file
> 
> on the as400 and then tried using the cpyfrmimpf command to copy it
back
> 
> into its regular format.   The problem occurs because there is numeric
> 
> data in the file.  Therefore the copy crashes because I am trying to
> 
> copy  17.00  - which is beign treated as a character field to a
numberic
> 
> field.
> 
>  
> 
>  
> 
>  
> 
> The command used to copy the data to the .txt file was:
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
> CPYTOIMPF  FROMFILE(Mylib/MyFile) +
> 
>  
> 
>              TOSTMF('home/yearend/yearend2004/MyFile.t +
> 
>  
> 
>              xt') MBROPT(*REPLACE) +
> 
>  
> 
>              STMFCODPAG(*PCASCII) RCDDLM(*CRLF) +
> 
>  
> 
>              DTAFMT(*FIXED) STRDLM(*NONE)
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
> Can anyone help me to restore this to its original data formats?
> 
>  
> 
>  
> 
>  
> 
> Thanks!
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
> Angela Wawrzaszek
> 
>  
> 
> IT Supervisor
> 
>  
> 
> awawrzaszek@xxxxxxxxxxxxxxx
> 
>  
> 
> (315) 258-4205
> 
>  
> 
>  
> 
>  
> 
> --
> 
> 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.

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





As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.