PH31179: MENU MANAGER (COMPLEX REMOTE INTERACTIVE FILE ACTION) RUNS COMMANDS IN THE WRONG ORDER, AND DOES NOT HONOR THE RETURN CODE

APAR status

• Closed as program error.

Error description

• To recreate the problem -
  
  In IDz v14.1 or 14.2 use Menu Manager to create a "remote
  action" according to the doc in
  https://www.ibm.com/support/knowledgecenter/SSQ2R2_14.1.0/com.ib
  m.tpf.toolkit.menumanager.doc/topics/complexfileaction2_t.html
  
  Set up a negative test (satisfied constraint: RC>0) (i.e.
  looking for failures only).  IDz ignores the return code; it
  acts as if the return code is always 0.  Use native TSO
  commands, TIME and LISTC, as well as a non-existent command,
  NONE or XYZ -
  
  first test -
  - set "remote action" to "NONE" (which gets rc=20), and
  "satisfied" action to "NO ACTION" (so expect to do nothing
  because rc=20), and set the "not satisfied" action to tso
  command "TIME".
  
  second test -
  - change the "remote action" to "LISTC" (gets rc=0).
  
  Both tests act as if the return code is zero.  Here's the output
  in the Remote Console (Note that the output of the "not
  satisfied" action shows up physically before the output of the
  actual command itself) -
  
  output from first test -
  ----------------------------------------
  > TIME
  IKJ56650I TIME-01:14:19 PM. CPU-00:00:00 SERVICE-372
  SESSION-00:00:00 MAY 1,2020
  ----------------------------------------
  > xyz
  RC=20
  ISPD223  Invalid command
  ISPD223  Command 'XYZ' not found or contains invalid syntax.
  
  output from second test -
  ----------------------------------------
  > TIME
  IKJ56650I TIME-01:16:18 PM. CPU-00:00:00 SERVICE-376
  SESSION-00:00:00 MAY 1,2020
  ----------------------------------------
  > LISTC ent('SYS1.PARMLIB') all
  NONVSAM ------- SYS1.PARMLIB
       IN-CAT --- CATALOG.V3S932
       HISTORY ...
       SMSDATA ...
       VOLUMES ...
  ...
  
  The first test should have performed no action after the rc=20.
  The second test seemed okay since the LISTC rc was not>0
  

Local fix

• none available
  

Problem summary

• See error description.
  

Problem conclusion

• The documentation has been updated with a limitation stating
  'Currently, there is no way to get the return code from the
  program or script.'
  

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

  DEV FOR Z/OS

• Fixed component ID

  5724T0700

Applicable component levels