RE: Question on Cobol (Unix) file layouts...

Cobol PIC 9 (5) V99 is 99999.99 and it's not packed (thank god).
In DDS you have to define it as 7,2.

What you may be experiencing in conversion is the sign byte.

PIC 9(5)V99 doesn't have the sign byte.  That would be PIC S9(5)V99 so
Excel, etc. may be messing you up there.

If you can't get it to work straight in you may have to create an
intermediate file where the fields are defined as PIC X(7).  Then use a
COBOL redefines to define the field as PIC 9(5)v99.

Let me know if you need more.  We use COBOL so I'm sure I can find an
example somewhere.

Ed Tate (etate01@sun.hazelwood.k12.mo.us)
Coordinator of Technology
Hazelwood School District
15955 New Halls Ferry
Florissant, MO  63031
314-953-5090



> -----Original Message-----
> From: owner-midrange-l@midrange.com
> [mailto:owner-midrange-l@midrange.com]On Behalf Of Chuck Lewis
> Sent: Thursday, February 18, 1999 7:07 AM
> To: MIDRANGE-L@midrange.com
> Subject: Question on Cobol (Unix) file layouts...
> Importance: High
>
>
> Hi Folks !
>
> You might not be able to help with this but if ANYONE that has worked
> with ALL kinds of different systems and languages can suffer through
> this, I'd appreciate it !
>
> I have yet another project to get data from our old (and now retired)
> NCR Unix box over to our AS/400 (it is Sales History information). My
> cohort who is the person responsible for the NCR/Unix box and it's
> homegrown apps, had given me what I GUESS you would call file layouts. I
> TRIED to explain to him what I needed ("look at a PF on the AS/400 as a
> reference and then give me the NCR 'file layout' in a similar layout so
> I don't have to do it").
>
> What I got was, again, the NCR "file layout" with a bunch of explanatory
> post-it notes.
>
> As an example:
> FD
> CNVHDR
> Post-it Note translation
>         LABEL RECORDS ARE STANDARD.
> 01    CNVH-REC.
>         03    CNVH-KEY.
>                 05    CNVH-ORDERNUM                      PIC    9 (6)
> .                   6 numeric
>                 05    CNVH-SEQUENCE                        PIC    9
> .                        1 numeric
>                 05    CNVH-ORDERLINENUM              PIC    999
> .                    3 numeric
>         03    CNVH-DATA
>                 05    CNVH-SYSDATE                            PIC    9
> (6) .                  6 numeric
>                 05    CNVH-BATCH-WSE                      PIC    XX
> .                    2 alpha
>                 05    CNVH-BATCH-BCHSEQ               PIC    9
> .                       1 numeric
>                 05    CNVH-SHIPPEDDATE                   PIC    9 (6)
> .                  6 numeric
>                 05    CNVH-INVOICEDATE                   PIC    9 (6)
> .                  6 numeric
>                 05    CNVH-EXTDSALESTAX                PIC    9 (5) V99
> .          5 numeric with 2 deciimals
>                 05    CNVH-EXTFTOTALORDER           PIC    9 (5) V99
> .          5 numeric with 2 decimals
>
> I am converting this ASCII file through Excel into a CSV file and then
> uploading it.
>
> So I define:
>                     ORDERNUM as numeric 6,0
>                     SQEUENCE as numeric 1,0
>                     ORDERLINENUM as numeric 3,0
>                     SYSDAT as numeric 6,0
>                     BATCH-WSE as 2A
>                     BATCH-BCHSEQ as numeric 1,0
>                     SHIPPEDDATE as numeric 6,0
>                     INVOICEDATE as numeric 6,0
>                     EXTDSALESTAX as numeric 7,2
>                     EXTFTOTALORDER as numeric 7,2
>
> Note the only differences are the last 2. I TRIED making them 5 with 2
> but when I bring it up in Excel to do the "mask" they are CLEARY 7 in
> length and if I do the transfer to the AS/400 it works.
>
> My question is, how do YOU interpret the last 2 fields from Unix/Cobol
> (?) to the AS/400 PF field designation ?
>
> Sorry to bug the list with this if you don't know. My thought was this
> MAY be an internal Cobol file layout that someone would be familiar with
> (I am SURE not and my cohort is not real helpful...)
>
> Thanks !
>
> Chuck
>
>
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---