RE: Cobol Data conversion using Perl

2002-02-13 Thread Moulder, Glen
eira, Jude (Jude)** CTR ** [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 13, 2002 10:41 AM > To: 'Tillman, James'; '[EMAIL PROTECTED]' > Subject: RE: Cobol Data conversion using Perl > > > I should have given more information in my earlier email. >

Re: Cobol Data conversion using Perl

2002-02-13 Thread Dirk Bremer
Steve, How funny you should mention that, I come from a COBOL background and find printf to be difficult to use compared to an edited PIC clause. In fact, maybe that's an idea for a module... Dirk Bremer - Systems Programmer II - ESS/AMS - NISC St. Peters 636-922-9158 ext. 652 fax 636-447-4471

RE: Cobol Data conversion using Perl

2002-02-13 Thread shurst
"'Tillman, James'" <[EMAIL PROTECTED]>, "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> cc: Subject:RE: Cobol Data conversion using Perl I should have given more information in my earlier email. Sorry about that. H

Re: Cobol Data conversion using Perl

2002-02-13 Thread Dirk Bremer
illman, James'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, February 13, 2002 09:40 Subject: RE: Cobol Data conversion using Perl > I should have given more information in my earlier email. > Sorry about that. > > Here is the structure

RE: Cobol Data conversion using Perl

2002-02-13 Thread Thomas R Wyant_III
Ah-Hah! It's all characters. "PIC XX" means a two-byte field, "PIC X(70)" means a 70-byte field. All you need is something like ($l_name, $f_name, $id1_num ...) = unpack 'A35A30A10...' where the elipsis ("...") means "you fill in the rest." Now figuring out what file to read and how to read