It's embarrassing to admit, but I actually did this to myself in one of our products (SyzMPF/z) which automates console messages. We also use a name table to hold the address if the getmained area for later processing by multiple address spaces. In my haste, I had created a situation whereby I created a new area (which was at a new location) and removed the old one, but didn't update the token, so it still pointed to the old area and resulted int he same error you have now. Luckily my error was caught in QA testing and the people there took great pride in holding it over my head.
If the code doesn't first check to see if the token exists, and just goes out and makes a new area and fails to check that either the token failed to be change or failed to be created, you could end up with the same type of error. In our case it was an easy fix because we already had the code to test these out, I had just bypassed it. Brian ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
