OpenFrame/Batch 7.1

This chapter briefly describes new features of OpenFrame/Batch 7.1. For further details on each feature, refer to the respective guide.

1. Updated Features

This section describes updated features of the new version.

1.1. Storing SPOOL Meta Information into Database

  • Modified so that any job-related meta information can be stored in a database, to address the FILE LOCK performance issues.

  • Set the USE_DATABASE key to NO, in the SPOOL section of the tjes subject, under OpenFrame Configuration, if you want to maintain the existing file-based management.

    For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide.

1.2. Managing Runner Slot Information as Tables

  • Changed the existing shared memory-based management of Runner slot information, to table-based management in a database.

  • Added OFM_BATCH_RUNNER tables to manage Runner slots.

1.3. Managing OpenFrame Configuration Information as Tables

  • Modified so that the existing file-based OpenFrame configuration information can be managed as tables in a database.

  • Changed the configuration meta file format to be loaded in a database, and separated each file by individual product.

  • Modified to load data into TmaxTCache, to synchronize the configuration information and support multi-node environments.

  • Added the ofconfig tool, to manage the modified configuration information structure.

    1. For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide.

    2. For more information about how to use the ofconfig tool, refer to OpenFrame Tool Reference Guide.

1.4. Managing Error Codes as Tables

  • Modified so that the existing file-based OpenFrame error information can be managed as tables in a database.

  • Added the insert feature to the oferror tool to load the error information into a database.

    For more information about the oferror tool, refer to OpenFrame Tool Reference Guide.

1.5. Formatting System and Server Logs

  • Formatted logs for all OpenFrame products.

  • Improved the date-hour display format in logs.

    • Service log format

      [YYYY-MM-DDTHH:MM:SS.ffffff] [SERVICE-NAME(PID)] [M] [MSGCODE] MESSAGE-CONTENTS

    • System log format

      [YYYY-MM-DDTHH:MM:SS.ffffff] [EXECUTED-MODULE] [CODE] [MSGCODE] EVENT FREE-FORMAT-CONTENTS

    • Operational log format

      [YYYY-MM-DDTHH:MM:SS.ffffff] [EXECUTED-MODULE] [CODE] [MSGCODE] EVENT FREE-FORMAT-CONTENTS

      For more information about logs in OpenFrame, refer to "Appendix.D Log Management" in OpenFrame Base Guide.