IJ18226: RETURN CODE 127 FOR ALL ACTIONS CALLED THROUGH GENERICEVENTPLUGIN

9.5.0-IBM-IWS-WIN_X86_64_ZOS_AGENT-FP0002
9.5.0-IBM-IWS-WIN_X86_64_AGENT-FP0002
9.5.0-IBM-IWS-SOLARIS_ZOS_AGENT-FP0002
9.5.0-IBM-IWS-SOLARIS_AGENT-FP0002
9.5.0-IBM-IWS-SOL_I386_ZOS_AGENT-FP0002
9.5.0-IBM-IWS-SOL_I386_AGENT-FP0002
9.5.0-IBM-IWS-LNX_X86_64_ZOS_AGENT-FP0002
9.5.0-IBM-IWS-LNX_X86_64_AGENT-FP0002
9.5.0-IBM-IWS-LNX_S390_ZOS_AGENT-FP0002
9.5.0-IBM-IWS-LNX_S390_AGENT-FP0002
9.5.0-IBM-IWS-LNX_PPC_ZOS_AGENT-FP0002
9.5.0-IBM-IWS-LNX_PPC_AGENT-FP0002
9.5.0-IBM-IWS-LINUXPPC_LE_ZOS_AGENT-FP0002
9.5.0-IBM-IWS-LINUXPPC_LE_AGENT-FP0002
9.5.0-IBM-IWS-IBM_I_ZOS_AGENT-FP0002
9.5.0-IBM-IWS-IBM_I_AGENT-FP0002
9.5.0-IBM-IWS-HPIA64_ZOS_AGENT-FP0002
9.5.0-IBM-IWS-HPIA64_AGENT-FP0002
9.5.0-IBM-IWS-AIX_ZOS_AGENT-FP0002
9.5.0-IBM-IWS-AIX_AGENT-FP0002
9.5.0-IBM-IWS-agent-zcentric-container-FP0002
9.5.0-IBM-IWS-agent-dynamic-container-FP0002
9.5.0-IBM-IWS-WINDOWS_X86_64-FP0002
9.5.0-IBM-IWS-server-container-FP0002
9.5.0-IBM-IWS-LINUX390-FP0002
9.5.0-IBM-IWS-LINUX_X86_64-FP0002
9.5.0-IBM-IWS-AIX-FP0002

APAR status

• Closed as program error.

Error description

• Evaluated the TWS/bin/executeCMD.sh script and found that there
  are a couple of issues.
  
  
  
  1) The LOCALOPTS variable setting will only work if TWS_basePath
  and TWS_datadir happen to be the same value.  From the script:
  
  
  
  LOCALOPTS=$CURRDIR/../localopts
  
  
  
  Where $CURRDIR is the TWS bin directory.
  
  
  
  For example:
  
  If /etc/TWA/twainstance0.TWA.properties has the following
  entries:
  
  
  
  TWS_basePath=/opt/HWS/95/iws/TWS
  
  TWS_datadir=/opt/HWS/95/iws/TWSDATA
  
  
  
  The executeCMD.sh will set LOCALOPTS to
  /opt/HWS/95/iws/TWS/bin/../localopts, but the localopts file
  actually exists here: /opt/HWS/95/iws/TWSDATA
  
  
  
  2) All commands submitted via GenericEventPlugin fail to run
  successfully and get return code 127.
  
  
  
  This is a sample trace.log entry for an event rule that is
  defined to execute /tmp/chimp.sh
  
  
  
  [8/12/19 17:03:17:997 CDT] 0000008b id=00000000 java.lang.String
  > executeAction(ActionContext,ActionRun) ENTRY
  com.ibm.tws.event.plugin.action.ActionContext@43ec5afa
  {ActionRun: header=[{ActionRunHeader: id=[null]
  actionScope=[/TMP/CHIMP.SH] actionType=[RunCommand]
  ruleName=[TOUCHCHIMP] ruleType=[EventRuleType_F]
  pluginName=[GenericActionPlugin] timestamp=[null]
  actionStatus=[null] actionResult=[null] message=[null]}]
  actionId=[null] ruleId=[69a7ee58-9cf4-3761-bc56-517daef0adee]
  ruleInstanceId=[000000000000000000000000000417]
  parameterMap=[{Command=/tmp/chimp.sh}]}
  
  [8/12/19 17:03:17:997 CDT] 0000008b id=00000000
  com.ibm.tws.plugin.GenericActionPlugIn                      3
  executeAction(ActionContext,ActionRun) Executing command
  
  
  workDir=null
  
  
  cmdArray=[/opt/HWS/95/iws/TWS/bin/executeCMD.sh,
  "/tmp/chimp.sh"]
  
  
  envParArray=[]
  
  [8/12/19 17:03:18:007 CDT] 0000008b id=00000000
  I AWSGAP002E An error occurred performing the action. The reason
  is: "127".
  
  [8/12/19 17:03:18:008 CDT] 0000008b id=00000000 java.lang.String
  < executeAction(ActionContext,ActionRun) RETURN
  
  [8/12/19 17:03:18:013 CDT] 0000008b id=00000000
  I AWSAHL007E The action "RunCommand" of event rule instance
  "TOUCHCHIMP (8/12/19 5:03 PM)" has completed with errors:
  AWSGAP002E An error occurred performing the action. The reason
  is: "127".
  
  [8/12/19 17:03:18:013 CDT] 0000008b id=00000000
  I AWSAHL009E The event rule instance "TOUCHCHIMP (8/12/19 5:03
  PM)" has completed with errors.
  
  
  
  *Note: If executeCMD.sh is modified to remove the double quote
  characters from the ${PARM} value then a call to a single work
  command will execute successfully.  For example:
  
  PARM=`echo ${PARM} | sed -e 's/"//g'`
  
  This does not help with commands that contain more than one
  argument.
  

Local fix

• a workaround for the most simple scenario is stripping the
  double quotes characters off of the arguments that are passed to
   the executeCMD.sh script.  For example:
  
  
  
  After the line:
  
  
  
  PARM=\"$@\"
  
  
  
  ... I added this line:
  
  
  
  PARM=`echo ${PARM} | sed -e 's/"//g'`
  
  
  
  In this way, single word commands are able to launch.
  

Problem summary

•  see apar description
  

Problem conclusion

•  apar will be fixed into 9.5 FP2
  

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

  TIV WKLD SCHDL

• Fixed component ID

  5698WKB95

Applicable component levels