Shutdown of IMS receive ACF05021 LOGONID nnnnnnnn NOT FOUND IN DATABASE; SVC DUMP HAS BEEN TAKEN
search cancel

Shutdown of IMS receive ACF05021 LOGONID nnnnnnnn NOT FOUND IN DATABASE; SVC DUMP HAS BEEN TAKEN

book

Article ID: 392955

calendar_today

Updated On:

Products

ACF2 - z/OS ACF2 - MISC

Issue/Introduction

Shutdown of IMS received the following message/dump:


 *ACFFE001 SVCA-CLN DUMP IN PROGRESS
  IEA794I SVC DUMP HAS CAPTURED:  nnn
  DUMPID=004 REQUESTED BY JOB (nnnnnnnn )
  DUMP TITLE=ACF05021 LOGONID nnnnnnnn NOT FOUND IN DATABASE; SVC
             DUMP HAS BEEN TAKEN
  ACFFE002 SVCA-CLN DUMP COMPLETED
  ACF05021 LOGONID nnnnnnnn NOT FOUND IN DATABASE; SVC DUMP HAS BEEN TAKEN  IMS

 

Questions:

  1. Will this occur even if the sign off command is used? 
  2. Will this occur for every logon that is not found (for example if 10 have been deleted will 10 messages/dumps be produced?)
  3. Is there any option to suppress this dump?

Environment

Product: ACF2

Resolution

Regarding the ACF05021 message, as part of the signoff process, ACF2/IMS attempts to update the violation count in the logonid record in the database but the logonid record is not there. This causes the abend.   

Answer to questions:

  1. If the administrator wishes to delete a logonid, they can issue a "/ACF SHOW SIGNON logonid" command and see where the logonid is signed on before issuing the delete and wait until the logonid is signed off or canceled prior to deleting the logonid. Or, instead of DELETE the logonids - you can SUSPEND them and then after a while - maybe a week/month etc you can delete all the SUSPENDed logonids.     
  2. The dump will occur if ACF2/IMS attempts to update the violation count in the logonid record in the database but the logonid record is not there.
  3. The SVC dump is generated to document the events surrounding the finding that a logonid record to be updated is not there. This could occur if the logonid was deleted while the user was logged on. Or, it could be a hacker who has chosen to break into the system the hard way, and  has faked up all the proper control blocks to look like he is using a logonid that doesn't exist, but has neglected to clean them up at logoff time.  For this potential situation the dump is produced, so they can root around in it and see what is going on. Currently there is no option to suppress the dump.