> One of my clients has procs like this: > > HRUN BP SOP1500 > STON > HORDER< > HCUSTOMER< > HPRODUCT< > HVENDOR< > P > > whereby the program (BP SOP1500) has the corresponding INPUT statements for > the file names and opens them as F1, F2, F3 which is a real bear when > reading the code.
Wow - that's just plan mean! There may have been a thought that it was a way to avoid hard-coding file names in case they ever changed (though that would be a weak argument), but then they're hard-coded in the PROC, so I can't see any benefit at all, other than obfuscation. The person that created it must have had a future grudge against whoever came along to maintain the code. "Take my job from me, did you? I'll teach you a lesson." :-) Tim Snyder Consulting I/T Specialist U2 Lab Services Information Management, IBM Software Group ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
