RE: DDS coding

Ah COBOL....I'm a little rusty and I've never used COBOL on the 400, but
a quick look at the reference manual lead me to believe that the iSeries
doesn't support PIC 9.99 in a externally defined file. 9V99 is supported
but not 9.99.

You might want to look at the CPYTOIMPF and CPYFRMIMPF commands
(depending on if the file is going out or coming in ).

Both of them work with the explicit decimal point in a text file.

So, if outgoing I'd: 
CPYTOIMPF to a stream file in the IFS
FTP the stream file from the IFS

Incoming I'd:
FTP to a stream file from the IFS
CPYFRMIMPF from the stream file in the IFS


HTH,

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of 
> msmith6@xxxxxxxxxxxx
> Sent: Wednesday, December 21, 2005 4:01 PM
> To: midrange-l@xxxxxxxxxxxx
> Subject: RE: DDS coding
> 
> subject: RE: DDS coding
> Ed wrote:
> "  Does Field1 need to be numeric?
>    I do not think you can put a '.' in a decimal field.
> 
>    If not try this
>    FIELD1    4A
>    Eval   Field1 = %char(1.21) "
>  
> This file is going to be FTP to a business partner.  They have the 
> first field of Numeric, Length of 4 for the first field.
> 
> Charles wrote:
> "  Why do you think you need to '.' in the file?
>    The only way to actually get it there is to make the field 
> character.
>    Of course, then you be able to stick all kinds of crap in."
> 
> Yeah, I know, but if the COBOL program always rights that then it 
> should be ok.  I was just looking for the MVS COBOL equivalent of 
> FIELD   PIC 9.99
> 
> 
> 
> -- 
> 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.
> 
>