SysLog message F61:
"TemSe input/output to a file that is not open"
This message may appear quite often in the SysLog.
No batch logs (job logs) exist: SM37 reports:
"Error occurred when reading job log JOBLGX...X...".
Message no. BT167
There are various possible causes.
SolutionYou will have to find the actual error. Possible method:
Evaluate the SysLog (SM21). Check off ->Layout in the settings:
With column for the message number
With lines for parameter records
Search for an F61 SysLog message. Record the time, client, and process. Position the cursor on the message and press F17=Ignore message. Then use ->SysLog ->Reformat to display a clearer list in which the F61 messages are suppressed.
Other SysLog messages should appear before the F61 messages (you will have to search for the time, since the F61 messages are no longer displyed). You will probably see something like:
E0A "&a /usr/sap/C11/SYS/global/000JOB" as parameter for the
subsequent SysLog entryg
E0A "&b LG/0001X11455901X13587 " as parameter for the subsequent
SysLog entry
E0A "&a [000]JOBLGX11455901X13587,1 " as parameter for the subsequent
SysLog entry
F3V File i/o error
If you find something like that: The first two entries contain the file name; the third contains the name of the TemSe object; the forth entry reports the actual error. Double-click on the forth item (Details). The end of the details list contains the Technical details -> Variable parts. The first five places are the operating system error number ("errno").
If your version of SM21 does not explain this number yet, you will have to look it up in the UNIX manual, page "intro(2)" or "errno", or in the UNIX file "/usr/include/sys/errno.h". The "errno"s also exist in non-UNIX systems, but these are explained somewhere in the C libraries. Unfortunately, the error numbers are platform-specific, and cannot all be included in this note.
The error number reveals the actual problem: Directory write-protected, disk full, etc.
No comments:
Post a Comment