Invalid file reference mainframe

User tried to update an empty file. The TO value on a DO statement is non-numeric. The BY value on a DO statement is non-numeric. The name of a procedure is used as a variable. A positional specification on the PROC statement was invalid. Invalid characters were found in a symbolic parameter on the PROC statement. A symbolic parameter name on the PROC statement is too long. The number of positional parameters defined on the PROC statement is fewer than the number passed.

No symbolic parameters were defined on the PROC statement. Duplicate parameter names were found on the PROC statement.

A keyword parameter has an invalid default value. A default keyword value was missing an ending quote on the PROC statement. A character between DBCS delimiters was outside the range of double-byte characters. A DBCS string contains an odd number of bytes, indicating that one of the characters is incomplete. A beginning DBCS delimiter was found without a corresponding ending delimiter. Two beginning DBCS delimiters were found without an intervening ending delimiter. An error occurred in an installation exit.

Data was found where operator was expected. Easytrieve Plus does an "automatic cycle". Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Easytrieve A invalid file reference Ask Question. Asked 8 years, 4 months ago. Active 8 years, 2 months ago.

Viewed 6k times. I am getting the error in this line of my easytrieve prog.. I have a DLBL like this.. Advanced search. If you don't test, then you'll get the Invalid File Reference if the record is not there.

It is one for the first record on the file and, if there are no more records on that file, it stays one. If there are more records but FILE2 has a lower key, again the record-count is one, and again you'll get the A Select all. The downstream job might not like an empty file, but what does it do with a record picked at random?