---

Appendix D. Error Messages

SNACRM Messages

The following messages are logged to the USERLOG file with a 90xx prefix and are also written to the stderr file. For any SNACRM messages not listed, contact BEA Connect Technical Support. The SNACRM error messages are listed in alphabetical order.

ERROR	Allocation Failure for <trancode> on <remotesysid>: <error>
	Description	An allocation error occurred.
	Action	The reason for the failure is described by <error>. Correct the problem with configuration or application.
	See Also	None
ERROR	Attempt to connect as second master refused!
	Description	A second GWSNAX is attempting to connect to the SNACRM as a master gateway. Only one master gateway is allowed.
	Action	Ensure that multiple TUXEDO configurations do not use the same SNACRM address.
	See Also	None
ERROR	Attempt to connect with incorrect group name refused!
	Description	The group name in the DMCONFIG file does not match the group name specified in the SNACRM command line.
	Action	Correct the group name that is in error and restart.
	See Also	None
ERROR	Attempt to send <nnnnn> bytes (> 32767)
	Description	The length of a send request exceeded 32767 (including overhead).
	Action	Check application program and correct.
	See Also	None
ERROR	CNOS Notification Received for unknown partner!
	Description	Multiple instances of the SNACRM may be using the same local LU.
	Action	Ensure that multiple TUXEDO configurations do not use the same local LU.
	See Also	None
ERROR	Configuration change on <linkref> requires cold start
	Description	Attempting to do a warm start after changing the domain configuration.
	Action	Change start type to "COLD" and restart.
	See Also	None
ERROR	Conversation terminated without confirm for context <correlator>
	Description	Sync level 2 conversation was terminated without confirm.
	Action	Check application program and correct.
	See Also	None
ERROR	Exchange logs failed with <linkref>
	Description	An error occurred during the exchange logs process.
	Action	Run CRMLOGS to examine the SNACRM log file. Cold start the TUXEDO application.
	See Also	None
ERROR	Exchange Logs Rejected for <remotesysid>. Restart Type or Log Name Mismatch
	Description	The log files for the SNACRM have been incorrectly modified.
	Action	Run CRMLOGS to examine the SNACRM log file. Cold start the TUXEDO application.
	See Also	None
WARNING	Inbound Exchange Logs Rejected for <remotesysid>
	Description	Link not configured for sync level 2.
	Action	None. This message is for information only.
	See Also	None
ERROR	Invalid cold start received from <remotesysid> Unrecovered Local transactions are pending.
	Description	Attempting to cold start host while warm starting TUXEDO.
	Action	Run CRMLOGS to examine the SNACRM log file. Cold start the TUXEDO application.
	See Also	None
ERROR	Invalid warm start received from <remotesysid>. Unknown log name.
	Description	The log files for the SNACRM have been incorrectly modified.
	Action	Run CRMLOGS to examine the SNACRM log file. Cold start the TUXEDO application.
	See Also	None
WARNING	Link not configured for sync-level 2.
	Description	This warning results when the inbound exchange log is rejected.
	Action	None
	See Also	None
ERROR	Link refers to undefined APPC stack!
	Description	The stackref in the link configuration is incorrect.
	Action	Correct the stackref that is in error, run dmloadcf, and restart.
	See Also	None
ERROR	Mixed Heuristic on link <linkref>
	Description	One side has reported committed while the other side has reported aborted.
	Action	Check the ULOG for any additional messages.
	See Also	None
ERROR	No Available Session on link <linkref> for context <correlator>
	Description	Maximum number of sessions has been exceeded.
	Action	Check session limits in DMCONFIG, stack configuration, CICS or VTAM. Increase session limits if necessary.
	See Also	None
ERROR	Missing send last from host <ATMI r/r> for context <correlator>
	Description	Host application did not issue send last during an out-bound request/ response service. The host application may have abended.
	Action	Check application program and correct.
	See Also	None
ERROR	No blob with recovery request. Tranid = <tctxt> dropped
	Description	Attempting to warm start after the SNACRM BLOBLOG has been modified.
	Action	Change start type to "COLD" and restart.
	See Also	None
ERROR	Requested Synclevel not supported by link <linkref> for context <correlator>
	Description	Attempted to issues a request at sync level 2 on a sync level 0 link.
	Action	Correct application.
	See Also	None
ERROR	Server <stackref> Creation Failed
	Description	SNACRM was unable to instantiate the stack object due to an error.
	Action	Check for additional messages in stderr. Could be that the shared library for the stack or the stack interface could not be loaded due to an incorrect library path.
	See Also	None
ERROR	Service Request at SL=2 Rejected on pending link <linkref>
	Description	An attempt to start a new sync level 2 request has been received and the Link is currently processing recovery information.
	Action	Wait until recovery is complete to request sync level 2 services.
	See Also	None
ERROR	Server <stackref> Failed, Code = <returncode>
	Description	SNACRM received a bad return code from the stack start-up.
	Action	The <returncode> is the value returned by the SNA Stack software. Check the status of the stack and the configuration of the stack and the DMCONFIG. Note: You must manually kill the SNACRM process.
	See Also	None
ERROR	Unable to start recovery task for link <linkref>
	Description	An error occurred during the warm start of TUXEDO.
	Action	Cold start the TUXEDO application.
	See Also	None
ERROR	Unknown tranid = <tctxt> dropped
	Description	Recovery was requested by TUXEDO on a transaction that was already forgotten by the SNACRM.
	Action	None. This message for information only.
	See Also	None
ERROR	Undefined Remote LU on link <linkref>
	Description	The remote LU does not exist as defined.
	Action	Check the DMCONFIG file and the stack configuration and correct the mismatch.
	See Also	None
ERROR	Unable to start session on link <linkref>. <reason>
	Description	Link activation failure due to SNA error.
	Action	<reason> is the description of the stack return code. Determine the cause and correct it.
	See Also	None
ERROR	Unable to initialize link <linkref>. <reason>
	Description	Link initialization failure due to SNA error.
	Action	<reason> is the description of the stack return code. Determine the cause and correct it.
	See Also	None
ERROR	Unrecovered tranid=<tctxt> blob dropped. Presumed forgotten.
	Description	SNACRM found recovery information but GWSNAX did not request recovery during warm start.
	Action	None
	See Also	None

GWSNAX Messages

For any GWSNAX messages not listed, contact your BEA Connect Technical Support.

3051 ERROR	Exceed local transaction limit<max_tran>!
	Description	Number of concurrent transactions using this domain gateway exceeded the configured limit.
	Action	Check the dmconfig file for MAXTRAN parameter, this number is the limit. If MAXTRAN is not specified, then check the ubbconfig file for MAXGTT parameter. In the later case MAXGTT is the limit. Modify the limit if necessary.
	See Also	None
3053 ERROR	Create transaction tree node failed!
	Description	Failed to create transaction tree node object. The reasons can be either because memory allocation failed, or the configured transaction limit reached.
	Action	Check the prior messages in the USERLOG. If the cause is the memory allocation failure, then update the system and/or system configuration. If the cause is the limit reached, then may need to modify the dmconfig or ubbconfig.
	See Also	None
3067 ERROR	Cannot set remote domain for transaction!
	Description	Several possibilities for this failure. The first one is unable to get shared memory lock, the other one is it reached the configured limit for number of remote domains that can get involved in the same transaction. This limit is specified in the MAXRDTRAN in the dmconfig.
	Action	Check the configuration, and compare with number of remote domains which may get involved in the transaction. Update the configuration file if necessary. If the cause is not in the configuration file, then contact your BEA Connect Technical Support.
	See Also	None
3071 ERROR	Defined transaction limit max_tran reached!
	Description	The number of concurrent transactions using this domain gateway exceeded the limit.
	Action	If MAXTRAN is not specified, then check the ubbconfig file for MAXGTT parameter. In the later case MAXGTT is the limit. Modify the limit if necessary.
	See Also	None
3085 ERROR	Transaction node is de-allocated because of ABEND!
	Description	Informational. Detected ABEND condition or received ABEND event from SNACRM causing the node object to be destroyed.
	Action	No action need to be taken.
	See Also	None
3124 ERROR	Send verb <verb_id> to snacrm failed!
	Description	Failed to send SNACRM verb through network connection.
	Action	Check the network connection and determine if the SNACRM is still alive.
	See Also	None
3127 ERROR	Send verb <verb_id> to SNACRM failed!
	Description	Failed to send SNACRM verb through network connection.
	Action	Check the network connection and determine if the SNACRM is still alive.
	See Also	None
3130 ERROR	Send verb <verb_id> to SNACRM failed!
	Description	Failed to send SNACRM verb through network connection.
	Action	Check the network connection and determine if the SNACRM is still alive.
	See Also	None
3146 ERROR	Unable to find SNACRM for superior remote domain<rdom_name>
	Description	Failed to find remote domain definition in the configuration in order to get SNACRM identification.
	Action	Check whether there is a configuration change between the boot that would modify or remove the remote definition from dmconfig. If there is no change, then contact your BEA Connect Technical Support.
	See Also	None
3149 ERROR	Could not create transaction tree structure!
	Description	Unable to allocate a transaction tree node structure to represent the transaction recovery object.
	Action	Check the configuration to determine if there is a change of MAXTRAN in dmconfig and/or a change of MAXGTT in ubbconfig. This condition may occur if there is a decrease in the number of transactions allowed between boot-ups while many transactions must be recovered. If no change is made, then contact your BEA Connect Technical Support.
	See Also	None
3502 ERROR	Buffer type <type,subtype> not defined in the buffer type switch!
	Description	The buffer type associated with the inbound message is not specified in the type switch.
	Action	Check the application, and configuration about which buffer type it is using. GWSNAX only supports standard TUXEDO buffer types over the domain gateway. If the buffer type is VIEW, VIEW32, FML, or FML32, then also check the environmental variable VIEWFILES, VIEWFILES32, VIEWDIR, VIEWDIR32.
	See Also	None
3505 ERROR	Input buffer too big<buflen>!
	Description	Input buffer exceeding 32K limit allowed for SNA Gateway.
	Action	Check the application, if necessary contact your BEA Connect Technical Support.
	See Also	None
3506 ERROR	Missing subtype specification for buftype
	Description	The subtype specification is required for this buffer type.
	Action	Check the application.
	See Also	None
3511 ERROR	Missing subtype for FML type buffer!
	Description	Missing subtype specification needed for decoding for FML buffer type.
	Action	Check the application, and check environmental variable setting of VIEWDIR, VIEWDIR32, VIEWFILE, VIEWFILE32. If necessary contact your BEA Connect Technical Support.
	See Also	None
3515 ERROR	Convert buffer type<buftype,bufstype> failed, convert failure!
	Description	Conversion from C structure to fielded buffer failed.
	Action	Check memory situation, if the error did not due to memory allocation failure then check the whether the actual data is larger than the definition.
	See Also	None
3517 ERROR	Missing subtype definition for FML32 buffer type!
	Description	FML32 buffer subtype is missing from domain configuration in either local or remote service definition.
	Action	Correct the domain configuration.
	See Also	None
3519 ERROR	Convert FML32 buffer type<buftype,bufstype> failed, convert failure!
	Description	Conversion from FML32 buffer type to C structure failed.
	Action	Check whether the buffer type definition is too large, and whether the view name can be found in the file specified by VIEWDIR32, VIEWFILE3. Also, check the view syntax.
	See Also	None
3521 ERROR	Convert FML32 buffer with subtype<bufstype> failed!
	Description	Conversion from C structure to FML32 failed.
	Action	Check whether the data is too large.
	See Also	None
3523 ERROR	Failed to convert for FML buffer <bufstype>, exceeding limit!
	Description	Failed to convert the FML buffer; the required buffer size to process the conversion exceeds the limit.
	Action	Check the view file definition for this FML buffer subtype.
	See Also	None
3524 ERROR	Failed to convert for FML32 buffer <bufstype>, exceeding limit!
	Description	Failed to convert the FML32 buffer, the required buffer size to process the conversion exceeds the limit.
	Action	Check the view file definition for this FML32 buffer subtype.
	See Also	None
3525 ERROR	Fail to retrieve remote service definition!
	Description	Could not find remote service definition in the shared memory.
	Action	Check the /Domain configuration using dmunloadcf command to check the remote service definition. If error found, then correct the dmconfig and reload it. If no error found contact your BEA Connect Technical Support.
	See Also	None
3527 ERROR	Must specify subtype for <buftype>
	Description	Missing specification for the buffer subtype.
	Action	Check the /Domain configuration for SNA gateway. If no error found in the configuration, contact your BEA Connect Technical Support.
	See Also	None
3529 ERROR	Convert buffer type <buftype> with subtype <bufstype> failed<rc=Ferror>!
	Description	Conversion of VIEW or VIEW32 data buffer to target record type failed.
	Action	Check the error code in the message, and make any correction according to the error code suggested. If nothing is wrong, then contact your BEA Connect Technical Support.
	See Also	None
3530 ERROR	Convert buffer type buftype with subtype bufstype failed<rc=Ferror>!
	Description	Convert VIEW or VIEW32 data buffer to target record type failed because it's length exceeds the limit.
	Action	Check the view definition.
	See Also	None
3534 ERROR	Convert FML buffer with subtype <bufstype> failed<Ferror=rc>!
	Description	Conversion of FML buffer to C structure failed with reason code.
	Action	Check the reason code, and make any correction if necessary. If no error can be found, contact your BEA Connect Technical Support.
	See Also	None
3536 ERROR	Convert FML buffer with subtype <bufstype> failed<Ferror=rc>!
	Description	Conversion FML buffer to C structure failed with reason code.
	Action	Check the reason code, and make any correction if necessary. If no error can be found, contact your BEA Connect Technical Support.
	See Also	None
3538 ERROR	FML32 buffer type requires subtype to be specified!
	Description	The required buffer type is not specified.
	Action	Do a dmunloadcf to find whether the configuration for the service has missing subtype for FML32 buffer type, and correct it. After the correction, reload the SNA gateway.
	See Also	None
3540 ERROR	Convert FML32 buffer with subtype <bufstype> failed<Ferror=rc>!
	Description	Conversion of FML32 buffer to C structure failed with reason code.
	Action	Check the reason code, and make any correction if necessary. If no error can be found, contact your BEA Connect Technical Support.
	See Also	None
3542 ERROR	Convert FML32 buffer with subtype <bufstype> failed<Ferror=rc>!
	Description	Conversion of FML32 buffer to C structure failed with reason code.
	Action	Check the reason code, and make any correction if necessary. If no error can be found, contact your BEA Connect Technical Support.
	See Also	None
5021 ERROR	Encode reply failed!
	Description	Failed to encode reply message data to SNACRM.
	Action	Look into the USERLOG for prior failure message which gives more detailed description of the reason why it failed. The most common reason is the buffer subtype not specified or not found. Check the /Domain configuration for OUTBUFTYPE of the failed service response.
	See Also	None
5023 ERROR	Could not get transaction
	Description	Failed to associate a transactional ACALL service request to a transaction object.
	Action	The most likely reasons for this failure are, exceeding local configured limit, and memory allocation failed to create the transaction object. First check the prior failure message to identify the real cause of the failure. If the failure is for local configuration limit exceeded, then check whether the application is licensed to do transactions, check the DMCONFIG file for MAXTRAN, and check that SYNC LEVEL is set to 2 for remote domain. If the failure is caused by memory allocation failure, then check the system memory configuration.
	See Also	None
5024 ERROR	Could not get API
	Description	The API information for the remote service is incorrect.
	Action	Check the DMCONFIG for any API not configured correctly. If everything looks fine, contact your BEA Connect Technical Support.
	See Also	None
5025 ERROR	Could not get transaction
	Description	Failed to associate a transactional CONNECT service request to a transaction object.
	Action	Most likely reason for this failure are, exceeding local configured limit, and memory allocation failed to create the transaction object. First check the prior failure message to identify the real cause of the failure. If the failure is for local configuration limit exceeded, then check if the application is licensed to do transaction, check the DMCONFIG file for MAXTRAN, and check that SYNC LEVEL is set to 2 for remote domain. If the failure is caused by memory allocation failure, then check the system memory configuration.
	See Also	None
5026 ERROR	Could not get API
	Description	The API information for the remote service is incorrect.
	Action	Check the DMCONFIG for any API not configured correctly. If everything looks fine, contact your BEA Connect Technical Support.
	See Also	None
5027 ERROR	Could not get API
	Description	The API information for the remote service is incorrect.
	Action	Check the DMCONFIG for any API not configured correctly. If everything looks fine, contact your BEA Connect Technical Support.
	See Also	None
5029 ERROR	Link status down for remote domain <rdom>
	Description	The link status for the remote domain is down.
	Action	Check whether the stack is up, and then check that the session between the stack provider and CICS is up.
	See Also	None
5030 ERROR	Link status pending for remote domain rdom
	Description	The link status for the remote domain is pending.
	Action	The transaction recovery is still in progress, wait a while before sending request to remote domain.
	See Also	None
5031 ERROR	Transaction not allowed, request rejected!
	Description	Failed to send ACALL request to remote domain because transaction is not allowed in the current configuration.
	Action	Check the following 3 things, first whether the GWSNAX is licensed to do transaction; second check whether the DMCONFIG file is configured to do transaction; third check whether the remote domain is configured to do SYNC level 2 transaction.
	See Also	None
5032 ERROR	Transaction not allowed, request rejected!
	Description	Failed to send CONNECT request to remote domain because the transaction is not allowed in the current configuration.
	Action	Check the following 3 things, first whether the GWSNAX is licensed to do transaction; second check whether the DMCONFIG file is configured to do transaction; third check whether the remote domain is configured to do SYNC level 2 transaction.
	See Also	None
5034 ERROR	Allocate context failed!
	Description	Failed to allocate ACALL request context.
	Action	Check any prior message to tell the real reason of failure. The most common reason for failure is memory allocation failed.
	See Also	None
5043 ERROR	Trans Event Error
	Description	Failed to find transaction object using TCTXT which is specified in the SNACRM_QUERY_SVC_TYPE. This will cause GWSNAX to shut down.
	Action	This could be a stale inbound request not cleaned up by SNACRM, contact your BEA Connect Technical Support.
	See Also	None
5050 ERROR	SHUTDOWN message received, shutdown gateway!
	Description	Gateway GWSNAX received SNACRM_SHUTDOWN message from SNACRM, and will shut down immediately.
	Action	Check any problem encountered in SNACRM and contact your BEA Connect Technical Support.
	See Also	None
5062 ERROR	Failed to find local service<resource> definition!
	Description	The gateway GWSNAX failed to find local service in the configuration specified in the SNACRM_QUERY_SVC_TYPE message received from SNACRM.
	Action	Check the DMCONFIG for any missing definition of the local service. If not, then contact your BEA Connect Technical Support.
	See Also	None
5065 ERROR	Enter shutdown
	Description	Failed to send SNACRM_QUERY_SVC_TYPE response to SNACRM.
	Action	Check any communication problem between GWSNAX and SNACRM.
	See Also	None
5067 ERROR	Decode inbound ACALL request failed
	Description	Decode data in the SNACRM_ACALL request from SNACRM failed.
	Action	Check for prior error message, and handle it accordingly.
	See Also	None
5068 ERROR	Could not get FUNC
	Description	Failed to get FUNCTION specification from configuration, or the FUNCTION specification in the configuration is not supported.
	Action	Check the DMCONFIG configuration for the service.
	See Also	None
5069 ERROR	Could not get FUNC
	Description	Failed to get FUNCTION specification from configuration, or the FUNCTION specification in the configuration is not supported.
	Action	Check the DMCONFIG configuration for the service.
	See Also	None
5070 ERROR	Failed in security checking for RRCORR<svcReqCorr>!
	Description	Security checking failed for the inbound ACALL request.
	Action	Check for prior failure message to identify real cause of security failure.
	See Also	None
5073 ERROR	Could not get API
	Description	Failed to retrieve API information from the configuration, or retrieved API information is not supported for inbound request.
	Action	Check the DMCONFIG for the API specified for the local service.
	See Also	None
5077 ERROR	Enter shutdown
	Description	Failed to send SNACRM_SIGNAL_EVENT message to SNACRM.
	Action	Check the connection between GWSNAX and SNACRM.
	See Also	None
5078 ERROR	Enter shutdown
	Description	Failed to send SNACRM_CONNECT response message to SNACRM.
	Action	Check the connection between GWSNAX and SNACRM.
	See Also	None
5081 ERROR	Inbound connect request security check failed, RRCORR<svcReqCorr>!
	Description	Failed to pass the security checking for the inbound SNACRM_CONNECT request
	Action	Check the security setting in the DMCONFIG file.
	See Also	None
5083 ERROR	Invalid buffer type, encode failed!
	Description	The buffer type used by the TUXEDO client or server is not recognized in GWSNAX gateway. The GWSNAX only recognizes standard buffer types, such as STRING, CARRAY, X_OCTET, X_COMMON, X_C_TYPE, VIEW, VIEW32, FML, and FML32.
	Action	Check the application programs which will communicate through GWSNAX gateway.
	See Also	None
5084 ERROR	Outbound ACALL encode failed!
	Description	Failed to encode data for outbound SNACRM_ACALL request message.
	Action	Check for prior error message for the real cause of failure, and handle the error accordingly.
	See Also	None
5087 ERROR	Invalid buffer type, decode failed!
	Description	Unrecognized buffer type found for inbound message from SNACRM.
	Action	Check the applications, and the DMCONFIG file for the INBUFTYE. Only STRING, CARRAY, X_OCTET, X_COMMON, X_C_TYPE, VIEW, VIEW32, FML, and FML32 are allowed.
	See Also	None
5090 ERROR	Outbound CONNECT encode failed
	Description	Failed to encode data for the outbound SNACRM_CONNECT request message.
	Action	Check for prior error message for actual failure reason. The most common reasons are either memory allocation failure, OUTBUFTYPE specification error in the DMCONFIG, or could not find the definition file such as VIEW, VIEW32, FML, and FML32.
	See Also	None
5091 ERROR	Outbound CONVSEND encode failed
	Description	Failed to encode data for the outbound SNACRM_SEND_DATA request message.
	Action	Check for prior error message for actual failure reason. The most common reasons are either memory allocation failure, OUTBUFTYPE specification error in the DMCONFIG, or could not find the definition file such as VIEW, VIEW32, FML, and FML32.
	See Also	None
5094 ERROR	Unable to send data on sna_conv_idx <ctx_idx>, gpnd <gpnd>
	Description	Failed to send SNACRM_CONNECT response to SNACRM, GWSNAX shutdown itself.
	Action	Usually a serious network problem has occurred. Check the network connection to determine if the SNACRM is still up.
	See Also	None
5101 ERROR	Unable to find view file for buftype <bufstype>
	Description	Failed to find view file for the FML buffer type specified in the INBUFTYPE for the inbound request.
	Action	Check the VIEWFILES and VIEWDIR environmental variable, and whether the view file is in the directory specified by VIEWDIR.
	See Also	None
5107 ERROR	Unable to get appkey for this outbound request
	Description	Failed to find the remote domain configuration information in the shared memory.
	Action	Check the DMCONFIG for the remote domain configuration and its security setting. Contact your BEA Connect Technical Support.
	See Also	None
5109 ERROR	Unable to find view file for buftype <bufstype>
	Description	Failed to find view file definition for encoding outbound FML data as specified in the OUTBUFTYPE.
	Action	First check the VIEWDIR, and VIEWFILES environment to find out whether the specified VIEW file for FML is there. Next, check the DMCONFIG for the OUTBUFTYPE to find out if it is correct.
	See Also	None
5110 ERROR	Unable to find view file for buftype <bufstype>
	Description	Failed to find view file definition for encoding outbound FML32 data as specified in the OUTBUFTYPE.
	Action	First check the VIEWDIR32, and VIEWFILES32 environment to find out whether the specified VIEW file for FML is there. Next, check the DMCONFIG for the OUTBUFTYPE to find out if it is correct.
	See Also	None
5112 ERROR	System full, can't create action, Enter shutdown
	Description	Failed to create GWSNAX gateway internal scheduled event to handle failure or disconnect.
	Action	Either memory allocation failed or system limit reached. Check and update system memory configuration. If the reason is the later one, then contact your BEA Connect Technical Support.
	See Also	None
6000 ERROR	YOUR CONNECT SNA LICENSE IS EITHER INVALID OR EXPIRED
	Description	The BEA CONNECT SNA v2.0 license is missing or expired.
	Action	Contact your BEA sale representative.
	See Also	None
6001 ERROR	YOUR CONNECT SNA LICENSE IS NOT ENABLED FOR SYNCLEVEL 2
	Description	The BEA CONNECT SNA v2.0 license does not include the license to run request at sync level 2.
	Action	Contact your BEA sale representative.
	See Also	None
90xx: INFO	SNACRM Message: <string1>
	Description	ERROR or informational message sent from SNACRM to GWSNAX, and logged in the USERLOG file. Refer to "SNACRM Messages."
	Action	Refer to SNACRM message file.
	See Also	None

---

---