OpenTP1 Version 7 System Definition

[Contents][Index][Back][Next]

Summary of amendments

The following table lists changes in this manual (3000-3-D52-30(E)) and product changes related to this manual for uCosminexus TP1/Server Base 07-03, uCosminexus TP1/Server Base(64) 07-03, uCosminexus TP1/Message Control 07-03, uCosminexus TP1/Message Control(64) 07-03, uCosminexus TP1/NET/Library 07-04, and uCosminexus TP1/NET/Library(64) 07-04.

Changes Location
The journal service is now able to output performance verification trace information (JNL performance verification trace).
With this change, the following operands and definition have been added:
  • System common definition
    jnl_prf_event_trace_level
  • JNL performance verification trace definition
The description for the following operand has also been changed:
  • Performance verification trace definition
    prf_trace_backup
1.1, 1.2, 1.2.1, 2.1.1, 2.2(4), 2.2(36)

System common definition in Chapter 3
jnl_prf_event_trace_level

Performance verification trace definition in Chapter 3
prf_trace_backup

JNL performance verification trace definition in Chapter 3, 7.2, Appendix D
Performance verification trace information for various lock events used by the lock service (LCK performance verification trace) can now be output.
With this change, the following operands and definition have been added:
  • User service definition
    lck_prf_trace_level
  • LCK performance verification trace definition
The description for the following operand has also been changed:
  • Performance verification trace definition
    prf_trace_backup
1.1, 1.2, 1.2.1, 2.1.1, 2.2(5), 2.2(37)

Lock service definition in Chapter 3
lck_prf_trace_level

Performance verification trace definition in Chapter 3
prf_trace_backup, LCK performance verification trace definition in Chapter 3, 7.2, Appendix D
A note has been added about creating definitions. 1.3
The explanation about the maximum length of a definition line has been changed. 1.4.2(6)
UAP trace information (UAP trace data file) can now be acquired without having to abort the process.
With this change, the following operands have been added:
  • System common definition
    uap_trace_file_put
  • User service default definition
    uap_trace_file_put
  • User service definition
    uap_trace_file_put
2.2(4), 2.2(41), 2.2(42)

System common definition in Chapter 3
uap_trace_file_put

User service default definition in Chapter 3
uap_trace_file_put

User service definition in Chapter 3
uap_trace_file_put

Specification of operands in user service definition for UAPs in Chapter 3
A function for specifying whether to use service information of specific nodes in a prioritized fashion has been added (service information prioritizing function).
With this change, the descriptions for the following operands have been changed.
  • System common definition
    all_node
    name_domain_file_use
The following operand has also been added:
  • Name service definition
    name_cache_validity_time
2.2(4), 2.2(7)

System common definition in Chapter 3
all_node, name_domain_file_use

Name service definition in Chapter 3
name_cache_validity_time, 7.2, Appendix D
Explanations have been added for the following operands about the timing at which RPC processing is retried.
  • System common definition
    rpc_retry
    rpc_retry_count
    rpc_retry_interval
2.2(4)

System common definition in Chapter 3
rpc_retry,
rpc_retry_count,
rpc_retry_interval
Event trace information (FIL event trace) can now be output in OpenTP1 file access requests.
With this change, the following operands have been added.
  • System common definition
    fil_prf_trace_option
    fil_prf_trace_delay_time
The description for the following operand has also been changed.
  • Performance verification trace definition
    prf_trace_backup
2.2(4)

System common definition in Chapter 3
fil_prf_trace_option, fil_prf_trace_delay_time

Performance verification trace definition in Chapter 3
prf_trace_backup

7.2
Explanations about the default values for the following operands have been changed.
  • Transaction service definition
    thread_stack_size
  • TAM service definition
    tam_pool_attri
2.2(10), 2.2(23)

Transaction service definition in Chapter 3
thread_stack_size

TAM service definition in Chapter 3
tam_pool_attri
Explanations have been added for the following operands.
  • System common definition
    ipc_sockctl_highwater
    ipc_sockctl_watchtime
  • RAP-processing listener service definition
    ipc_sockctl_highwater
    ipc_sockctl_watchtime
2.2(32)

System common definition in Chapter 3
ipc_sockctl_highwater, ipc_sockctl_watchtime

RAP-processing listener service definition in Chapter 3
ipc_sockctl_highwater
ipc_sockctl_watchtime
7.2
Explanations about the fixed specification have been changed for the following operands.
  • System environment definition
    shmpool_attribute
  • DAM service definition
    dam_cache_attribute
  • TAM service definition
    tam_pool_attri

System environment definition in Chapter 3
shmpool_attribute

DAM service definition in Chapter 3
dam_cache_attribute

TAM service definition in Chapter 3
tam_pool_attri
The explanation about global domains has been changed for the following operand.
  • System common definition
    rpc_multi_tp1_in_same_host

System common definition in Chapter 3
rpc_multi_tp1_in_same_host
Formulas for calculating the maximum size of record data acquired in the journal when the MQA service is used have been added to the description for the following operand.
  • System journal service definition
    jnl_max_datasize

System journal service definition in Chapter 3
jnl_max_datasize
Explanations about system behavior when Y is specified have been added for the following operands.
  • System journal service definition
    jnl_unload_check
  • Archive journal service definition
    jnl_unload_check
  • User service definition
    service_hold
    service_priority_control

System journal service definition in Chapter 3
jnl_unload_check

Archive journal service definition in Chapter 3
jnl_unload_check

User service definition in Chapter 3
service_hold, service_priority_control
Explanations about output of messages to syslog have been added for the following operands.
  • Log service definition
    log_syslog_out
    DCSYSLOGOUT

Log service definition in Chapter 3
log_syslog_out, DCSYSLOGOUT
The formula for determining the assumed buffer area size has been changed for the following operands.
  • DAM service definition
    dam_cache_size
    dam_cache_size_fix

DAM service definition in Chapter 3
dam_cache_size, dam_cache_size_fix
Notes for the RAP-processing listener service definition have been added or changed. RAP-processing listener service definition in Chapter 3
An explanation has been changed about the rtsput definition command options and the acquisition-target objects that can be specified.

Real-time statistics service definition in Chapter 3
rtsput
Explanations about when specification of the following operands is omitted have been changed.
  • User service default definition
    rpc_trace
    rpc_trace_name
    rpc_trace_size
  • User service definition
    rpc_trace

User service default definition in Chapter 3
rpc_trace,
rpc_trace_name,
rpc_trace_size

User service definition in Chapter 3
rpc_trace
A note has been added about specifying the -i option with the trnrmid definition command.

User service default definition in Chapter 3
trnrmid

User service definition in Chapter 3
trnrmid
An explanation about specifying the status_change_when_terming operand has been added to the description for the following operand.
  • User service definition
    node_down_restart

User service definition in Chapter 3
node_down_restart
The maximum value that can be specified with the -j option has been increased for the following definition commands:
  • mcfmcomn
  • mcfmuap
  • mcftcomn
4.2(1), 4.2(2)

MCF communication configuration definition in Chapter 5
mcfmcomn,
mcfmuap,
mcftcomn
An explanation about timer start request messages has been added to the description for the -t option of the mcfttim definition command.

MCF communication configuration definition in Chapter 5
mcfttim
The number of messages that are output has been changed when 0 is specified in the -m option of the mcftalcle definition command, or when specification of the -m option is omitted.

MCF communication configuration definition in Chapter 5
mcftalcle
An explanation has been added about how to specify the -n option of the mcfaalcap definition command when the application start function is being used.

MCF application definition in Chapter 5
mcfaalcap
Notes and definition examples have been added for the -g option and the -v option of the mcfaalcap definition command.

MCF application definition in Chapter 5
mcfaalcap
A step and a note have been added in the section on how to change definitions. 7.1
The following status inheritance definitions have been added as definitions that are affected by changes in an OpenTP1 system:
  • The -g option of the mcfmsts definition command
  • The -v option of the mcfmsts definition command
7.3.1
scd_hold_recovery_count has been added in the scd file as a definition that is affected by changes in an OpenTP1 system. 7.3.1, 7.3.2
A procedure for changing host names and IP addresses has been added. 7.3.5(2)
Formulas for estimating the amount of static shared memory required for TP1/Server Base have been changed. B.1(1)(g), B.1(1)(n), B.1(2)(f)
The formula for estimating the size of the shared memory pool has been changed. B.1(8)
Formulas have been added for estimating the amount of static shared memory for the MCF service, and the relationships between the specified definition values. B.2(1)
Formulas for estimating the amount of static shared memory required for the MCF service have been changed. B.2(1)(a), B.2(1)(b)
OpenTP1 service start and OpenTP1 service stop have been added as audit events. Appendix C
Messages and problem identification codes output during definition checking have been added and changed. Appendix D
Notes have been added about migrating to OpenTP1 Version 7 from OpenTP1 Version 5 or earlier. Appendix E

The following table lists changes in this manual (3000-3-D52-30(E)) and product changes related to this manual for uCosminexus TP1/Message Control 07-02 and uCosminexus TP1/NET/Library 07-03

Changes Location
MHP can now use the facility for dynamic loading of services.
With this change, the description for the following operand has been changed.
  • User service definition
    service

User service definition in Chapter 3
service
When MCF static shared memory is insufficient, additional memory from an unused area is automatically secured.
With this change, the following option has been added:
  • The -i option of the mcfmcomn definition command
4.3.3(4)

MCF manager definition in Chapter 5
mcfmcomn

The following table lists changes in this manual (3000-3-D52-30(E)) and product changes related to this manual for uCosminexus TP1/Message Control 07-01 and uCosminexus TP1/NET/Library 07-01

Changes Location
Performance verification information (MCF performance verification trace) can now be output for important events during message exchange processing.
With this change, the following definitions and operands have been added:
  • User service default definition
    mcf_prf_trace
  • User service definition
    mcf_prf_trace
  • MCF performance verification trace definition
  • System service information definition
    mcf_prf_trace
  • System service common information definition
    mcf_prf_trace_level
The description for the following operand has also been changed.
  • Performance verification trace definition
    prf_trace_backup
1.1, 1.2, 1.2.2, 2.2(41), 2.2(42)

Performance verification trace definition in Chapter 3
prf_trace_backup

User service default definition in Chapter 3
mcf_prf_trace

User service definition in Chapter 3
mcf_prf_trace

Specification of operands in user service definition for UAPs in Chapter 3, Table 4-2 in subsection 4.1.1, 4.2(4), 4.2(5), 4.2(6) MCF performance verification trace definition in Chapter 5

System service information definition in Chapter 5
mcf_prf_trace

System service common information definition in Chapter 5
mcf_prf_trace_level

7.2, B.2(1)(a)
MCF information can now be acquired as real-time statistics acquisition items.
With this change, the following definition and operands have been added:
  • Real-time statistics acquisition-item definition
    rts_mcf_ap_scd_stay
    rts_mcf_ap_usr_srvc
    rts_mcf_in_msg_scd_wait
    rts_mcf_out_msg_sync_scd_wait
    rts_mcf_out_msg_resp_scd_wait
    rts_mcf_out_msg_prio_scd_wait
    rts_mcf_out_msg_norm_scd_wait
    rts_mcf_que_scd_wait_num
2.2(40)

Real-time statistics acquisition-item definition in Chapter 3
rts_mcf_ap_scd_stay, rts_mcf_ap_usr_srvc, rts_mcf_in_msg_scd_wait, rts_mcf_out_msg_sync_scd_wait, rts_mcf_out_msg_resp_scd_wait, rts_mcf_out_msg_prio_scd_wait, rts_mcf_out_msg_norm_scd_wait, rts_mcf_que_scd_wait_num

In addition to the above changes, minor editorial corrections have been made.

The following table lists changes in the manual (3000-3-D52-20(E)) and product changes related to that manual for uCosminexus TP1/Server Base 07-02, uCosminexus TP1/Message Control 07-01, and uCosminexus TP1/NET/Library 07-01.

Changes
The XA resource service can now be used to output the performance verification trace (prf trace).
With this modification, the following definitions and an operand have been added:
  • XAR performance verification trace definition
  • XAR resource service definition
    xar_prf_trace_level operand
The description of the maximum length of a definition line has been changed.
Functionality that allows the system to operate without using the system journal file (journal fileless mode) has been added.
With this addition, the following items have been added:
  • The jnl_fileless_option operand in the system common definition
  • Notes in the journal service definition and system journal service definition
  • The number of definition files that contain system service definitions
  • Notes on the atomic_update operand in the user service definition
  • The formula for estimating the amount of shared memory required on a node running in journal fileless mode
In addition, the description indicating that the XA resource service is unavailable in journal fileless mode has been added.
The functionality for setting a timeout for a thread waiting for a resource to be unlocked by another thread has been expanded.
With this expansion, the specifiable range for the thdlock_sleep_time operand in the following definitions has been changed:
  • System common definition
  • System service common information definition
Notes on specification have also been added.
In addition, the thdlock_sleep_time operand has been deleted from the user service definition and user service default definition.
The user authentication facility can now be used in Linux and AIX.
With this modification, the default value of the client_uid_check operand in the system common definition has been changed.
The name service can now be used to output the event trace.
With this modification, the nam_prf_trace_level operand has been added to the system common definition.
The process service can now be used to output an event trace.
With this modification, the explanation of the prc_prf_trace operand in the process service has been changed.
A specifiable range for the trn_tran_process_count operand in the transaction service definition that applies when the MCF service is used has been added.
A parallel access facility for system journal files has been added.
With this modification, the following operands and an option have been added to the system journal service definition:
  • jnl_max_file_dispersion operand
  • jnl_min_file_dispersion operand
  • -e option in the jnladdpf definition command
In addition, the explanations of the following operands and an option in the archive journal service definition have been changed:
  • jnl_max_file_dispersion operand
  • jnl_min_file_dispersion operand
  • -e option in the jnladdpf definition command
An audit log output facility has been added.
With this modification, the following operands have been added:

Log service definition:
  • log_audit_out
  • log_audit_path
  • log_audit_size
  • log_audit_count
  • log_audit_message

RAP-processing listener service definition:
  • log_audit_out_suppress
  • log_audit_message

RAP-processing client manager service definition:
  • log_audit_out_suppress
  • log_audit_message

User service default definition:
  • log_audit_out_suppress
  • log_audit_message

User service definition:
  • log_audit_out_suppress
  • log_audit_message
An explanation of the remote API facility has been added for the following items:

RAP-processing listener service definition:
  • rap_term_disconnect_time
  • rap_stay_watch_time
  • rap_stay_warning_interval
  • watch_time

System service definitions that can be changed at restart:
  • RAP-processing listener service definition
  • RAP-processing client manager service definition
In addition, the explanations of the following items have been changed:

RAP-processing listener service definition:
  • rap_connect_interval
  • rap_recovery_server

Notes on the RAP-processing listener service definition
Functionality that suppresses backing up of PRF trace files has been added.
With this modification, the prf_trace_backup operand has been added to the performance verification trace definition.
Functionality that allows the real-time statistics service to back up RTS log files has been added.
With this modification, the rts_log_file_backup operand has been added to the real-time statistics service definition.
Items that can be acquired by using the real-time statistics service have been added.
With this modification, the following operands have been added to the real-time statistics acquisition-item definition:
  • rts_scd_svc_scd_wait operand
  • rts_scd_svc_using_buf operand
  • rts_scd_parallel operand
Operation of the schedule service can now be specified on a service basis.
With this modification, the scdsvcdef definition command has been added to the following definitions:
  • User service definition
  • User service default definition
Notes that apply when the scdsvcdef definition command is specified in any of the following operands in the user service definition have also been added:
  • message_store_buflen operand
  • message_cell_size operand
In addition, the formula for calculating the memory for the scheduler in the formulas for calculating static shared memory for TP1/Server Base has been changed.
Functionality that dynamically loads service functions has been added.
With this modification, the UAP shared library name can now be specified for the service operand in the user service definition.
In addition, notes on the rtsput definition command has been added to the real-time statistics service definition.
In the Linux version, an attempt to output a message to syslog can now be retried if the attempt fails.
With this modification, the explanations of the following operands have been changed:
  • log_syslog_elist
  • log_syslog_elist_rint
Notes on specifying the time zone have been added.
Examples of defining the acquisition items for real-time statistics have been added.
RAP has been removed from the service group types that can be specified in the type operand.
Functionality that monitors the message queues remaining in the input queue has been added.
With this modification, the service group attribute definition has been added to the MCF manager definition.
The specifiable range for the mcfmsmsg definition command has been changed.
Functionality that can reuse a model definition when an application attribute definition is specified has been added.
With this modification, the -N option has been added to the mcfaalcap definition command in the MCF application definition.
The explanation of the -o option for the MCF definition object creation utility startup command has been changed.
The explanation of what is inherited has been changed for the following options:
  • -g option of the mcfmsts definition command
  • -v option of the mcfmsts definition command
  • -a option of the mcftsts definition command
A list of definitions that must be reviewed with regard to the changes to the OpenTP1 system has been added.
An explanation of the shared memory requirements when the prf_trace operand is specified in the system common definition has been added.
The method of calculating the amount of dynamic shared memory for TP1/Server Base when there is only a memory queue has been added.
Messages and problem identification codes that are output during definition checking have been added or changed.

The following table lists changes in the manual (3000-3-D52-20(E)) and product changes related to that manual for uCosminexus TP1/Server Base 07-01.

Changes
The following operands have been added:
  • rap_message_id_change_level operand in the RAP-processing listener service definition, user service default definition, and user service definition
  • user_command_online_tp1mngr_id operand in the system environment definition
Duplication of the node_id operand in the system common definition in the OpenTP1 system can now be checked.
With this modification, the name_nodeid_check_message operand has been added to the name service definition.
The MSDTC linkage facility, which enables transaction linkage on a two-phase commit basis between OpenTP1 and an application running on .NET Framework, has been added.
With this modification, the xar_msdtc_use operand has been added to the XA resource service definition.
The timeout for receiving the response to a service request in communication performed by the journal service can now be specified.
With this modification, the jnl_watch_time operand has been added to the journal service definition and global archive journal service definition.
The message transmission order and application startup order can now be selected.
With this modification, the -c option has been added to the mcfmuap definition command in the MCF manager definition.
Whether the values specified in definitions are appropriate for OpenTP1 operation can now be checked in detail.