AE:Error when calling the function 'pthread_security_np(CREATE)', error code '139(EDC5139I Operation not permitted.)'

Document ID : KB000088333
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
The file transfer from z/OS to Linux fails with the following error message:

In the UNIX/Linux agent's log:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
20161116/202016.818 - U02000013 Connection to Agent 'dev1.prod.fedex.com:2300(*FT3439124)' initiated.
20161116/202016.828 - U02000006 Connection to Agent 'MVSDEV1(*FT3439124)' was successfully established.
20161116/202016.828 - U02000229 FT '3439124': Thread '00007FDF1A985700' started.
20161116/202016.828 - U00011407 FT '3439124': FileTransfer with partner 'MVSDEV1' started.
20161116/202016.831 - U02000102 Error when calling the function 'pthread_security_np(CREATE)', error code '139(EDC5139I Operation not permitted.)'.
20161116/202016.831 - U00011409 FT '3439124': FileTransfer ended abnormally.
20161116/202016.831 - U02000230 FT '3439124': Thread '00007FDF1A985700' ended.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

In the z/OS agent's log:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
20161116/142016.828 - Unable to create security environment for user 'opa2115'
20161116/142016.828 - U02000102 Error when calling the function 'pthread_security_np(CREATE)', error code '139(EDC5139I Operation not permitted.)'.
20161116/142016.828 - U02000135 Thread '*FT(3439124)' ended.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Environment:
OS: Z/OS
Resolution:
Assuming that z/OS Agent v11.2.2 has been installed and the system user has already the following permission on z/OS but the issue remains, you also need to make sure that the password in the LOGIN object for z/OS user is correct.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
​Needed permissions for agent user:
FACILITY class, BPX.SERVER profile with READ access
FACILITY class, BPX.DAEMON profile with READ access
FACILITY class, BPX.SUPERUSER profile with READ access
UserID of agentuser don't have to be zero, with BPX.SUPERUSER it should be able to change effective userid.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~