システム・メッセージ: CMDTUXカタログ200-299


201	*ERROR: CLOPT parameter must be <= len* characters in length**
	Description	The value for `CLOPT` indicated by the arrow is greater than 256 characters in length.
	Action	Edit the configuration file such that all `CLOPT` parameters are less than or equal to 256 characters.
	See Also	`ubbconfig`(5)
203	*ERROR: Group name must be <= len* characters in length**
	Description	The `SRVGRP` value indicated by the arrow is greater than 30 characters in length.
	Action	Edit the configuration file such that all `SRVGRP` values are less than or equal to 30 characters in length.
	See Also	`ubbconfig`(5)
205	*ERROR: Group name grpname* not defined in GROUPS section*
	Description	The specified server group name grpname has not been defined in the GROUPS section of the configuration file.
	Action	Edit the configuration file such that the server group name is defined in the GROUPS section.
	See Also	`ubbconfig`(5)
207	ERROR: SRVID parameter must be >= 1 and <= 30000
	Description	The value for `SRVID` indicated by the arrow must be greater than or equal to 1 and less than or equal to 30000.
	Action	Specify a value for `SRVID` that is greater than or equal to 1 and less than or equal to 30000.
	See Also	`ubbconfig`(5)
209	*ERROR: RQADDR parameter must be <= len* characters in length**
	Description	The value for `RQADDR` indicated by the arrow must be less than or equal to 30 characters in length.
	Action	Specify a value for `RQADDR` that is less than 31 characters in length.
	See Also	`ubbconfig`(5)
211	ERROR: RQPERM parameter must be >= 1 and <= 0777
	Description	The value for `RQPERM` indicated by the arrow must be between 0001 and 0777, inclusive.
	Action	Specify a value for `RQPERM` that is between 0001 and 0777, inclusive.
	See Also	`ubbconfig`(5)
213	ERROR: RPPERM parameter must be >=1 and <= 0777
	Description	The value for `RPPERM` indicated by the arrow must be between 0001 and 0777, inclusive.
	Action	Specify a value for `RPPERM` that is between 0001 and 0777, inclusive.
	See Also	`ubbconfig`(5)
215	ERROR: MAXGEN parameter must be >= 1 and < 256
	Description	The value given for `MAXGEN` indicated by the arrow is invalid because it is not between 1 and 255, inclusive.
	Action	Specify a value for `MAXGEN` that is between 1 and 255, inclusive.
	See Also	`ubbconfig`(5)
217	ERROR: GRACE parameter must be >= 0
	Description	The value for `GRACE` indicated by the arrow is invalid because it is not greater than or equal to 0.
	Action	Specify a value for `GRACE` that is greater than or equal to 0.
	See Also	`ubbconfig`(5)
219	ERROR: SEQUENCE parameter must be > 0 and < 10000
	Description	The value given for `SEQUENCE` indicated by the arrow is invalid because it is not between 1 and 9999, inclusive.
	Action	Specify a value for `SEQUENCE` that is between 1 and 9999, inclusive.
	See Also	`ubbconfig`(5)
220	*ERROR: Duplicate SERVICES section**
	Description	There is more than one SERVICES section of the configuration file defined.
	Action	Edit the configuration file such that there is only one SERVICES section.
	See Also	`ubbconfig`(5)
221	*ERROR: GROUPS section must appear before SERVICES section*
	Description	The SERVICES section is defined before the GROUPS section in the configuration file.
	Action	Edit the configuration file such that the GROUPS section is defined before the SERVICES section.
	See Also	`ubbconfig`(5)
222	*ERROR: Could not initialize sort of SERVICES section**
	Description	An internal error occurred while attempting to sort the SERVICES section during `tmloadcf`.
	Action	Attempt to load the configuration again via `tmloadcf`. If the error occurs again, contact Oracle TUXEDO system Technical Support.
	See Also	`ubbconfig`(5), `tmloadcf`(1)
223	*ERROR: Could not turnaround sort of SERVICES section**
	Description	An internal error occurred while attempting to sort the SERVICES section of the configuration file during `tmloadcf`.
	Action	Attempt to load the configuration again via `tmloadcf`. If the error occurs again, contact Oracle TUXEDO system Technical Support.
	See Also	`ubbconfig`(5), `tmloadcf`(1)
224	*ERROR: Couldn't retrieve data from SERVICES sort**
	Description	An internal error occurred while attempting to sort the SERVICES section of the configuration file during `tmloadcf`.
	Action	Attempt to load the configuration again via `tmloadcf`. If the error occurs again, contact Oracle TUXEDO system Technical Support.
	See Also	`ubbconfig`(5), `tmloadcf`(1)
226	*ERROR: Service name must be <= len* characters in length**
	Description	The `SVCNM` parameter indicated by the arrow is invalid because it is more than 15 characters in length.
	Action	Specify a service name value that is less than or equal to 15 characters in length.
	See Also	`ubbconfig`(5)
228	*ERROR: Service service_name* can't have two different ROUTING values**
	Description	The indicated service name has two different routing criteria associated with it.
	Action	Edit the configuration file such that if multiple ROUTING entries exist for the same service name but have different `SRVGRP` parameters, the `ROUTING` parameter must be the same for all of these entries.
	See Also	`ubbconfig`(5)
229	エラー: メモリーの割当てに失敗しました
	説明	`malloc()`を使用してオペレーティング・システムから動的にメモリーを割り当てようとしましたが、`UBBCONFIG`ファイルのSERVERSセクションに保持される情報を追跡するための表の設定中に失敗しました。
	アクション	マシンのメモリー量およびプロセスによって使用されるメモリー量に対して、オペレーティング・システム・パラメータが正しく設定されていることを確認してください。マシンのメモリー使用量を減らすか、マシンの物理メモリー量を増やしてください。

230	エラー: メモリーの割当てに失敗しました
	説明	`malloc()`を使用してオペレーティング・システムから動的にメモリーを割り当てようとしましたが、`UBBCONFIG`ファイルのSERVICESセクションに保持される情報を追跡するための表の設定中に失敗しました。
	アクション	前出のメッセージ229を参照してください。

231	エラー: メモリーの割当てに失敗しました
	説明	`malloc()`を使用してオペレーティング・システムから動的にメモリーを割り当てようとしましたが、`UBBCONFIG`ファイルのSERVICESセクションに保持される情報を追跡するための表の設定中に失敗しました。
	アクション	前出のメッセージ229を参照してください。

232	*ERROR: Need different SRVGRP for the SERVICE svcname.*
	Description	The same service has been specified more than once, but the `SRVGRP` parameter is absent.
	Action	Edit the `UBBCONFIG` file and specify different `SRVGRP` entries for each `SVCNAME` defined.
	See Also	`ubbconfig`(5)
233	*ERROR: SERVICE svcname* can't have SRVGRP srvgrp on different entry.**
	Description	The same service has been specified more than once, using the same `SRVGRP` value.
	Action	Edit the `UBBCONFIG` file and specify different `SRVGRP` entries for each `SVCNAME` defined.
	See Also	`ubbconfig`(5)
235	エラー: メモリーの割当てに失敗しました
	説明	`tmloadcf`コマンドは、`malloc()`ライブラリ呼出しを使用して、構成ファイルの解析に使用する内部メモリーを取得します。この`malloc()`呼出しのいずれかが失敗した場合は、使用可能なメモリーがなかったことを意味します。メモリーまたはスワップの領域の空き容量が限られているマシンに対して、構成ファイルが大きすぎた可能性があります。
	アクション	マシンにかかる負荷が軽減されてから、再び`tmloadcf`を実行してください。`DEFAULT`パラメータを活用して各セクションのグローバル・オプションを設定することで、構成ファイルのサイズを小さくしてください。
	関連項目	`tmloadcf`(1)、`ubbconfig`(5)
237	*ERROR: Failure during input to sort of SERVICES section**
	Description	The `tmloadcf` command sorts the entries in the SERVICES section by service name. During this processing, an internal error occurred. Since sort processing uses temporary memory and disk space, the most common cause of sort failure is if these resources run out. The temporary files used for sorting are usually placed in `/usr/tmp` or `/tmp`.
	Action	Check that there is available temporary disk space in `/usr/tmp` and `/tmp`. Try running the command again when the system is less heavily loaded.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
239	*ERROR: The SRVGRP parameter must be <= len* characters**
	Description	The `SRVGRP` parameter in the configuration file must be a string of 30 or fewer characters.
	Action	Choose a `SRVGRP` value that is no more than 30 characters and make sure it matches a group name in the GROUPS section.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
241	*ERROR: Group name group_name* must match a name from the GROUPS section*
	Description	The `SRVGRP` parameter of the SERVERS section in the configuration file does not match an entry in the GROUPS section. This can be due to a direct error here, or a previous error while compiling the group name entry.
	Action	Correct the `SRVGRP` entry, or the group name entry that it is supposed to match.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
243	*ERROR: BUFTYPE parameter must be <= len* characters**
	Description	The `BUFTYPE` parameter in the configuration file must be a string of 256 or fewer characters.
	Action	Shorten the `BUFTYPE` parameter, and make sure it matches a buffer type that is in the Oracle TUXEDO system buffer Type Switch.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
245	ERROR: TRANTIME parameter must be >= 0 and < 2147483648
	Description	The `TRANTIME` parameter was outside the allowable numeric range.
	Action	Specify a value that is 0 or greater and less than 2,147,483,648.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
247	*ERROR: ROUTING routingname must be <= len characters**
	Description	The routingname of the ROUTING section of the configuration file must be <= 15 characters.
	Action	Specify a value that is less than or equal to 15 characters.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
249	ERROR: LOAD parameter must be >= 1 and <= 32767
	Description	The `LOAD` parameter in the SERVICES section of the configuration file must be within the proper range of values.
	Action	Specify a value that is between 1 and 32,767.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
251	ERROR: PRIO parameter must be >= 1 and <= 100
	Description	The `PRIO` parameter in the SERVICES section of the UBBCONFIG must be within the proper range of values.
	Action	Specify a value that is between 1 and 100, inclusive.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
252	*ERROR: Duplicate ROUTING section present**
	Description	A second ROUTING section was encountered in the configuration file. Only one is allowed.
	Action	Place all routing entries within a single ROUTING section.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
253	*ERROR: The GROUPS section must appear before the ROUTING section*
	Description	The ROUTING section appeared in the configuration file before any GROUPS section appeared. This could be due to the sections being out of order or missing.
	Action	Make sure that the GROUPS section appears before the ROUTING section.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
255	*ERROR: Routing name must be <= len* characters**
	Description	The `ROUTING` identifier must be <= 15 characters.
	Action	Specify a value that is less than or equal to 15 characters.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
256	ERROR: FIELD parameter missing in ROUTING entry routingname*
	Description	Each entry in the ROUTING section of the configuration file must have a `FIELD` parameter.
	Action	Specify a `FIELD` value for each entry that is the name of the routing field.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
257	ERROR: RANGES parameter missing in ROUTING entry routingname*
	Description	Each entry in the ROUTING section of the configuration file must have a `RANGES` parameter.
	Action	Specify a `RANGES` value for each entry that specifies the ranges and associated server groups for the routing field.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
258	ERROR: BUFTYPE parameter missing in ROUTING entry routingname*
	Description	Each entry in the ROUTING section of the configuration file must have a `BUFTYPE` parameter.
	Action	Specify a `BUFTYPE` value that is a list of types and subtypes of data buffers for which this routing entry is valid.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
260	*ERROR: FIELD parameter must be <= len* characters in length**
	Description	The Field name in the `ROUTING` section must be less than 30 characters in length.
	Action	Specify a `FIELD` name that is less than 30 characters long.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
262	*ERROR: RANGES parameter must be <= len* characters**
	Description	The `RANGES` string in the ROUTING section was greater than 256 characters in length.
	Action	Shorten the `RANGES` string and re-load the configuration file.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
264	*ERROR: BUFTYPE parameter must be <= len* characters**
	Description	The `BUFTYPE` parameter was greater than 256 characters.
	Action	Shorten the `BUFTYPE` parameter and re-load the configuration file.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
265	ERROR: More than one NETWORK section is present
	Description	A `UBBCONFIG` file can only have one NETWORK section. More than one NETWORK section was encountered while processing the `UBBCONFIG` file.
	Action	Check the `UBBCONFIG` file for the NETWORK keyword. It is possible that an editing error left an extra copy of that line.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
266	*ERROR: The MACHINES section must precede the NETWORK section*
	Description	The NETWORK section of the `UBBCONFIG` file was encountered before any MACHINES section. The information in the MACHINES section is needed to process the NETWORK section.
	Action	Check if a MACHINES section is in the `UBBCONFIG` file. If it is, place it before the NETWORK section.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
272	*ERROR: NETWORK LMID lmid does not appear in MACHINES section*
	Description	The `LMID` identifier lmid in the NETWORK section of the `UBBCONFIG` file did not appear in the MACHINES section. The `LMID` parameter is the identifier at the beginning of the line, and does not appear with the keyword `LMID`.
	Action	Make sure that the `LMID` is spelled correctly, and has a matching entry in the MACHINES section.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
274	ERROR: NADDR parameter missing in NETWORK entry lmid*
	Description	The entry for lmid in the NETWORK section has no `NADDR` parameter. This parameter is required.
	Action	Add a `NADDR` parameter to the NETWORK entry.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
276	*ERROR: NADDR parameter must be <= len* characters in length**
	Description	The `NADDR` parameter in the NETWORK section of the `UBBCONFIG` file must be <= len characters.
	Action	Shorten the `NADDR` parameter and re-load the configuration.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
278	ERROR: There is an invalid hexadecimal digit in the NADDR parameter
	Description	The `NADDR` parameter in the NETWORK section of the `UBBCONFIG` file was specified as a hexadecimal number (starting with 0x or \x), but a non-hexadecimal character was encountered in the string.
	Action	Enter hexadecimal characters in the `NADDR` parameter and re-load the configuration.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
280	ERROR: NADDR parameter must contain an even number of hex digits.
	Description	The `NADDR` parameter in the NETWORK section of the `UBBCONFIG` file was specified as a hexadecimal number (starting with 0x or \x). This requires that there be an even number of characters following the prefix.
	Action	Correct the `NADDR` to have an even number of hexadecimal characters and re-load the configuration.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
282	ERROR: BRIDGE parameter must be an absolute pathname
	Description	The `BRIDGE` parameter in the NETWORK section of the `UBBCONFIG` file must be an absolute pathname of the network device. This means it must begin with a '/' character.
	Action	Replace the current `BRIDGE` parameter with the full pathname of the device, for example, "`/dev/tcp`".
	See Also	`tmloadcf`(1), `ubbconfig`(5)
284	*ERROR: NLSADDR parameter must be <= len* characters**
	Description	The `NLSADDR` parameter in the NETWORK section of the `UBBCONFIG` file must be <= len characters.
	Action	Change the `NLSADDR` parameter to be 78 characters or less and reload the configuration.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
286	ERROR: There is an invalid hexadecimal digit in the NLSADDR parameter
	Description	The `NLSADDR` parameter in the NETWORK section of the `UBBCONFIG` file was specified as a hexadecimal number (starting with 0x or \x), but a non-hexadecimal character was encountered in the string.
	Action	Enter hexadecimal characters in the `NLSADDR` parameter and re-load the configuration.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
288	ERROR: NLSADDR parameter must contain an even number of hex digits
	Description	The `NLSADDR` parameter in the NETWORK section of the `UBBCONFIG` file was specified as a hexadecimal number (starting with 0x or \x). This requires that there be an even number of characters following the prefix.
	Action	Correct the `NLSADDR` to have an even number of hexadecimal characters and re-load the configuration.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
290	ERROR: NETID parameter must be >=0 and <=256
	Description	The `NETID` is an undocumented parameter in the `UBBCONFIG` file, used for internal testing purposes. It should not be used by the end user.
	Action	Remove the `NETID` parameter or change its value to be in the range 1-255.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
291	*ERROR: Failure opening TUXCONFIG section sectionname* (vtoc_error=vtoc_errno)**
	Description	The `TUXCONFIG` file is a binary file in the Oracle `TUXEDO VTOC` format. Each section of the `UBBCONFIG` file (RESOURCES, MACHINES, etc.) is stored as a separate table in the `TUXCONFIG` file. While trying to update the `TUXCONFIG` file, `tmloadcf` got an error trying to open the specified sectionname. The section of the `TUXCONFIG` and a low level error code are printed in this message.
	Action	If the `TUXCONFIG VTOC` is only being used to hold the `TUXCONFIG` tables (and not the `TLOG` or a Oracle `TUXEDO/D` database), then the first thing to try is to recreate a new `TUXCONFIG`. If the `TUXCONFIG` is a UNIX file, simply remove it. If it is stored on a raw disk, erase it by entering: echo " " >$TUXCONFIG If the error persists, check for disk-type error conditions that might cause problems writing to files. Finally, contact Oracle TUXEDO system Technical Support, making sure to have the vtoc_errno that was printed in the error message.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
292	*ERROR: Error writing RESOURCES section of the TUXCONFIG file (vtoc_errno= vtoc_errno)**
	Description	The `TUXCONFIG` file is a binary file in the Oracle `TUXEDO VTOC` format. Each section of the `UBBCONFIG` file (RESOURCES, MACHINES, etc.) is stored as a separate table in the `TUXCONFIG` file. An error occurred while trying to write to the RESOURCES section of the `TUXCONFIG`.
	Action	If the `TUXCONFIG` file is a UNIX file, the file system that it is in should be checked to see if it has enough free space. The file should be checked to see if its permissions allow writing. If the `TUXCONFIG VTOC` is being used only to hold the `TUXCONFIG` tables (and not the `TLOG` or a Oracle `TUXEDO/D` database), then the first thing to try is to recreate a new `TUXCONFIG`. If the `TUXCONFIG` is a UNIX file, simply remove it. If it is stored on a raw disk, erase it by entering: echo " " >$TUXCONFIG If the error persists, check for disk-type error conditions that might cause problems writing to files. Finally, contact Oracle TUXEDO system Technical Support, making sure to have the vtoc_errno that was printed in the error message.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
293	*ERROR: Failed to write the TUXCONFIG file (vtoc_errno=vtoc_errno).*
	Description	The `TUXCONFIG` file is a binary file in the Oracle `TUXEDO VTOC` format. Each section of the `UBBCONFIG` file (RESOURCES, MACHINES, etc.) is stored as a separate table in the `TUXCONFIG` file. An error occurred while writing to a section of the `TUXCONFIG`.
	Action	If the `TUXCONFIG` file is a UNIX file, the file system that it is in should be checked to see if it has enough free space. The file should be checked to see if its permissions allow writing. If the `TUXCONFIG VTOC` is being used to hold only the `TUXCONFIG` tables (and not the `TLOG` or a Oracle `TUXEDO/Q` database), then the first thing to try is to recreate a new `TUXCONFIG`. If the `TUXCONFIG` file is a UNIX file, simply remove it. If it is stored on a raw disk, erase it by entering: echo " " >$TUXCONFIG If the error persists, check for disk-type error conditions that might cause problems writing to files. Finally, contact Oracle TUXEDO system Technical Support, making sure to have the vtoc_errno that was printed in the error message.
	See Also	`tmloadcf`(1), `ubbconfig`(5)