OpenFrame/OSC 7.1
This chapter briefly describes new features of OpenFrame/OSC 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. Managing System Definition Resource as RDB
-
Changed the existing TSAM data set-based management of system definition resources, to RDB table-based management.
-
Modified to use the oscinit tool, to create SD resource tables as follows:
OFM_OSC_SD_GROUP OFM_OSC_SD_CONN CONNECTION OFM_OSC_SD_FILE FILE OFM_OSC_SD_PROG PROGRAM OFM_OSC_SD_TYPE_TERM TYPETERM OFM_OSC_SD_TERM TERMINAL OFM_OSC_SD_TSMODEL TSMODEL OFM_OSC_SD_JNL_MODEL JOURNALMODEL OFM_OSC_SD_MAP_SET MAPSET OFM_OSC_SD_WEB_SVC WEBSERVICE OFM_OSC_SD_PIPIELINE PIPELINE OFM_OSC_SD_ENQ_MODEL ENQMODEL OFM_OSC_SD_TCPIP_SVC TCPIPSERVICE OFM_OSC_SD_SESSION SESSIONS OFM_OSC_SD_PARTITION PARTITIONSET OFM_OSC_SD_PROFILE PROFILE OFM_OSC_SD_LIBRARY LIBRARY OFM_OSC_SD_URIMAP URIMAP OFM_OSC_SD_TRANS TRANSACTION OFM_OSC_SD_TRAN_CLASS TRANCLASS OFM_OSC_SD_TDQ TDQUEUE
-
For more information about SD resource tables, refer to "3.3 Creating Application Server Database Tables" in OpenFrame OSC Administrator’s Guide.
-
For more information about how to use the osiinit tool, refer to OpenFrame Tool Reference Guide.
-
1.2. RTSD Management Method Changed
-
The previous method created and dropped RTSD tables on startup and shutdown of a region.
The updated version creates RTSD tables by using the oscinit tool and reads SD tables on startup of a region, to load them into RTSD tables. On shutdown of a region, RTSD records are deleted from the region.
-
The following RTSD tables are created by oscinit.
OFM_OSC_CONN CONNECTION OFM_OSC_FILE FILE OFM_OSC_PROG PROGRAM OFM_OSC_TERM TERMINAL OFM_OSC_TSMODEL TSMODEL OFM_OSC_JNL_MODEL JOURNALMODEL OFM_OSC_MAP_SET MAPSET OFM_OSC_WEB_SVC WEBSERVICE OFM_OSC_PIPIELINE PIPELINE OFM_OSC_ENQ_MODEL ENQMODEL OFM_OSC_TCPIP_SVC TCPIPSERVICE OFM_OSC_PARTITIONSET PARTITIONSET OFM_OSC_PROFILE PROFILE OFM_OSC_LIBRARY LIBRARY OFM_OSC_URIMAP URIMAP OFM_OSC_TRANS TRANSACTION OFM_OSC_TRAN_CLASS TRANCLASS OFM_OSC_TDQ TDQUEUE OFM_OSC_NETNAME NETNAME
-
For more information about RTSD resource tables, refer to "3.3 Creating Application Server Database Tables" in OpenFrame OSC Administrator’s Guide.
-
For more information about how to use the osiinit tool, refer to OpenFrame Tool Reference Guide.
-
1.3. TCache Configuration Changed
-
Each CACHE_NAME in pfmtcache.cfg has been modified in accordance with each changed RTSD table name.
#cache for OSCOIVP1 CACHE_NAME=OSCOIVP1 # the name of cache SIZE_MEM=32767 # the total cache memory size in kilo-bytes SIZE_HASH=32 # the number of hash key (MAX=65536) SIZE_KEY=30 # the number of digits of the index column SIZE_REC=2078 # the size of a single record in bytes INV_TIMEOUT=1 # invalidation timeout in sec # cache for REGION MASTER CACHE_NAME=OFM_OSC_REGION_MASTER # the name of cache SIZE_MEM=32 # the total cache memory size in kilo-bytes SIZE_HASH=32 # the number of hash key (MAX=65536) SIZE_KEY=8 # the number of digits of the index column SIZE_REC=40 # the size of a single record in bytes INV_TIMEOUT=1 # invalidation timeout in sec #cache for OFM_OSC_TX_TIME CACHE_NAME=OFM_OSC_TX_TIME # the name of cache SIZE_MEM=32 # the total cache memory size in kilo-bytes SIZE_HASH=32 # the number of hash key (MAX=65536) SIZE_KEY=14 # the number of digits of the index column SIZE_REC=38 # the size of a single record in bytes INV_TIMEOUT=1 # invalidation timeout in sec
2. Miscellaneous Information
This section describes changes to the product.
2.2. TSAM Connection Method Changed
-
Changed the existing [DB_INFO] section from osc.conf, to the [DBIO_CLIENT] section in dbconn.conf, an OpenFrame configuration file.
-
Changed the existing [TSAM_CLIENT] section from osc.conf, to the [TSAM_CLIENT] section in dbconn.conf, an OpenFrame configuration file.
2.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.
-
For more information about OpenFrame Configuration, refer to OpenFrame Configuration Guide.
-
For more information about how to use the ofconfig tool, refer to OpenFrame Tool Reference Guide.
-
2.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.
2.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.
-