Each command has its own set off possible error messages. You can see the list using this procedure.
1. Go to a command entry line
2. Type the command (for example, CRTDUPOBJ)
3. Press F1. (Remember, F1 is your friend! Try it anywhere you can put a cursor).
4. Page down to the bottom. You should see a list of possible error messages.
5. Now for each message (for example, CPF2182), enter this command: DSPMSGD the-message-ID (for example, DSPMSGD CPF2182)
6. Take option 1 to look at the text. Often you will find recovery options.
This procedure is not fool proof because I'm making some assumptions that may not always be true.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
