The new administration SMF recording feature displays different data when the administration actions are run batch vs. foreground

Products

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

Issue/Introduction

Issue:

There are difference in administrative SMF records depending if they are generated either foreground or batch. SMF records generated foreground may contain more data than records generated from a batch administration job (ENBE1000).

Cause:

When an environment change is made foreground, the complete definition is displayed to screen. The output SMF record or ALOGDSN will reflect that data. However, when a change is made in batch, only limited data is available. For example, a 'DELETE TYPE' action in batch, only needs the environment, system, type, and stage. The batch generated SMP record will not have base or delta library information. If a type is deleted foreground, the SMF record will contain base and delta informtion, since that data is presented during the delete.   

Workaround:

Working as designed. If all environment data is required, perform action foreground.

Environment

Release:
Component: ENDBAS