PH47836: IDZ 15.0.3 REMOTE PREPROCESSOR DOES NOT RUN SUCCESSFULLY USING SEQUENTIAL DATASET FOR THE PREPROCESSOR OUTPUT LOCATION.

APAR status

• Closed as program error.

Error description

• IBM Developer for z Systems - IDz - v15.0.3
  Remote Preprocessor does not run successfully using
  sequential dataset for the Preprocessor Output Location.
  
  Recreate steps:
  1.Specify a dataset which include FEKRNPLI under REXX or CLIST
  invoking preprocessor field.
  2.Then specify an existing sequential dataset under Preprocessor
  output location field and High-lever qualifier under High-level
  qualifier for preprocessor data field.
  3.Open a program to run preprocessor will met this issue.
  

Local fix

• Workaround - specify a fully qualified PDS member for the
  Preprocessor Output Location.  In some cases, using a fully
  qualified PDS member worked and in other cases this workaround
  did not work.
  

Problem summary

• When using the "Identify using configured preprocessors" action
  to identify preprocessor statements using a remote preprocessor,
   as configured in the active property group, the action will
  always delete the resource defined in "Preprocessor Output
  Location" prior to executing the "REXX or CLIST invoking
  preprocesor", regardless of whether the "Preprocessor Output
  Location" resolves to an existing PDS member or a sequential
  data set.  This behavior is not compatible with the sample
  remote preprocessor scripts shipped with IDz, and after
  discussing internally it has been decided that if the output
  file resolves to a sequential data set, the action should not
  delete the remote resource prior to invoking the specified REXX
  or CLIST invoking preprocessor.
  

Problem conclusion

• The "Identify using configured preprocessors" action, when
  configured by the active property group to use remote
  preprocessors, will delete the remote resource identified by
  "Preprocessor Output Location" prior to executing the "REXX or
  CLIST invoking preprocesor" only if the "Preprocessor Output
  Location" resolves to an existing PDS member.  But if it
  resolves to a sequential data set it will not be deleted.
  

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