Posted by Frank Schubert on July 02, 2007 at 11:36:37:
In Reply to: VIOF150C posted by Keith Reynolds on June 15, 2007 at 12:12:29:
: What is VIOF150C. I get this message when trying to initiate IOF. From
: our main menu, I enter I.I. The panel has I,'PGM(IOFSPF)....'. In the
: upper right hand corner I get 'NO MATCH'. I hit PF1 to show the long
: message which is 'NOTHING MATCHING SPECIFIED SELECTION CRITERIA WAS FOUND'.
: I enter MSGID and get 'The message ID of the last message was "VIOF150C"'.
: I am the only user having this problem.
The usage of "I.I" threw me off. After communicating with you, I determined that effectively, you were just trying to invoke IOF without any parameters. So for purposes of this discussion, you were just issuing the "I" command.
It appears that you must have the "NOMATCH=EXIT" parameter set in the B49CMPAT option member. If it is not specified in the B49CMPAT member, then the default is "NOMATCH=EXIT". What this means is that if you bring up IOF and it cannot find any jobs, then it will exit with the "NO MATCH" error message.
My guess would be that what happened to you is that you might have had a JOBNAME prefix set which might have been present in the system at one time, but when you received this error, there were not jobs in the system with this jobname. Hence IOF received this error message and exited. There are other ways other than JOBNAME that will cause a "NO MATCH" error, such as a DEST with no jobs routed to it.
There are three ways to get around this. The easiest is whenever you get a "NO MATCH" error, you should always be able to invoke IOF and request that you go to the "IOF Option Menu". This should always be permitted and you would then see whatever filter was applied that was causing the problem. The easiest way to do this is to issue "I.". For your situation, this would be "I.I.". Note the extra period.
The second is to change the NOMATCH parameter in B49, but this will have an effect system wide. If you do this, then any user that is used to IOF exiting back to the ISPF Primary Option menu, will not longer experience this. By setting "NOMATCH=MENU", this causes IOF to remain active and stay on the "IOF Options Menu" with the "NO MATCH" error, instead of exiting to ISPF. Not a big issue, but would be a change that would affect many users. This might be looked on as a positive thing, but it also might not as it means that IOF would be working differently than before. My experience is that users tend to get upset when things change.
The third thing, which is what I am guessing you might have done is to delete the IOFPROF member in your ISPF Profile dataset, which would have removed the filter, thus allowing you back into IOF. But this would also have deleted other profile settings you might have made. THis is also not recommended.
There are other things that might have occured to confuse you, but they chance of it being one of these is less likely, but not impossible.
So, the best thing to do when you experience this, is to invoke IOF with the extra period, as in "I.". This will always allow you into IOF, where you can make adjustments to display other things. If you find that using "I." does not work, then you should contact technical support as there is possibily another issue in the way that IOF is being invoked that prevents this.
I hope this helps.
Thanks.