Conference iosg::all-in-1

2591.0. "US SPD 3.2 bug, 4.0 SMNETUPDT.SCP ok ? " by UTRTSC::SCHOLLAERT (Think before you shrink) Fri Mar 28 1997 12:12

    Hi,
    
    Customer report known 3.2 problem:
    
    "network.dat fields blanked out with US SPD"
    
    When using the SPD (set personal details) it blanks out the
    fullname and department field in the Network profile.       

    Stars states: reported to Engineering, no workaround.
    
    I tested this function on V4.0 BL210. works fine.
    
    Looks like script SMNETUPDT.SCP and Form SPD contain the fixes...

    New on Form SPD : GET #US_SPD = 1\DO SMNETUPDT\
    
    $DIFF ALLI_USER:[ALLIN1_V40.LIB_SHARE]SMNETUPDT.SCP ALLI_USER:[ALLIN1_V
    32.LIB_SHARE]SMNETUPDT.SCP    /PARA
    
                                       |  !
------------------- 131 ----------------------------------- 136 ---------------
! check whether any field has been ch  |  ! check whether any field has been ch
------------------- 135 ----------------------------------- 140 ---------------
.IF #US_SPD EQ 1                       |
.THEN                                  |
    GET #NWK_FULNAM = FULNAM_DISP      |
    GET #NWK_DEPART = DEPART_DISP      |
.ELSE                                  |
    GET #NWK_FULNAM = FULNAM           |
    GET #NWK_DEPART = DEPART           |
.END_IF                                |
                                       |
------------------- 147 ----------------------------------- 143 ---------------
.IF NETWORK.FULNAM[#COMPKEY] NES #NWK  |  .IF NETWORK.FULNAM[#COMPKEY] NES FULN
------------------- 155 ----------------------------------- 151 ---------------
.IF NETWORK.DEPART[#COMPKEY] NES #NWK  |  .IF NETWORK.DEPART[#COMPKEY] NES DEPA
------------------- 195 ----------------------------------- 191 ---------------
  .FX WRITE CHANGE NETWORK %KEY=#COMP  |    .FX WRITE CHANGE NETWORK %KEY=#COMP
        DEPART=#NWK_DEPART,PHONE = PH  |          DEPART=DEPART,PHONE = PHONE,A
------------------- 237 ----------------------------------- 233 ---------------
  .FX WRITE CHANGE NETWORK %KEY=#COMP  |    .FX WRITE CHANGE NETWORK %KEY=#COMP
        DEPART=#NWK_DEPART,PHONE = PH  |          DEPART=DEPART,PHONE = PHONE,A
------------------- 246 ----------------------------------- 242 ---------------


    I tested US SPD with the 4.0 version of SMNETUPDT.SCP.
    Seems to work fine. Any gotchas ? If so, will there be a
    formal fix for 3.2 ?

    Cheers,

    Jan
    

    Re .1
    
    It's Easter here in Britain, so we were all out of the office on Friday
    and Monday. I'm two weeks behind...
    
    Note 1941 describes this problem at some length, and there's a V3.2
    patch for it. I expect that the patch contains the same file as the
    Office Server script, since we always fix in the base before building a
    patch, but I couldn't tell you for sure if that's true.
    
    Dave?

    >It's Easter here in Britain, so we were all out of the office on
    >Friday and Monday. I'm two weeks behind...
    
    It was also Easter here in Holland, but us support people 
    had to work anyway....
    
    Note 1941 is related to the DDS bug, not the NETWORK fields one.
    
    SUBSCRIBER_CHANGE_INTERACTIVE.SCP is processed after SMNETUPDT.SCP
    on form SPD, so I don't think it fixes the NETWORK bug.
    
    Cheers,
    
    Jan

    Many of us had to work over Easter as well.
    As you have discovered, I have fixed smnetupdt.scp in Office Server,
    but as yet, no patch has been made for V3.2.
    DaveT