Ron, Your application people MUST first add checks in their program(s) for valid numeric data (ALWAYS do this when reading data supplied by outside vendors and customers; trust but verify is the golden rule) and automatically skip those records. Another good practice for "bad data" records is to reject them to another output file and write a reject report program to list out the "bad data" records for the vendor or client to correct the next day.
If your application code cannot skip bad data records (or supply a default value for the bad numeric data, frequently zero), being able to "automatically" skip the records already processed will not help -- the program will just abend again on the same record that caused the abend in the first place. It is in general quite hard (i.e., requires some manual effort) to skip up to and then bypass a "bad data" record. Once the application code is set up to handle any bad data records, the "checkpoint/restart" facilities which are built-in to z/OS can help you "automatically" restart an abended job at the point it was abended, but there is some additional setup you have to do. HTH Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Ron Thomas Sent: Thursday, August 02, 2012 2:05 PM To: [email protected] Subject: Re: File Processing The current abend is SOC7 & module needs to run in production. The input file is comming from a third party vendor and some reason the data isn the file is corrupted, the program might get abended. We need a process to work in production so that once restarted from the same step the program should be skipping all the of the records it already processed . Thanks, Ron T ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
