 FASBE$LOG_IO Switch
The FASBE switch FASBE$LOG_IO can be
instrumental in determining
at what point in processing a program failure is occurring. Your
support representative may instruct you to define this switch
at DCL before entering into the FASBE system, as follows:
$ DEFINE FASBE$LOG_IO Y
After FASBE login each program accessed will
create a log in FDAT
recording all file input/output activity. The name of these log
files are LOG followed by the program name with a time stamp for
the file extension.
Example: LOGPAP100.13158842
NOTE:
Every action, including login itself, will be recorded
into an FDAT:LOG* file. You may want to delete excess logs before
analyzing with the suggestions which follow.
The best way to analyze the program data is
through formatting
the information into a more readable state. Utilize a peek command
file which resides in your COM directory to set up a predefined
FPEEKLOG symbol as follows:
$ @COM:PEEK_AS
$ FPEEKLOG/OUT=filename.out
Review the resulting file, noting that I/O
functions are coded
as follows in the 3rd position of the LOG-TRANSACTION section:
0 START
1 OPEN/INPUT
2 OPEN/IO
3 READ NEXT
4 CLOSE
5 READ
6 WRITE
7 REWRITE
8 DELETE
9 READ/LOCK
(Top)
| 
