It appears that the field always begins in column 165? 

In a case like that my preferred solution would be to define the flat 
file's record as one long field, say, "FullRecord" and also define a 
datastructure named "FullRecordDS" where the field CONQTY is defined in 
the datastructure at column 165.  Then, when needed in the Calcs, "     C  
    MOVE FullRecord      FullRecordDS"   That'd do all the data moves for 
you.  There are several trivial refinements for that solution. 

Toward your solution I'd  offer this:  Don't you have to substring a 
field, not a file?

Booth Martin

"connie amerine" <>
Sent by:
11/16/1999 08:13 AM
Please respond to MIDRANGE-L

        To:     <>
        Subject:        Fw: text files

-----Original Message-----
From: connie amerine <>
To: <>
Date: Monday, November 15, 1999 3:35 PM
Subject: Fw: text files

-----Original Message-----
From: connie amerine <>
To: <>
Date: Monday, November 15, 1999 3:12 PM
Subject: text files

Our customer downloads a monthly order on a NT work station to us, I then 
FTP it to the AS/400. Once is it on the AS/400 as a flat file, I am 
attemping to use the file by using substring command to put some of the 
data into a sorted file. Once I use the substring and move the data into 
the physical file, it should be there, but.....I m getting the message 
that the field or indicater is not defined. 
5            SUBST<FILENAME>:165CONQTY    5
              MOVE CONQTY    CTYQTY
The code looks similiar to that...can anyone help?
Thanks in advance

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to
| To subscribe to this list send email to
| To unsubscribe from this list send email to
| Questions should be directed to the list owner/operator:

This thread ...

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

This mailing list archive is Copyright 1997-2020 by 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].