|
Yes, I've been IS Manager at this company for 15 years. We've gone from proprietary NCR minicomputers to NCR Unix systems to a combination of AS/400 and NT servers (all at my direction). Until the AS/400, we were diehard supporters of Cobol and Unix. We all absolutely love the AS/400. Previously, I always thought of people/companies using the AS/400 as boring, unimaginative sheep that followed IBM's direction (whatever that might be). Now, I feel the AS/400 is the best combination of solid integration, performance and reliability that you can only get with a single company producing both the hardware and O/S and yet the system is in my opinion more open than the Unix system it replaced. Unix <> Unix (meaning if you are not on the right "flavor" you can't run software just because it is available on Unix). I have to admit that some of the AS/400 hardware components seem pricey, but right now I wouldn't bet our enterprise applications on any other server! > -----Original Message----- > From: Chuck Lewis [SMTP:CLEWIS@IQUEST.NET] > Sent: Wednesday, February 24, 1999 11:54 AM > To: MIDRANGE-L@midrange.com > Subject: Re: Question on Cobol (Unix) file layouts... > > Thanks Dan ! > > Nice to know that someone ELSE has been down this road ! :-) > > We you on the NCR staff before the switch ? Everyone happy with the AS/400 > now ? > > Chuck > > Dan Thomas wrote: > > > In (any) Cobol PIC 9(5)V99 is a seven byte field. I believe you handled > > this correctly. And yes, these file layouts are "internal" compared to > > AS/400 DB2 files. We converted from a NCR Unix RM/Cobol to AS/400 RPG > > (JBA). We created ASCII flat files and copied them from Unix to our PC > and > > then from PC to AS/400 using Client Access. We probably could have > FTP'd > > from Unix to AS/400 but this approach did work well for us. Feel free > to > > e-mail me if you need further assistance. > > > > > -----Original Message----- > > > From: Chuck Lewis [SMTP:CLEWIS@IQUEST.NET] > > > Sent: Thursday, February 18, 1999 8: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 > > +--- > > +--- > | 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 +---
As an Amazon Associate we earn from qualifying purchases.
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.