Re: IOSTAT=127

nmm1@xxxxxxxxx writes:

Well, you are missing quite a lot. Firstly, because of the way that
I/O is buffered and Unix works, you often get an error message MUCH
later than you should have done, and they may even get delayed until
after the CLOSE (so you miss them). That explains why you�see the
error near the end.

In this particular case, I know exactly where the problem occurs,
because there is only one statement that uses that particular error
branch. The statement immediately following the WRITE statement
tests for a nonzero IOSTAT and if so, takes the error branch.
Furthermore, the program both writes the output to a disk file and
displays it on the screen. The screen write succeeds, and the disk
write fails, and the failure is when the program tries to write the
final two lines of the output file.

Secondly, think quotas and so on.

Already thought about that. If a quota was causing the problem, then
why wouldn't it also cause the same problem on the other disk drive?

Also remember that civilised systems
(not include Gnome, for example) use text files for configuration, and
can be searched. 'grep 127 /usr/include/*/errno.h' gives you your
answer!

It's the "answer" only if that's the only possible error 127. Without
knowing for sure what compiler was used to build the application, there
would seem to at least be the possibility that the runtime error is
specific to the compiler. What I found for g95 is that error numbers
1 to 199 are from the system, but I know that ifort has some runtime
errors in that range. Maybe they're the same?

I have no idea what sort of key it is blithering on about, as I am
no USB expert, but solving that is left as an exercise for the
student :-)

There are no ideas here either, hence the request to the newsgroup.

.

Relevant Pages

  • Re: fclose failure conditions
    ... disk volume for the use of my program. ... close my output file, I probably won't be able to write an message to ... My programs never store more than a small ... the file and reading from it without losing that buffered data. ...
    (comp.lang.c)
  • Re: Print statement within If-Then block changes output!!!????
    ... Does it have a floppy disk drive that is actually floppy? ... I am not sure about the status of the Fortran I compiler. ... The emulator is often many times faster than the original hardware. ... Very large disk space. ...
    (comp.lang.fortran)
  • Re: Some clarification on "Pre-Parsers" and other bits
    ... fast working on a typical GCC-generated assembly file. ... single assembler to output multiple diffent object formats" ... somewhat less code in the compiler. ... the assembly output to GAS without going through a disk file". ...
    (alt.lang.asm)
  • Re: Help with running IBM-COBOL ver 1.0 on Windows 2000/XP
    ... So long as its obsession to look for a disk in drive A are ... some versions of this compiler fail if you have ... compiler and in so called COBOL 650, ... file and debug script are doing. ...
    (comp.lang.cobol)
  • Re: non-32bit-relocation
    ... > basically, other code aside, the nasm compiler says, when using -f elf, that ... There are a number of assembly language resources for FreeBSD; ... to do disk I/O, and the BIOS interface does not own the disk, ...
    (freebsd-hackers)