We are running z/OS 1.12 on a z9BC. We have COBOL 3.4. Neither will ever be upgraded. We will not obtain new hardware or software. Given the absolute truth of the preceding :-( does anybody know a better way to convert a CSV file, coming in from a UNIX box, to a "normal" sequential file with fixed length character fields. At present we use the UNSTRING verb to do this. We get these files daily and they are 100s of thousands to a bit over a million records. This takes a while, both wall clock and CPU wise. Oh, these actually use the pipe symbol, | (0x4F) and not a comma, if that is of any relevance. Please don't suggest HLASM because our programming staff (two people) basically knows only two languages: COBOL and CA-EasyTrieve. Yes, we are leaving the z/OS arena. We should have been off of it at the end of last month, but the off-site vendor (CSC) basically said that they couldn't do what our actuarial people need done, so CSC sends us file with we use to load VSAM data sets which the actuarial people then use in their processes. Supposedly, this will only stay around until the actuaries find a different way to do their jobs on Windows effectively. But I'm not in that loop (Personally, I'd look at the R language - free & almost as good as SAS).
-- Unix: Some say the learning curve is steep, but you only have to climb it once. -- Karl Lehenbauer Unicode: http://xkcd.com/1726/ Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
