PROBLEM
The IVP test of the PhoneBook App w/r to the IMSAPPC
connector is failing.
There appears to be a security violation,
The phonebook application is part of the IMS APPC BETA connector IVP
code documentation from IBM.
See this doc under connector support;
http://www-3.ibm.com/software/webservers/appserv/download_v4z.html
WebSphere TM Application Server V4.0.1 for z/OS and OS/390 IBM
Connector Installation and Usage Guide
Version Beta 4.01.001
12/12/2001
This documentation describes installing the connector and using the
the
Phone Book Application for the IVP.
The PhoneBook connector code is failing at init time.
Messages:
Found module: /WebSphere/apps/BBOASR2/null/PhoneBookSessionEJB.jar
beans?0?.getEjbClass(): com.ibm.ws390.imsappc.phonebook.PhoneBookSession
Bean
com.ibm.ivj.eab.command.CommandException: IVJC0872: ResourceException
during execute() IMSAPPC_390RMIO.sendReceive(): reques
failed during cppSendReceive native method.
This appears to be an error in an ejb class.
From the trace.
Initially, I see minor code C9C24C07
Just prior to that there is the following trace records:
Trace: 2002/02/21 21:03:53.408 01 t=7E7828 c=1.4 key=P8 (13007002)
FunctionName: com.ibm.connector2.ws390.imsappc.IMSAPPC_390RMIO
SourceId: com.ibm.connector2.ws390.imsappc.IMSAPPC_390RMIO
Category: EVENT
ExtendedMessage: 390RMIO_SendReceive; value 1 = 578,832,512,
value 2 = "IVTNO", value 3 = [B@135baf65, value 4 = 49, value 5 = 89
value 6 = "HE70917", value 7 = false
.
Followed by a trace with "Error issuing APPC service" as the description.
In this trace, it says APPC service ATBRCVW failed with reason code 100
with APPC error code description:
ATB80100I From VTAM macro APPCCMD: Primary error return code: 0004
secondary error return code: 0005, sense code: 080F6051
followed by:
ATB70017I TP security violation. Partner LU IMS 3962 rejected the
allocate request because authorization checks failed.
.
Value 6 in the trace above is the user that is getting the security
violation.
The ID in value 6 "HE70917" ie mine !.. I ran the USS Phone Book script
from the shell.I will check on the LU settng and the IMS log .
.
Other reasons that could cause a security violation:
If the LUs are not defined with SECACPT=ALREADYV for already verified in
the VTAM config for the LUs, it could also surface as a security violation
since this setting would tell the IMS end not to do any checking for the
TP.
SOLUTION:
The key was a recycle of the WASLU.. We had fogotten that RACF APPC
profile, and had refreshed WAS and RACF, but not the WASLU. A recycle
of the WASLU today, and the test worked fine.
|