Message - 0P26

Nov 28, 2018


Cause: The specified seek address is invalid for this device type, or
A file has been opened and closed, and an attempt has been made to execute an I/O
operation. or
The problem program has been canceled in response to message 4440A, the AB routine has
been entered, and an attempt has been made to write on an unexpired file. This write opera-
tion is normally a file mark generated by the close routine. To protect the unexpired file, this is
not written and, therefore, the file is not closed.
Programmer Action: Check the LISTIO output to ensure that the proper device was assigned.
If the device assignment is correct, obtain a system dump at the time of the failure and check
the device type accessed. Also, check the access routines for overlay in real storage, invalid
upper and lower limits on the DASD seek routine, or invalid seek address generation, or
Check the close routine for additional I/O operations after CLOSE is issued, or
Use the LVTOC output to check that the correct extents were given. The file opened by your
program has not been closed. The file has no EOF mark and should be rebuilt with larger
Make the necessary corrections and resubmit the job.
If the problem recurs. have
· job stream
· log sheet
· program listing
· system dump
· printer output
available for problem determination.
Operator Action: See Figure 4 at the beginning of this section. Then, execute LISTIO and
check that the proper device type has been assigned (for example, if a 3330 is called for, that
a 3330 was assigned and not a 2314). If this is not the problem, execute LVTOC for the
indicated file, and return the LVTOC and LISTIO output to your programmer.

Used with Courtesy and Permission of International Business Machines, Inc.

Contact Us
This Site's Privacy Policy
Google's privacy policies