|
Buck wrote:
3. Re: Debug in WDSC (Buck) date: Fri, 27 Oct 2006 10:22:43 -0400(I used to write ReXX macros under MVS and never understood whymidrange systems couldn't do that.)Okay, I gotta ask... Why can't SEU do that? I.e., what "macros" would you like in SEU that can't be done with ReXX? (Not that anyone would _want_ to.)Here's an example I wanted to use yesterday. I'm fiddling with a CPYFRMIMPF, and I have DDS that has numeric fields in it. That DDS also specifies EDTCDE(whatever). For my tinkering purposes, I need another version of that file's DDS where every field is character. I can pretty easily change out all the spots that say '5p 0' or '10s 0', making them '5a ' and '10a ', but I can't readily delete the lines that say EDTCDE(whatever). I say 'pretty easily' although it takes several passes to change P to A and S to A, restricting by column and remembering to hide comment lines <g>. A ReXX macro does all of that in one pass. Now, as the 'real' DDS changes (new fields, different sizes and such), I run my macro over itto translate it into the version that's character-only.
Buck,Since this is the WDSC list, discussion of how to do this in SEU is better in Midrange_L. But because it started with an idea like "WDSC can do it but SEU can't", I have to say at least that I don't see why this can't be implemented as a user-defined line command in SEU. (Maybe semantically that means it's not a 'macro'?)
And I'm not at all sure that learning how to do it in WDSC is easier than learning the SEU technique. If one or two 'good' ways to do it in WDSC were posted, I think it would be very interesting to see them compared to an SEU solution. If nothing else, it could show green-screen developers a clearly mapped transition from one to the other. WDSC is clearly the future and transition should be addressed.
Of course, I might still not be understanding the problem. Tom Liotta
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.