DISP=MOD in Endevor processors causes C1X0245E

Products

• Endevor
• Endevor Natural Integration
• Endevor - ECLIPSE Plugin
• Endevor - Enterprise Workbench

Issue/Introduction

When using "DISP=MOD" in processor the dataset can be allocated in an unexpected way.  For example the dataset is allocated to
a non-SMS managed disk instead of a SMS managed as a temporary dataset should be.

Resolution

Here is an explanation of what is happening with DISP=MOD:

• For each processor step, ENDEVOR dynamically allocates the specified datasets by means of the DYNALLOC macro provided by MVS (also known as SVC 99).
  
  
• Unlike JCL allocation, the DYNALLOC macro does not support the allocation of a temporary dataset with DISP=MOD.
  
  
• ENDEVOR needs therefore to simulate it by allocating a permanent (cataloged) dataset and deleting it afterwards.
  
  
• Trying to catalog a dataset with a temporary dataset name may lead to various problems.

Prevent these problems by either:

• Avoiding to use DISP=MOD for temporary datasets in processors.
  
  
• Using the C1DEFLTS MODHLI= parameter causes ENDEVOR to format the dataset name differently for temporary datasets with DISP=MOD.
  Notes:
  1) The dataset will be allocated as <MODHLI>.DYYDDD. for the first qualifier(s) so this can result in error C1X0245E during the generate of a processor.
  2) If the ENCOPTBL option DS_INTERNAL_TEMP is enabled, the file will have the .RA000. qualifier instead of .RA0.