VMXAIC1250W Connect to *IDENT failed with IPRCODE= 15.

Document ID : KB000107133
Last Modified Date : 19/07/2018
Show Technical Document Details
Issue:
I have a z/VM 6.4 system with VM:Secure 3.2.
The z/VM 6.4 system is SSI enabled with two members in the SSI cluster.
do not know if this could be a possible cause of my issue, but I changed the SSI NAME of an SSI enabled cluster to SSI Name: SOE64ZVM.

Now I cannot initialize VM:Secure.
 am receiving the following errors:
   VMXAIC1250W Connect to *IDENT failed with IPRCODE= 15.
   VMXAIC1255I Attempting *IDENT reconnection in one minute.

Have you seen this problem before?
Any ideas on this?
Environment:
2-member SSI
Cause:
Missing IUCV *IDENT record in VMSECURE's directory entry. 
Resolution:
VM:Secure wouldn't initialize because of a missing IUCV *IDENT record in VMSECURE's directory entry.


In VMSECURE’s directory entry they had: 

IUCV *RPI MSGLIM 65535 
IUCV ALLOW 


** Please note, there is no IUCV *IDENT record in the entry. 


Their PRODUCT CONFIG showed: 

RESID VMSECURE GLOBAL 

SSINODE SOE64M01 
SSINODE SOE64M02 


As doc'ed: 

RESID resourcename [GLOBAL [SSIONLY]] 

Definitions 
• resourcename 
Specifies the name of an APPC resource. This resource name must also be specified on an IUCV*IDENT statement in the product server directory entry. 
• GLOBAL 
Specifies that the named resource is known globally throughout the TSAF or ISFC collection. The GLOBAL parameter must also be specified on an IUCV *IDENT statement in the product server directory entry, if this operand is present. 
• SSIONLY 
Specifies that APPC connections to the RESID are only accepted from VM systems residing in the SSI cluster as the VM system hosting the product server virtual machine. 


So, it looks like you need to add the IUCV *IDENT resid record in the directory entry for VM:Secure, with the correct resource ID. 

Update VMSECURE’s directory entry and add the IUCV *IDENT resid record and then try initializing again.