z/OS-based licensing

z/OS-based licensing is available only for IBM® Developer for z/OS® Enterprise Edition, and allows a workstation to receive an activation code from the RSE daemon upon connection. No action is required on the workstation to enable this, but the z/OS host must be configured to enable provisioning of activation codes, as described in Security definitions.

z/OS-based licensing relies on workstations being able to uniquely identify themselves to the host. For this purpose, each workstation client generates a unique token upon first connecting to the host. When a client is cloned to another workstation, the existing unique token must be removed so that the new client can generate its own unique token. The resetting of the token is described in Value Unit client licensing considerations.

When the client connects to a host system that is configured for VU licensing, and the user selects the MVS Files node in the Remote Systems view, then the Properties view shows the status of the VU license (Active, Expired, or Not Available) and the registered VU Offering (for example, IBM APP DLIV FND). 
Note: You can see the client-based license type and status by using the Manage Licenses action in the IBM Developer for z/OS client or in Installation Manager, but not the z/OS-based (VU) license status. When the VU license status is Active, client-based licensing is not used. If the VU license status is Expired, then client based licensing is used until the client reconnects to the host system. After the client reconnects to the host, the VU license status is Active again. As long as users connect to the host at least once every 30 days, the VU license remains active.