Skip to Main Content
Status Planned
Workspace EntireX
Created by Michael Brice
Created on Jun 5, 2023

Mainframe license check frequency

Minimise JES output utilisation Operational advantage. Simplify automatic log analysis. Ensure visibility of significant job log events.

I have a situation in an z/OS system where the LPAR Capacity is modified dynamically, with the consequence that a Broker task is performing a license check approximately 80 times per day, and an Adabas task is doing the same check approximately 12 times per day.

The output generated by Broker for a license check is 67 lines and for the Adabas task it is 18 lines of output.

The production environment is running 24/7, with the consequence that these tasks generate large volumes of JES output, up to 1 million lines per quarter for Broker (5 instances) and 100K lines per quarter for the Adabas task (120 instances). Over 97% of this output is a result of the license checks.

In conclusion I would propose the following:

  • All products that perform a license check should do so using the exact same criteria

  • The output should be conditional, based upon a configuration parameter with the values ALL, WARNING, or ERROR, where WARNING includes ERROR related events (default value WARNING).

  • The report generated should be the same for all checks for all relevant products

  • The output should be date/time stamped

  • Gadi Benedek
    Jul 2, 2023

    Dear Michael,

    Thank you for sharing your valuable feedback and submitting a feature request. We greatly appreciate your input and are pleased to inform you that your suggestion has been carefully evaluated and has been approved for implementation in our next release.

    We believe that this enhancement will provide a more efficient and enjoyable user experience. We are committed to delivering the highest quality and user satisfaction, and your feedback has played an instrumental role in shaping our product.

    We will keep you updated on the progress of the implementation and provide further details closer to the release date. Should you have any additional questions or suggestions, please don't hesitate to reach out to us. We value your partnership and are here to support you every step of the way.

    Once again, thank you for your valuable contribution, and we look forward to providing you with an improved experience in our next release.

    Best regards,

    Gadi Benedek

    Product Manager, EntireX