Skip to main content
Status: Delivered

Included in ZMF 8.3

In many cases there are no "refresh" called for a package leaving the user a confused because you can't see what is in a package unless you refresh it yourself.

Status: Delivered

Included in ZMF 8.3

In many cases there are no "refresh" called for a package leaving the user a confused because you can't see what is in a package unless you refresh it yourself.

Hi Peter, Can you please provide some additional background or examples of where you believe the refresh should automatically occur? Many thanks, Steve
Status: Delivered

Included in ZMF 8.3

In many cases there are no "refresh" called for a package leaving the user a confused because you can't see what is in a package unless you refresh it yourself.

Examples would be: when a member is checkin from a pc file when a build is done it is not refreshed to Active In general every time something happens to a member or package it shiold be refreshed.
Status: Delivered

Included in ZMF 8.3

In many cases there are no "refresh" called for a package leaving the user a confused because you can't see what is in a package unless you refresh it yourself.

This may not always be possible for every ZMF4ECL action. For example, where an asynchronous process is executed on the mainframe that results in an adjustment to the ChangeMan Explorer contents. However, ENH334041 has been opened requesting that we research the automatic refresh of this view's contents after developer actions wherever reasonable and viable.
Status: Delivered

Included in ZMF 8.3

In many cases there are no "refresh" called for a package leaving the user a confused because you can't see what is in a package unless you refresh it yourself.

Octane item 21444. This will be researched to determine feasibility.

Terms & ConditionsAccessibility statement