If you get Read failed for view messages
You might get messages similar to the one shown in the following figure:
Read failed error message for CPUSTRT
COMMAND ===> SCROLL ===> PAGE
CURR WIN ===> 1 ALT WIN ===>
>W1 =LCUINFO===========SYSE=====*========DDMMMYYYY==HH:MM:SS====MVMVS====D=====
BBMXC7039E View CPUSTRT Not Found
Try one of the solutions in the following table:
Action | Explanation |
|---|---|
Check the messages in the window to see if the view name is misspelled. If it is, type the correct view name on the COMMAND line. If you were executing a hyperlink, type CUST and change the hyperlink target to the correct view name. | MainView looks for views spelled exactly as they are entered. You might have misspelled the view name when you typed it on the COMMAND line. If you were trying to execute a hyperlink, the view name might have been misspelled when the hyperlink was established. You can get a list of the view names by using the VIEWS view. |
Check the window information line. If it contains anything other than MVMVS, you are in another product. Change the product context back to MainView by issuing this command: CON = MVMVS | MainView shares a number of views with CMF MONITOR. Depending on how your site is set up, displaying one of these common views can automatically change the context to another product. For example, suppose you display the DSLIST view from MainView. Someone at your site has customized DSLIST while in CMF MONITOR, so that DSLIST is interpreted as a CMF view. When the view is displayed, the window information line changes from MVMVS to CMF. Then, when you try to display a view that is unique to MainView, MainView looks for the view in CMF, cannot find it, and displays the error messages shown in above Figure . Changing the context back to MVMVS solves the problem. |
Related topic