Two possibilities that I can think of (perhaps more) ... The FEKFRSRV task is not really an STC, but a (1) APPC task of a (2) USS task. In case (1), this task name should be placed in the ASCH subsystem entry under WLM option "6". In case (2), this task should be placed in the OMVS subsystem entry under WLM option "6".
IMHO, nothing should ever run with SYSOTHER, which you are correctly trying to fix. Everything should be well known, and classified accordingly. On Wed, 25 Apr 2007 07:01:06 -0400, Bob Shannon <[EMAIL PROTECTED]> wrote: >In our shop FEKFRSRV is in a service class of SYSOTHER even though I >explicitly defined it to go into another service class. I assumed it was >an STC. What do I have to do to get this thing out of SYSOTHER? TIA. > > > >Bob Shannon > >Rocket Software > > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO >Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
