RSED start with IVP parameter fails with Access Error

Problem

Similar error messages occur in various tests. RSED start with IVP parameter is failing with access error to IRRPTAUTH.FEKAPPL.* profile in the PTKTDATA security class.

Error

JES Job Monitor test:

executed on SYSTEM — Mon May 16 14:46:35 EDT 2011
executed by uid=130154(STCRSE) gid=839(STARTASK)
using /etc/rdz/rsed.envvars 
current address space size limit is 1084203008 (1034.0 MB)
maximum address space size limit is 1084203008 (1034.0 MB)
testing JES Job Monitor on port 6715...
Initialize failed, rc= 1004

Lock Daemon test:

executed on SYSTEM — Mon May 16 14:46:36 EDT 2011 
executed by uid=130154(STCRSE) gid=839(STARTASK)
using /etc/rdz/rsed.envvars 
current address space size limit is 1084203008 (1034.0 MB)
maximum address space size limit is 1084203008 (1034.0 MB)
testing RSE Lock Daemon on port 4036...
Initialize failed, rc= 1004

TCP/IP IVP test:

Initialize failed, rc= 1004

PassTicket IVP test:

the default applid=FEKAPPL 
Access Error to IRRPTAUTH.FEKAPPL.* profile in PTKTDATA security class:
   SAF RC=4 ; RACF RC=4 ; RACF Reason=0
 RSE daemon IVP ended — return code 40 —

Explanation and resolution

The RC=1004 is caused because the TCPIP stack could not be found.

Access Error to IRRPTAUTH.FEKAPPL.* profile in PTKTDATA is caused because PTKTDATA was not in the GENERIC PROFILE CLASS.

RC=1004 can be resolved by changing the socket initialization in FEKFIVPJ.

Parse value socket('Initialize', 'RSCLIENT') with return code. Parse value socket('Initialize', 'RSCLIENT',40,TCPIP stack name) with return code.

To make the client connection work, _BPXK_SETIBMOPT_TRANSPORT must be set in rsed.envvars pointing to the correct TCPIP stack.

The Access error can be resolved with: SETR GENERIC(PTKTDATA), followed by SETR RACLIST(PTKTDATA) REF.

Additional information

None.