CLOPT Corrupts When Changing It Via MIB (Doc ID 2055913.1)

Last updated on SEPTEMBER 16, 2015

Applies to:

Oracle Tuxedo - Version 11.1.1.2.0 and later
Information in this document applies to any platform.

Symptoms

 When changing CLOPT for WSL via a MIB request it will be corrupted.

Initial value in ubbconfig:

"WSL" SRVGRP=WSGROUP1 SRVID=1 CLOPT="-A -- //10.10.10.10:40000 -H //20.20.20.20:MMMM -T 10 -m 250 -M 250 -x 8 -p 45501 -P 48499 -T 10 -N 180 -K both -z 0 -Z 0"

 Modify via MIB with following ud script

ud32 -C tpsysadm  <<!
SRVCNM  .TMIB
TA_CLASS        T_SERVER
TA_SRVGRP       WSGROUP1
TA_SRVID        1
TA_CLOPT        -A -- -n //10.10.10.10:40000 -H //30.30.30.30:MMMM -T 10 -m 250 -M 250 -x 8 -p 45501 -P 48499  -N 180 -K both -z 0 -Z 0
TA_MIN  1
TA_MAX  1
TA_OPERATION    SET

!

 tmunloadcf result (old "-H" option value is added at the end of new WSL CLOPT setting):

"WSL"   SRVGRP="WSGROUP1"       SRVID=1
        CLOPT="-A --  -n //10.10.10.10:40000 -H //30.30.30.30:MMMM -m 250 -M 250 -x 8 -p 45501 -P 48499 -N 180 -K both -z 0 -Z 0 //20.20.20.20:MMMMM 10 10"

 CLOPT is corrupted from tmunloadcf result, but it works well as expected parameter when booting WSL

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms