P102558: [PM8.1]: FLOW NAME DISAPPEARS AFTER SUBMITTED FROM SMC TO JFD

APAR status

• Closed as program error.

Error description

• [  flow name disappears in PM after submitted from client, for
  example, a flow name is WGENTING\88096533:Testing in SMC, after
   submitted to JFD, it becomes WGENTING\88096533 in JFD, the
  actual flow name "Testing" is missing  ]
  <IMPACT>: -- impact of problem in customer env (best/worse case
  scenarios)
  [  flow name is wrong, and the same user cannot submit more
  flows to JFD   ]
  <HOW TO REPRODUCE/DETAILS OF PROBLEM>: -- full details of the
  problem
      <Reproducing environment location & access>: [    ]
      <If no reproducing environment available, why>: [    ]
      <Customer data location if any>: [    ]
  
  ==============================Below is the issue description:
  
  In pm8.1 code:
  paragon/API/java/src/com/platform/LSFJobFlow/api/JFFlowDefinitio
  nManager.java,
  
     public void submitFlow(JFFlow flow, String comments, boolean
  ready,
                            String appKey) throws JFException,
  IOException
     {
  
  ...
          String flowname = flow.getName();
          String username = user.toJSUserName();
  
         if(flowname.startsWith(username + ":")) {
                 // do nothing, for keeping backward compatibility
          } else {
              flowname = username + ":" + flowname;
              flow.setName(flowname);
          }
     ...
  
    }
  
  The above code adds user name if it doesn't exist in flowname.
  Normally it works fine, however, it will cause problem in the
  following case:
  the flow.getName() has already contained username, for instance,
  the flowname is: WGENTING\88096533:Testing
  and the user who logged in SMC with lower case domain name:
  wgenting\88096533
  
  after scheduling the flow in SMC by the user who logged in as
  wgenting\88096533, the function adds a second user name to
  flowname, so the flowname becomes:
  wgenting\88096533:WGENTING\88096533:Testing, the evidence is in
  below XML file for this flow:
  
  <?xml version="1.0" encoding="UTF-8"?>
  <!--XML Jobflow definition -->
  <!--This file has been generated with Process Manager.
      Modify at your own risk.  Changes may render the definition
  unusable.
      The definition format may change in future versions of
  Process Manager.    -->
  <!DOCTYPE JobFlowReq SYSTEM "JobFlowDef30.dtd"><JobFlowReq
  DTDVersion="3.0"
  MainEntry="wgenting\88096533:WGENTING\88096533:Testing"
  EndBehaviour="FlowContinue"  FlowStateMailWhen="End"
  MailDestination="leechoon.chan@rwgenting.com"
  Description="Testing"  Exclusive="No"
  APP_AUTH="8fU15PiJ4Q+/qtU7uqx/UVzTXSaZySvLO0hGDMAonT+TJCiQzOEaBa
  jDkiStST16b4UOrMFfScJE
  w8wAoNDajg=="  Operation="Schedule" >
  <JobDef ExecutionType="lsf"
  Name="wgenting\88096533:WGENTING\88096533:Testing:testemail">
    <JobCmdLine
  Value="E:\SAS\GENM\Lev1\ETLMain\BatchServer\sasbatch.bat -log
  E:\SAS\GENM\Lev1\ETLMain\SASEnvironment\SASCode\JobLogs\testemai
  l_#Y.#m.#d_#H.#M.#s.log -batch -noterminal -logparm
  &quot;rollover=Session&quot;  -sysin
  E:\SAS\GENM\Lev1\ETLMain\SASEnvironment\SASCode\Jobs\testemail.s
  as"/>
    <UserName  Value="wgenting\88096533"/>
  </JobDef>
  <JobFlowDef
  Name="wgenting\88096533:WGENTING\88096533:Testing"><Events
  CombinationType="And"><Event GeneratorType="CalendarTime_v1"
  TimeZoneType="1" >Daily:20:53%1+Server@Sys</Event></Events>
    <ActivityDef  Name=""  ImplementType="Job"
  ImplementRefer="wgenting\88096533:WGENTING\88096533:Testing:test
  email" Description="null"
  ><Exceptions></Exceptions></ActivityDef>
  </JobFlowDef>
  </JobFlowReq>
  
  The wgenting\88096533:WGENTING\88096533:Testing will be
  truncated by JFD to wgenting\88096533:WGENTING\88096533 when
  creating flow, so the flow name "Testing" disappears after
  processed by JFD.
  
  The reason is in current code, we treat the domain name in low
  case and upper case as different, e.g. wgenting\88096533 is
  different from WGENTING\88096533, so
  flowname.startsWith(username + ":") returns false in this case;
  but actually user can logged in to Windows with both cases of
  domain name, as in windows user name is case insensitive. The
  code should handle this case.
  
  Related PMR: 13201,442,000
  

Local fix

• N/A
  

Problem summary

• FLOW NAME DISAPPEARS AFTER SUBMITTED FROM SMC TO JFD
  

Problem conclusion

• Delivered a formal patch to solve the problem.
  

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:

Fix information

• Fixed component name

  LSF STAND EDITI

• Fixed component ID

  5725G8201

Applicable component levels