IBM Support

How to use proxy.attempts in C:D UNIX

Technical Blog Post


Abstract

How to use proxy.attempts in C:D UNIX

Body

The proxy.attempt parameters in C:D UNIX netmap.cfg file is used to force all users to be proxied when it is set to y:

# Local Connect:Direct connection information
local.node:\
 :api.max.connects=16:\
...
:proxy.attempt=y:

This is a sample implementation scenario.

The user needs to submit several processes on C:D z/OS to copy files to C:D UNIX.
All processes are submitted by the same userid but for each submitted process the user wants a different C:D UNIX local userid to be used.
For example the MVSUSER userid on the C:D z/OS node CD.ZOS submits these three processes, each one should use a different C:D UNIX local userid:
   
   PROC1 should use C:D UNIX local userid user1
   PROC2 should use C:D UNIX local userid user2
   PROC3 should use C:D UNIX local userid user3

This cannot be done directly within the C:D userfile.cfg file as there is no support for a one to many mapping.

The user can use proxies to accomplish this task:

  1- specify proxy.attempt=y in the netmap.cfg file

  2- Add the SNODEID parameter with a dummy username in each process submitted on C:D z/OS:

     PROC1 PROCESS SNODEID=(MVSUSER1) ...
     PROC2 PROCESS SNODEID=(MVSUSER2) ...
     PROC3 PROCESS SNODEID=(MVSUSER3) ...

  3- Create remote user records in the userfile.cfg file corresponding to each of the dummy username:
     
     MVSUSER1@CD.ZOS:\
      :local.id=user1:

     MVSUSER2@CD.ZOS:\
      :local.id=user2:

     MVSUSER3@CD.ZOS:\
      :local.id=user3:

4- Create local user records in the userfile.cfg file for user1, user2 and user3.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS4PJT","label":"IBM Sterling Connect:Direct"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

UID

ibm11123833