|
|
| Author |
Message |
Tharageshwari Marukkutti
New User
Joined: 10 Oct 2007
Posts: 9
Location: Chennai, India
|
|
|
|
Hi,
CICS transaction fails with AICO abend for the userID CICSV32. The explanation quoted is " SECURITY VIOLATION " for that particular transaction.The User is not defined correctly.Please let me know how to define a Userid for a Transaction and is there anything need to be done to get rid of the Abend? |
|
| Back to top |
|
 |
References
|
 Posted: Thu May 29, 2008 5:30 pm Post subject: Re: AICO Abend for a transaction |
|
|
|
|
enrico-sorichetti
Global Moderator
Joined: 14 Mar 2007
Posts: 2665
Location: italy
|
|
|
|
| Quote: |
AICO
Explanation: An unexpected EXCEPTION response was received from a call to the user (US) domain.The call was issued during initialization of a transaction that was started without a terminal. The call was made as part of processing to associate the transaction with its intended user. The attempt to associate the intended user with the transaction has failed. The userid for the intended user of the transaction may not be correctly defined.
System Action: The transaction is abnormally terminated with a CICS transaction dump.
User Response: Determine why the intended user of the transaction is not correctly defined.
Examine messages produced for the CICS job by the external security manager (ESM). This may require the assistance of a security administrator.
It may be necessary to examine the transaction dump to determine why the external security manager has informed CICS that the user is not correctly defined.
When the user has been correctly defined, consider rerunning the transaction.
Module: DFHICXM
|
|
|
| Back to top |
|
|
Bill O'Boyle
Active User
Joined: 14 Jan 2008
Posts: 296
Location: Orlando, FL, USA
|
|
|
|
For further details, locate the User-EIB in the transaction dump, which will give you the last EIBFN, EIBRCODE, EIBDS (if applicable), EIBRSRCE (if applicable), EIBRESP (always non-zero) and EIBRESP2 (which may or may not be zero).
This might help you in determining what the program was attempting to do (IE: The last CICS API issued), so the Administrator of your "ESM" (External Security Manager), can adjust the security level (or outright disallow) this user's access.
Regards,
Bill |
|
| Back to top |
|
|
|
|
