The first time you run PWB or CodeView, it creates a CURRENT.STS (current status) file in your INIT directory. If there is no INIT directory, PWB and CodeView create the file in the current directory.
CURRENT.STS keeps track of the following items for PWB:
Open windows, including their size and position and the list of open files in each window
Screen height
Window style
Find string
Replace string
The options used in a find or find-and-replace operation, such as the use of regular expressions
Optionally, all environment variables
PWB and CodeView share the current location and filename for the active window. When you leave CodeView after a debugging session and return to PWB, PWB positions the cursor at the place where you stopped debugging. For more information on the items that CodeView saves in CURRENT.STS, see “The CURRENT.STS State File” on page 343.
The next time you run PWB, it reads CURRENT.STS and restores the editing environment to what it was when you left PWB. For more information on how PWB uses environment variables, see “Environment Variables”.
The status files are plain text files. You can load one into an editor and read it. However, you might corrupt the file if you try to modify it. There is no need to modify it because PWB keeps it updated for you. No harm occurs if you delete CURRENT.STS. However, you will have to manually reopen the files you were working on.