Check for empty input file in jcl

If you get EOF you abend. If not, validate the date. If invalid abend. Read the file again. If not EOF, abend. Close the file.

If you need to do this with date from one file or another, just set an indicator for the EOF abend. Do the same processing for the second file different indicator and abend if either is set. But beware Steve's caution. The problem I have is that people can explain things quickly but I can only comprehend slowly. Regards Nic. I don't like datasets which can't have their contents verified.

Header record with logical file name, logical date for the data. Data records, which can be sequence-checked if they should be in sequence. Here is a sample Sort job that will not modify an existing data set, but will create it if it does not yet exist: Select all.

Perhaps there is another way using SyncSort to check if File A exists. I am writing code under one system that reads a file from another system. I do not have authority to write a file that does not exist from the other system. Now, when my program executes, I receive a file attribute mismatch error.

How would I change the record length from 80 to of a file that does not exist? I posted this here because Robert Sample had replied with this solution, however, I realize this is no longer a SyncSort issue. I will post this to a different forum, if necessary, however, I welcome a SyncSort solution as well! Again, I appreciate your time. That way I could inform the end user which scenario actually occurred. Here, we have prepared the important JCL Interview Questions and Answers, which will help you succeed in your interview.

These interview questions are divided into two parts are as follows:. Please note, those are overridden, not overwritten. Please find below code snippet which defines references of multiple version of GDG:. Return code 4 of any kind of JCL job can be considered an empty file choosing as input for the job.

Normally, the developer manages the same in a different way; if the return code came as 4, then the job is automatically terminated, not required to process further for the next executable logic. As an empty file is normally not required to process further as it will take minimum space in the mainframe system, it is well aware that mainframe system cost is too high, so handling this kind of error will require expertness for any mainframe or JCL job developer.

Below three approaches can communicate it:. After sending the required data to the Cobol program, every JCL job is waiting to return a response from that program and decide the JOB further process.