Frank, We chose to specify NOPFD. Our programmers do not select compile options for themselves, so we had to choose the option for them that would not cause them any execution problems, even if it produces less efficient code.
Regards, Greg Shirey Ben E. Keith Company -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Frank Swarbrick Sent: Wednesday, September 24, 2014 7:06 PM To: [email protected] Subject: COBOL NUMPROC compile option <snip> Should we risk it? Has anyone out there ever "migrated" to PFD with "legacy" data files? I'm quite certain that we do have at least some cases where one program wrote out data defined as signed and other programs read it with the same area defined as unsigned. Curse it, but I know I've seen it. I think the less likely, but not impossible, situation would be testing it for numeric. Mostly we only test for numeric if: - We sometimes intentionally store non-numeric (usually low-values; maybe spaces sometimes) data in a numeric field in some situations - We're getting data from an external source and want to validate it (though I imagine we do this far less than we perhaps should!). ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
