PQ45923: FTP FROM TSO GETS MESSAGE CEE5101C 0D070200

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Same problem as described in PQ39576 except this is for C socket
  instead of Extended sockets (PQ39576).Problem Scenario: After a
  C sockets application is started through ISPF.If an attempt is
  made to FTP from TSO it fails with the followingmessage:
  CEE5101C During initialization, the Open Edition callable servic
  BPX1MSS failed. The system return code was 0000000156,the reason
  code was 0D070200. The appl. will be terminated.
  Here's what the reason code means: 0200  JRPswKeyNotValid
  The PSW key of the caller is not a valid key.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the Communications Server for   *
  *                 OS/390 Releases 7, 8, & 10 IP: C Sockets API *
  ****************************************************************
  * PROBLEM DESCRIPTION: After an application that uses the C    *
  *                      Sockets API executes under TSO,         *
  *                      subsequent TSO applications fail with   *
  *                      msgCEE5101C rc156 rsn0D070200           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The problem with the EZASMI interface described by APAR PQ39576
  also exists in the C Sockets API.
  A user invokes a TSO application which establishes and
  terminates a TCP/IP connection via the C Sockets API.  While
  creating the application-TCP/IP connection, the C Sockets
  Transform layer calls OMVS to dub the address space tha
  represents the user's TSO session.  This is done in key 6 (C
  Sockets Transform layer always executes in key 6).  There is no
  BPX1MPC call when the application-TCP/IP connection is
  terminated.  The TSO user then invokes an application such as
  FTP which calls OMVS directly without using any of the Socket
  APIs that first transform the Sockets call to an OMVS call.
  OMVS sees that the user was dubbed in key 6 but the current call
  is not in key 6.  This results in the following error:
  CEE5101C During initialization, the Open Edition callable
  service BPX1MSS failed. The system return code was 0000000156,
  the reason code was 0D070200. The application will be
  terminated.
  
  Here's what the reason code means:
  0200  JRPswKeyNotValid
         The PSW key of the caller is not a valid key.
         Action: A service was requested that requires the invoker
         to be in the same key that the process was dubbed under.
  +-------------------------------------------------------------+
  + Please check our Communications Server for OS/390 homepages +
  + for common networking tips and fixes.  The URL for these    +
  + homepages can be found in Informational APAR II11334.       +
  +-------------------------------------------------------------+
  

Problem conclusion

• EZBSOCIF has been amended to issue a BPX1MPC call if it is
  terminating an application-TCP/IP connection and the current
  task has no other application-TCP/IP connections active.
  
  * Cross Reference between External and Internal Names
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UQ51566 UQ51568 UQ51569

Modules/Macros

• EZBSOCIF
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R370 PSY UQ51566

     UP01/03/13 P F103

• R380 PSY UQ51568

     UP01/03/13 P F103

• R50A PSY UQ51569

     UP01/03/13 P F103

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.