PN71403: AFTER RACF ABEND ALSO NVAS ABEND0C4 OCCURES AND NO USER IS ABLE TO LOGON TO NVAS. ALL LOGON ATTEMPTS FAILS WITH MSGEMS0507E.

APAR status

• Closed as suggestion for future release.

Error description

• RACF abends with 0C4 when a single user profile is destroyed in
  the RACF database. RACF recovers this situation.
  Then NVAS gets an ABEND0C4 in module EMSXRCVY + offset x'88'.
  NVAS seems to recover this situation because users already in
  session can work.
  But all user trying to logon to NVAS gets ems1035e on screen
  msgEMS1035E You cannot log on at the moment; try again later
  and msgEMS0507E ASR EMSELNQH ABNORMALLY TERMINATED. RC=000C4000
  in the syslog.
  NVAS must be restarted.
  NVAS recovery routine does not handle the EMSELNQH subtask.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• The NVAS recovery process is not designed to recover from
  abends in task EMSELNQH. When such an abend occur, the task is
  terminated; all the users currently logged on to NVAS can work
  regularly, but it is not possible for other users to log on to
  NVAS.
  
  This APAR gives a summary of NVAS recovery process
  functionality, as currently implemented in version 2.1.0.
  All the tasks define an ESTAE routine to perform clean-up and
  take an SDUMP in case of ABEND; not all the tasks are able to
  set a return point (SETRP macro) to recover from the abend. The
  decision was made during design to implement the recovery
  process only for the tasks that revealed to be more error prone;
  on the other hand, for some tasks a recovery process does not
  make sense, like EMSMAIN, that is responsible for initialization
  and termination.
  
  ** EMSMAIN Task ************************************************
  - ESTAE routine: EMSIESTA
  - No recovery implemented
  
  ** EMSRENV Task ************************************************
  - ESTAE routine: EMSRESTA
  - The recovery process is implemented for this task.
  
  ** EMSEUS Task *************************************************
  - ESTAE routine: EMSEESTA
  - The recovery process is implemented for this task with some
    restrictions.
    EMSEUS recovery process keeps the task from terminating
    whenever the abend occurs while the current processing is
    related to a specific resource id, that means always with the
    exception of the internal routine that dequeues an RQE. Only
    the involved user is dropped, meaning that user's terminal and
    application sessions are terminated.
  
  ** EMSELNQH Task ***********************************************
  - ESTAE routine: EMSEESTA
  - No recovery implemented
  
  ** EMSEVQH Task ************************************************
  - ESTAE routine: ABENDERR inside EMSEVQH
  - No recovery implemented
  
  ** EMSCINIT and EMSCSESS tasks *********************************
  - ESTAE routine: EMSCESTA
  - Recovery routine: EMSXRCVY
    Many CS modules can run under EMSCINIT, EMSCSESS or EMSEUS
    tasks; NVAS is able to always recover CS abends, except for CS
    initialization phase.
  
  ** EMSCTIME Task ***********************************************
  - ESTAE routine: EMSCESTA
  - No recovery implemented.
  
  ** EMSCEXTP Task ***********************************************
  - ESTAE routine: EMSCESTA
  - No recovery implemented.
  
  ** EMSCNISS Task ***********************************************
  - ESTAE routine: EMSCNEST
  - No recovery implemented.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels