BPXM047I BPXBATCH FAILED BECAUSE SPAWN (BPX1SPN) OF SLAPD FAILED WITH RETURN CODE 00000081 REASON CODE 053B006C when starting CA LDAP

Document ID : KB000047984
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:


BPXM047I BPXBATCH FAILED BECAUSE SPAWN (BPX1SPN) OF SLAPD FAILED WITH
        RETURN CODE 00000081 REASON CODE 053B006C.                  
IEF142I CALDAP CALDAP - STEP WAS EXECUTED - COND CODE 2816           
By BPXMTEXT BPXFSSTA 07/13/11       

JRFileNotThere: The requested file does not exist received when starting CA LDAP.

Solution:

IBM documents the error message as follows:


BPXM047I BPXBATCH FAILED BECAUSE SPAWN (BPX1SPN) OF program_name FAILED       
WITH RETURN CODE return_code REASON CODE reason_code. 

Explanation

BPXBATCH encountered an error when trying to issue a spawn (BPX1SPN) callable service to the program name specified. An incorrect program name may have been specified.

In the message text:


program_name - Up to the last 128 characters of the failed program name.   
return_code - The failure return code.                                     
reason_code - The failure reason code. For an explanation of the return    
             code and reason code, see z/OS UNIX System Services Messages 
             and Codes.  

System action
The system ends the program.

Operator response
None.

System programmer response
None.
None.

Programmer response
Look up the return code and reason code to determine why the BPX1SPN callable service (SPAWN) failed. Verify the program name exists in the path specified.

Module
BPXMBATC

Source
z/OS UNIX System Services kernel (BPX)

Routing Code
11

Descriptor Code
6

===========================================================================
Return Code:
===========================================================================
129 0081 ENOENT No such file, directory, or IPC member exists.
===========================================================================
Reason code:
===========================================================================

053B JrTdOptGone

The stack chosen by the IPv6 option or by the IPv4 option is not active on this socket.

Action: The function choose a stack with the IPV6_PKTINFO ancillary data item, IP_PKTINFO ancillary data item, sockaddr scope id, or socket options of IPV6_PKTINFO or IPV6_MULTICAST_IF and that stack is not attached to this socket. The stack may have been recycled since setsockopt() was called or the interface index used may be wrong.

The reason code '053B006C' during CA LDAP initialization usually means that the CA LDAP install directory or the slapd.conf file cannot be found.

  1. Ensure that the file system where the CA LDAP install directory resides is mounted.

  2. Confirm that all references to the CA LDAP directory name are spelled correctly and proper case used (lowercase/uppercase) in the CA LDAP startup JCL and slapd.env files.

  3. The CA LDAP started task acid OMVS segment must have a HOME directory that points to the CA LDAP directory name. Verify that it is spelled correctly and properly cased.

  4. Make sure the CA LDAP configuration file slapd.conf specification in the CA Top Secret startup JCL is spelled correctly and proper case used. It is specified on the statement that executes BPXBATA8 on the PARM parameter. For example:

    //LDAP EXEC PGM=BPXBATA8,REGION=0M,TIME=NOLIMIT,
    PARM='PGM slapd -d &DEBUG. -f ./slapd.conf'