|
|
|
| |
|
General message to log NW_UNISYS messages
|
| |
|
Corrective action is given in the messages, otherwise contact Unisys Customer Support.
|
|
|
Tried to write more than maxlen:len=%ld, maxlen=%ld
|
| |
|
An internal error has been detected while processing the transaction blob record.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Can't create file %s in APPDIR for storing OSITP blob
|
| |
|
The Transaction blob file specified could not be created in the APPDIR directory.
|
| |
|
Check the file privileges of the APPDIR directory.
|
|
|
Can't write to OSITP blob file %s in APPDIR
|
| |
|
The GWOSITP software was unable to write to the Transaction blob file specified.
|
| |
|
Check to make sure there is sufficient space available in the APPDIR directory.
|
|
|
Unable to retrieve Network context, shutdown Gateway!
|
| |
|
An internal error has been detected while processing the action.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Unable to retrieve file descriptor, shutdown Gateway!
|
| |
|
An internal error has been detected while processing the action.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Unable to obtain svc (%s) info from shared memory, request rejected!
|
| |
|
The requested remote service could not be found in Domain remote service section of shared memory.
|
| |
|
Use dmunloadcf command to verify that the remote service specified is defined in the current configuration. If this service is not shown to exists in the current configuration, add it to the DM_REMOTE_SERVICES section of the domain configuration file, shutdown the gateway, rerun dmloadcf, and reboot the OSITP gateway process.
|
|
|
Find network transaction failed, shutdown Gateway!
|
| |
|
An internal error has been detected while processing the action.
|
| |
|
Contact Unisys Customer Support
|
|
|
Can not create Network Context, request rejected!
|
| |
|
A network context structure could not be created for the current tpcall. It is possible that the necessary memory could not be allocated.
|
| |
|
Adjust system parameters to allow more memory and restart the OSITP Gateway process.
|
|
|
Could not retrieve Network context, shutdown Gateway!
|
| |
|
An internal error has been detected while processing the action.
|
| |
|
Contact Unisys Customer Support
|
|
|
Unable to obtain remote domain info from shared memory
|
| |
|
An internal error has been detected while processing the action.
|
| |
|
Contact Unisys Customer Support
|
|
|
Transaction table full, request rejected!
|
| |
|
The number of current transaction exceeds the number allocated to this gateway as defined by the domain configuration parameter MAXTRAN or the total number of transaction allocated as defined by the TUXCONFIG parameter MAXGTT.
|
| |
|
Increase the appropriate Transaction parameter and restart the OSITP Gateway process and domain if necessary.
|
|
|
Unable to set nettxid in shmem
|
| |
|
An internal error has been detected while processing the action.
|
| |
|
Contact Unisys Customer Support
|
|
|
Cannot associate with network transaction
|
| |
|
An attempt to start this transaction failed either because this transaction is shown to have already completed or was aborted.
|
| |
|
|
|
|
Could not find RDOM %s cache entry
|
| |
|
The specified Remote domain should have already been placed in Cache. Either the rdom name or the cache memory has been corrupted.
|
| |
|
Contact Unisys Customer Support
|
|
|
Cannot set remote domain for transaction
|
| |
|
The Maximum number of remote domains for a given transaction has been exceeded.
|
| |
|
Increase the MAXRDOM parameter in the domain configuration file, rerun dmloadcf, and restart the OSITP Gateway, or reduce the number of remote domains involved in a single transaction.
|
|
|
Resumed with BLOCKING timeout
|
| |
|
A blocking timeout has occurred on a request to a remote host.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure. Check configuration and increase the BLOCKTIME value, if needed.
|
|
|
|
| |
|
An internal error has been detected while processing the action.
|
| |
|
Contact Unisys Customer Support
|
|
|
Couldn't retrieve TRAN table from shmem, shutdown Gateway!
|
| |
|
An internal error has been detected while processing the action.
|
| |
|
Contact Unisys Customer Support
|
|
|
Unable to obtain local tdomain address from shmem
|
| |
|
An internal error has been detected while processing the action.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Unable to get remote service information from shared memory
|
| |
|
The remote service name specified was not found in the DM_REMOTE_SERVICES shared memory tables.
|
| |
|
Check the domain configuration file DM_REMOTE_SERVICES section and verify that the Remote service specified has been defined. If not defined, correct the and restart any necessary processes.
|
|
|
Protocol error, DiaFSM state(%d), shutdown Gateway!
|
| |
|
A tpcall was received and the dialog was not in the FREE state. An internal processing error has occurred while processing a transaction.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, DiaFSM state(%d), shutdown Gateway!
|
| |
|
A tpconnect was received and the dialog was not in the FREE state. An internal processing error has occurred while processing a transaction.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, DiaFSM state(%d), shutdown Gateway!
|
| |
|
A tpsend was received and the dialog was not in a valid state. An internal processing error has occurred while processing a transaction.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, DiaFSM state(%d), shutdown Gateway!
|
| |
|
A tpsend was received and the dialog was not in a valid state. An internal processing error has occurred while processing a transaction.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, DiaFSM state(%d), shutdown Gateway!
|
| |
|
A Network reply was received and the dialog was not in a valid state. An internal processing error has occurred while processing a transaction.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, DiaFSM state(%d), shutdown Gateway!
|
| |
|
A Network failure was received and the dialog was not in a valid state. An internal processing error has occurred while processing a transaction.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, DiaFSM state(%d), shutdown Gateway!
|
| |
|
A Network tpcall was received and the dialog was not in a valid state. An internal processing error has occurred while processing a transaction.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, DiaFSM state(%d), shutdown Gateway!
|
| |
|
A Network tpconnect was received and the dialog was not in a valid state. An internal processing error has occurred while processing a transaction.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, DiaFSM state(%d), shutdown Gateway!
|
| |
|
A Network tpsend was received and the dialog was not in a valid state. An internal processing error has occurred while processing a transaction.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, DiaFSM state(%d), shutdown Gateway!
|
| |
|
A MSG reply was received and the dialog was not in a valid state. An internal processing error has occurred while processing a transaction.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, DiaFSM state(%d), shutdown Gateway!
|
| |
|
A MSG tpdisconnect was received and the dialog was not in a valid state. An internal processing error has occurred while processing a transaction.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, DiaFSM state(%d), shutdown Gateway!
|
| |
|
A MSG failure was received and the dialog was not in a valid state. An internal processing error has occurred while processing a transaction.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, DiaFSM state(%d), shutdown Gateway!
|
| |
|
A tpconnect confirm was received and the dialog was not in a valid state. An internal processing error has occurred while processing a transaction.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, DiaFSM state(%d), shutdown Gateway!
|
| |
|
A tpconnect fail was received and the dialog was not in a valid state. An internal processing error has occurred while processing a transaction.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, DiaFSM state(%d), shutdown Gateway!
|
| |
|
An internal processing error has occurred while processing a transaction.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, DiaFSM state(%d), shutdown Gateway!
|
| |
|
An invalid dialog state was encountered. An internal processing error has occurred while processing a transaction.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Internal error, shutdown Gateway!
|
| |
|
An internal processing error has occurred while processing this action.
|
| |
|
Look for prior Userlog messages for more information. Contact Unisys Customer Support.
|
|
|
Can't find input message buffer, ACALL event deleted!
|
| |
|
A reply was received for an ACALL event which has been deleted and no longer exists.
|
| |
|
|
|
|
More than one tpcall to AUTOPREPARE svc (%s) attempted, request rejected
|
| |
|
An attempt to make more than one tpcall within a transaction to an AUTOPREPARE service was attempted. This tpcall was rejected.
|
| |
|
Modify the client code or remove the AUTOPREPARE setting on the Service.
|
|
|
copy_local_service: Memory error on Local Service
|
| |
|
An internal error has been detected while copying a Local Service.
|
| |
|
Contact Unisys Customer Support.
|
|
|
copy_remote_domain: Memory error
|
| |
|
An internal error has been detected while copying a Remote Domain.
|
| |
|
Contact Unisys Customer Support.
|
|
|
copy_remote_service: Memory error on remote Service
|
| |
|
An internal error has been detected while copying a Remote Service.
|
| |
|
Contact Unisys Customer Support.
|
|
|
gwnwUtility_getLocalConfig: Memory error
|
| |
|
An internal error has been detected while getting the local configuration.
|
| |
|
Contact Unisys Customer Support.
|
|
|
gwnwUtility_getLocalConfig: Error walking though LDOM list
|
| |
|
An internal error has been detected while walking the LDOM list.
|
| |
|
Contact Unisys Customer Support.
|
|
|
read_cfg_in_file: Error allocating receive buffer
|
| |
|
An internal error has been detected while allocating the receive buffer.
|
| |
|
Contact Unisys Customer Support.
|
|
|
read_cfg_in_file: Can't send request to service DMADM. Tperrno = %d
|
| |
|
The gateway has attempted to call the DMADM server to obtain the OSITP configuration information. The DMADM server did not respond.
|
| |
|
If running in a Multiple Machine (MP) configuration the DMADM service is required. In this case you need to modify the ubbconfig file and add DMADM as a service. See OSI-TP Uses guide for help. Reprocess the file with tmloadcf. Then rerun tmboot. If running in the single machine (SHM) configuration the DMADM service is not needed and and this message can be ignored.
|
|
|
read_cfg_in_file: Bad version # of BDMCONFIG file
|
| |
|
The binary file "BDMCONFIG" contains an internal version number which is incompatible with this version of OSITP.
|
| |
|
Reprocess your DMCONFIG file with dmloadcf to create a new binary "BDMCONFIG" file.
|
|
|
read_cfg_in_file: Memory error on local domains
|
| |
|
An internal error has been detected while processing the local domains.
|
| |
|
Contact Unisys Customer Support.
|
|
|
read_cfg_in_file: Memory error on Remote domains
|
| |
|
An internal error has been detected while processing the remote domains.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Unable to allocate memory for Remote domains
|
| |
|
An internal error has been detected while processing the remote domains.
|
| |
|
Contact Unisys Customer Support.
|
|
|
read_cfg_in_file: Memory error on Local services
|
| |
|
An internal error has been detected while processing Local Services.
|
| |
|
Contact Unisys Customer Support.
|
|
|
read_cfg_in_file: Memory error on Remote services
|
| |
|
An internal error has been detected while processing Remote Services.
|
| |
|
Contact Unisys Customer Support.
|
|
|
read_cfg_in_file: fopen error on input file %s
|
| |
|
Error opening input file.
|
| |
|
Verify file exists and is accessible by you.
|
|
|
read_cfg_in_file: Read error on # of Version number.
|
| |
|
Error processing binary configuration file.
|
| |
|
Reprocess dmconfig text file with dmloadcf.
|
|
|
Encode of AE Title (%s) failed for RDOM (%s)
|
| |
|
An error occured while encoding the AE Title for the indicated remote domain.
|
| |
|
Contact Unisys Customer Support.
|
|
|
read_cfg_in_file: Read error on # of Local domains.
|
| |
|
Error processing binary configuration file.
|
| |
|
Reprocess dmconfig text file with dmloadcf.
|
|
|
Encode of AE Title (%s) failed for LDOM (%s)
|
| |
|
An error occured while encoding the AE Title for the indicated local domain.
|
| |
|
Check the definition of the AE Title for this local domain in the dmconfig file and correct. Shutdown the Gateway, rerun dmloadcf and reboot the Gateway process.
|
|
|
read_cfg_in_file: Read error on local domains
|
| |
|
Error processing binary configuration file.
|
| |
|
Reprocess dmconfig text file with dmloadcf.
|
|
|
read_cfg_in_file: Read error on # of Remote domains.
|
| |
|
Error processing binary configuration file.
|
| |
|
Reprocess dmconfig text file with dmloadcf.
|
|
|
read_cfg_in_file: Read error on Remote domains.
|
| |
|
Error processing binary configuration file.
|
| |
|
Reprocess dmconfig text file with dmloadcf.
|
|
|
read_cfg_in_file: Read error on # of Local services.
|
| |
|
Error processing binary configuration file.
|
| |
|
Reprocess dmconfig text file with dmloadcf.
|
|
|
read_cfg_in_file: Read error on Local Services.
|
| |
|
Error processing binary configuration file.
|
| |
|
Reprocess dmconfig text file with dmloadcf.
|
|
|
read_cfg_in_file: Read error on # of Remote services.
|
| |
|
Error processing binary configuration file.
|
| |
|
Reprocess dmconfig text file with dmloadcf.
|
|
|
read_cfg_in_file: Read error on Remote Services.
|
| |
|
Error processing binary configuration file.
|
| |
|
Reprocess dmconfig text file with dmloadcf.
|
|
|
BDMCONFIG environment variable is not set.
|
| |
|
The environment variable BDMCONFIG is not set.
|
| |
|
Set the environment variable BDMCONFIG to the fully qualified name of the BDMCONFIG file.
|
|
|
|
| |
|
An internal error occurred; gw_nw_buf_encode failed to initialize ioptr structure. The vbuf for which the ioptr was to be initialized is corrupted.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
The Gateway process was unable to encode the typed buffer.
|
| |
|
Look for further errors which indicate the type and subtype of the buffer which could not be encoded. Check the encoding types and the typed buffer definitions to ensure that they are compatible. Correct any discrepancies and restart the OSITP Gateway process if necessary.
|
|
|
|
| |
|
The Gateway process was unable to decode the typed buffer.
|
| |
|
Look for further errors which indicate the type and subtype of the buffer which could not be decoded. Check the encoding types and the typed buffer definitions to ensure that they are compatible. Correct any discrepancies and restart the OSITP Gateway process if necessary.
|
|
|
|
| |
|
An Internal error has occurred while trying to perform a tpalloc.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
Unable to process typed buffer, type=%s subtype=%s
|
| |
|
The Gateway process was unable to convert the specified buffer to an ASN.1 encoded buffer.
|
| |
|
Check the encoding types and the typed buffer definitions to ensure that they are compatible. If buffer conversion is being performed, check to make that the data conversion specified is valid. Correct any discrepancies and restart the OSITP Gateway process if necessary.
|
|
|
Unable to reconstruct typed buffer, type=%s subtype=%s
|
| |
|
The Gateway process was unable to convert an ASN1 encoded buffer tothe specified buffer.
|
| |
|
Check the encoding types and the typed buffer definitions to ensure that they are compatible. If buffer conversion is being performed, check to make that the data conversion specified is valid. Correct any discrepancies and restart the OSITP Gateway process if necessary.
|
|
|
INRECTYPE buffer type (%s) cannot be converted to NATIVE A SERIES buffer.
|
| |
|
The buffer type, specified by INRECTYPE, to be converted to a NATIVE A SERIES buffer is not a valid type for this conversion. Only buffers of type X_COMMON, X_C_TYPE, VIEW, and VIEW32 are valid.
|
| |
|
Check to make sure you are calling this service with the correct buffer type, or that the encoding of NATIVE_A_SERIES is correct.
|
|
|
Buffer type (%s) cannot be converted to a NATIVE A SERIES buffer.
|
| |
|
The buffer type to be converted to a NATIVE A SERIES buffer is not a valid type for this conversion. Only buffers of type X_COMMON, X_C_TYPE, VIEW, and VIEW32 are valid.
|
| |
|
Check to make sure you are calling this service with the correct buffer type or that the encoding of NATIVE_A_SERIES is correct.
|
|
|
read_cfg_in_file: fopen error on input file %s
|
| |
|
DMADM had a problem opening the binary configuration file, BDMCONFIG.
|
| |
|
Make sure the binary configuration file, BDMCONFIG, exists and is accessible to you.
|
|
|
Bad File Handle for binary file
|
| |
|
An internal error was detected in DMADM while trying to process the binary configuration file (BDMCONFIG).
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An internal error was detected in DMADM.
|
| |
|
Contact Unisys Customer Support.
|
|
|
BDMCONFIG environment variable is not set.
|
| |
|
The environment variable BDMCONFIG is not set.
|
| |
|
Set the environment variable BDMCONFIG to the fully qualified name of the BDMCONFIG file.
|
|
|
Invalid conversation context
|
| |
|
An internal error has been detected.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, msg state(%d), shutdown Gateway!
|
| |
|
An internal error has been detected.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, msg state(%d), shutdown Gateway!
|
| |
|
An internal error has been detected.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, dial state(%d), shutdown Gateway!
|
| |
|
An internal error has been detected.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, node state(%d), shutdown Gateway!
|
| |
|
An internal error has been detected.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, msg state(%d), shutdown Gateway!
|
| |
|
An internal error has been detected.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, node state(%d), shutdown Gateway!
|
| |
|
An internal error has been detected.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Could not find transaction node, shutdown Gateway!
|
| |
|
An internal error has been detected.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, msg state(%d), shutdown Gateway!
|
| |
|
An internal error has been detected.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Could not find transaction node, shutdown Gateway!
|
| |
|
An internal error has been detected.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Can not create Network Context, request rejected!
|
| |
|
A Network Context structure could not be allocated for the requested tpconnect. There is not enough process memory available to allocate the structure necessary for processing the requested tpconnect.
|
| |
|
Increase system parameters to allow more process memory and restart the Gateway.
|
|
|
Could not retrieve Network context, shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support
|
|
|
Could not retrieve Network context, shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support
|
|
|
Unable to obtain svc (%s)info from shared memory, request rejected!
|
| |
|
The service requested could not be found in the shared memory DM_REMOTE_SERVICES section. The shared memory has been corrupted.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Transaction table full, request rejected!
|
| |
|
The number of outstanding Transactions has exceeded the Maximum number allowed as defined by the Local Domains MAXTRAN or the Machines definition MAXGTT.
|
| |
|
Increase either the MAXTRAN or MAXGTT configuration parameter and restart the Gateway.
|
|
|
Unable to create gwnwClientAgent, request rejected!
|
| |
|
There is not enough process memory available to allocate the structure necessary for processing the requested tpconnect.
|
| |
|
Increase system parameters to allow more process memory and restart the Gateway.
|
|
|
Unable to obtain remote domain info from shared memory
|
| |
|
The remote domain could not be found in the shared memory DM_REMOTE_DOMAINS section. The shared memory has been corrupted.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Conversation identifier is invalid
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Couldn't retrieve TRAN table from shmem
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Unable to set nettxid in shmem
|
| |
|
An attempt to set the network transaction id in shared memory failed. This could indicate that the shared memory tables have been corrupted.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Cannot associate with network transaction
|
| |
|
An attempt to start this transaction failed either because this transaction is shown to have already completed or was aborted.
|
| |
|
|
|
|
Cannot set remote domain for transaction
|
| |
|
An attempt to set the remote domain for this transaction failed.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Invalid incoming conversation context
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Conversation identifier is NULL
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Invalid conversation context
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Resumed with blocking timeout
|
| |
|
This conversation incurred a blocking timeout and will be aborted.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure. Check configuration and increase the BLOCKTIME value, if needed.
|
|
|
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Software Support.
|
|
|
Could not find RDOM %s cache entry
|
| |
|
The remote domain id specified for this service could not be found in the remote domain cache. This could indicate that the configuration file is incorrect or that there has been corruption of the remote domain cache.
|
| |
|
Check the domain configuration file and make sure that the remote domain specified is defined in the file correctly. If in error, correct the error, shutdown the gateway, reload the configuration file, and restart the gateway.
|
|
|
Invalid outgoing conversation context
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Software Support.
|
|
|
Found transaction without log record
|
| |
|
A previous transaction was found, however a log record for this transaction did not exist. This transaction will be rolled back.
|
| |
|
|
|
|
Create transaction node failed, shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
The transaction log record could not be recovered. The transaction will be rolled back.
|
| |
|
|
|
|
Unable to create action to handle restarted transaction!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Create transaction node failed, shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Unable to create action to handle restarted transaction!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Unable to create action to handle restarted transaction!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
The specified view file could not be found.
|
| |
|
Check to make sure that the view file exists and the VIEWFILES or VIEWFILES32 environment variables contain the specified view file name. Also check to make sure that the view file is located in the directory specified by the VIEWDIR or VIEWDIR32 environment variable.
|
|
|
|
| |
|
The APDU buffer allocated was not large enough to hold the data contained in the view buffer.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
The APDU buffer allocated was not large enough to hold the data contained in the view buffer.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
The APDU buffer allocated was not large enough to hold the data contained in the view buffer.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An internal error occured; An attempt to allocate a buffer failed.
|
| |
|
Contact Unisys Technical Support
|
|
|
Invalid data type for X_C_TYPE
|
| |
|
The data type contained in the view is not a valid X_C_TYPE buffer data type. Valid X_C_TYPE data types are short, int, long, char, float, double, decimal, string, and carray.
|
| |
|
Look for further error which indicate the name of the VIEW buffer which is in error. Correct the View buffer to contain the correct data types or define the buffer as X_C_TYPE.
|
|
|
|
| |
|
The specified view file could not be found.
|
| |
|
Check to make sure that the view file exists and the VIEWFILES32 environment variables contain the specified view file name. Also check to make sure that the view file is located in the directory specified by the VIEWDIR32 environment variable.
|
|
|
|
| |
|
The specified view file could not be found.
|
| |
|
Check to make sure that the view file exists and the VIEWFILES or VIEWFILES32 environment variables contain the specified view file name. Also check to make sure that the view file is located in the directory specified by the VIEWDIR or VIEWDIR32 environment variable.
|
|
|
Missing data element in received Data Stream
|
| |
|
The X_C_TYPE buffer did not contain the expected data element as defined by the destination VIEW.
|
| |
|
Look for further User Log messages which indicate what the VIEW Type and Subtype was involved, then make sure the source VIEW and destination VIEW definitions are identical. Correct the VIEWs and restart the necessary gateway process.
|
|
|
|
| |
|
The APDU buffer allocated was not large enough to hold the data contained in the view buffer.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Missing data element in received Data Stream
|
| |
|
The X_C_TYPE buffer did not contain the expected data element as defined by the destination VIEW.
|
| |
|
Look for further User Log messages which indicate what the VIEW Type and Subtype was involved, then make sure the source VIEW and destination VIEW definitions are identical. Correct the VIEWs and restart the necessary gateway process.
|
|
|
|
| |
|
The APDU buffer allocated was not large enough to hold the data contained in the view buffer.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Missing data element in received Data Stream
|
| |
|
The X_C_TYPE buffer did not contain the expected data element as defined by the destination VIEW.
|
| |
|
Look for further User Log messages which indicate what the VIEW Type and Subtype was involved, then make sure the source VIEW and destination VIEW definitions are identical. Correct the VIEWs and restart the necessary gateway process.
|
|
|
|
| |
|
The data type contained in the view is not a valid X_C_TYPE buffer data type. Valid X_C_TYPE data types are short, int, long, char, float, double, decimal, string, and carray.
|
| |
|
Look for further error which indicate the name of the VIEW buffer which is in error. Correct the View buffer to contain the correct data types or define the buffer as X_C_TYPE.
|
|
|
|
| |
|
A null buffer was passed to a service call/service reply.
|
| |
|
Make sure the buffer is allocated, and the buffer is not NULL
|
|
|
|
| |
|
Buffer type not defined in the buffer type switch
|
| |
|
Examine the application and the configuration to determine which buffer type is being used. GWOSITP only supports standard TUXEDO buffer types over the domain gateway. If the buffer type is VIEW, VIEW32, then also examine the environment variables VIEWDIR, VIEWFILES, VIEWDIR32, and VIEWFILES32
|
|
|
Unable to obtain svc info from svcinfo
|
| |
|
An internal error occured; gw_nw_buf_encode failed to obtain remote service information
|
| |
|
Contact Unisys Technical Support
|
|
|
Unable to obtain INRECTYPE for remote service
|
| |
|
An internal error occured; gw_nw_buf_encode failed to obtain INRECTYPE for remote service
|
| |
|
Contact Unisys Technical Support
|
|
|
Can't find LSVC entry by rname %s
|
| |
|
An internal error occured; gw_nw_buf_encode failed to obtain local service information
|
| |
|
Contact Unisys Technical Support
|
|
|
Unable to obtain INRECTYPE for local service
|
| |
|
An internal error occured; gw_nw_buf_encode failed to obtain INRECTYPE for local service
|
| |
|
Contact Unisys Technical Support
|
|
|
Received type(%s:%s) does not match INBUFTYPE(%s:%s)
|
| |
|
Buffer received by the gateway does not match INBUFTYPE configuration
|
| |
|
Reconfigure INBUFTYPE to match incoming buffer type and subtype
|
|
|
|
| |
|
The specified view file could not be found.
|
| |
|
Check to make sure that the view file exists and the VIEWFILES environment variables contain the specified view file name. Also check to make sure that the view file is located in the directory specified by the VIEWDIR environment variable.
|
|
|
Conversion invalid from (%s) to (%s)
|
| |
|
Conversion from a 16:bit buffer to 32:bit buffer, or vice versa, is not allowed
|
| |
|
Make sure conversion specified is between 16-bit buffers, or between 32-bit buffers
|
|
|
INRECTYPE not configured for (%s)
|
| |
|
Buffers of type FML / FML32 cannot be transmitted to a remote system
|
| |
|
Configure INRECTYPE to VIEW, X_C_TYPE, or X_COMMON
|
|
|
|
| |
|
Could not find the listed view file
|
| |
|
Verify VIEWDIR and VIEWFILES environment variables
|
|
|
|
| |
|
Could not find the listed view file
|
| |
|
Verify VIEWDIR32 and VIEWFILES32 environment variables
|
|
|
Invalid buffer type specified
|
| |
|
Buffer type not defined in the buffer type switch
|
| |
|
Examine the application and the configuration to determine which buffer type is being used. GWOSITP only supports standard TUXEDO buffer types over the domain gateway. If the buffer type is VIEW, VIEW32, then also examine the environment variables VIEWDIR, VIEWFILES, VIEWDIR32, and VIEWFILES32
|
|
|
Memory allocation failure
|
| |
|
An internal error occured; gw_nw_buf_encode failed to allocate XATMI_typed_buffer
|
| |
|
Contact Unisys Technical Support
|
|
|
|
| |
|
Buffer type not defined in the buffer type switch
|
| |
|
Examine the application and the configuration to determine which buffer type is being used. GWOSITP only supports standard TUXEDO buffer types over the domain gateway. If the buffer type is VIEW, VIEW32, then also examine the environment variables VIEWDIR, VIEWFILES, VIEWDIR32, and VIEWFILES32
|
|
|
Memory allocation failure
|
| |
|
An internal error occured; gw_nw_buf_encode failed to allocate ap_osi_vbuf
|
| |
|
Contact Unisys Technical Support
|
|
|
|
| |
|
An internal error occured; gw_nw_buf_encode failed to encode typed buffer
|
| |
|
Contact Unisys Technical Support
|
|
|
Conversion invalid from (%s) to (%s)
|
| |
|
Buffers of type FML and FML32 cannot be transmitted to a remote system
|
| |
|
Remove INRECTYPE or reconfigure INRECTYPE to a different type such as a VIEW
|
|
|
Received type(%s:%s) does not match OUTRECTYPE(%s:%s)
|
| |
|
Buffer received by the gateway does not match OUTRECTYPE configuration
|
| |
|
Reconfigure OUTRECTYPE to match incoming buffer type and subtype
|
|
|
OUTBUFTYPE(%s:%s) invalid for received type(%s)
|
| |
|
Received type cannot be converted to OUTBUFTYPE
|
| |
|
Configure OUTBUFTYPE to X_OCTET, STRING, or CARRAY
|
|
|
|
| |
|
Could not find the listed view file
|
| |
|
Verify VIEWDIR and VIEWFILES environment variables
|
|
|
FML incompatible field in %s:%s
|
| |
|
The listed view contains packed decimal data type. Views containing this type cannot be used for FML-to-view or view-to-view conversions
|
| |
|
Remove packed decimal fields from the input FML or view, or send the same view structure to the local gateway that is sent to the remote gateway
|
|
|
Cannot convert view (%s) not mapped to FML
|
| |
|
Listed view is not mapped to FML
|
| |
|
Recompile the view WITHOUT the '-n' option of the view compiler
|
|
|
|
| |
|
Allocation of an TUXEDO typed buffer failed
|
| |
|
Contact Unisys Technical Support
|
|
|
|
| |
|
The conversion of a C structure to a fielded buffer failed
|
| |
|
Contact Unisys Technical Support
|
|
|
|
| |
|
Could not find the listed view file
|
| |
|
Verify VIEWDIR and VIEWFILES environment variables
|
|
|
Cannot convert view (%s) not mapped to FML
|
| |
|
Listed view is not mapped to FML
|
| |
|
Recompile the view WITHOUT the '-n' option of the view compiler
|
|
|
|
| |
|
Allocating a typed buffer for the listed view failed
|
| |
|
Contact Unisys Technical Support
|
|
|
|
| |
|
The conversion of a fielded buffer to a C structure failed
|
| |
|
Contact Unisys Technical Support
|
|
|
Unable to obtain svc info from svcinfo
|
| |
|
An internal error occured; gw_nw_buf_decode failed to obtain remote service information
|
| |
|
Contact Unisys Technical Support
|
|
|
Unable to obtain OUTRECTYPE for remote service
|
| |
|
An internal error occured; gw_nw_buf_decode failed to obtain OUTRECTYPE for remote service
|
| |
|
Contact Unisys Technical Support
|
|
|
Can't find LSVC entry by rname <%s>
|
| |
|
An internal error occured; gw_nw_buf_decode failed to obtain local service information
|
| |
|
Contact Unisys Technical Support
|
|
|
Unable to obtain OUTRECTYPE for local service
|
| |
|
An internal error occured; gw_nw_buf_decode failed to obtain OUTRECTYPE for local service
|
| |
|
Contact Unisys Technical Support
|
|
|
|
| |
|
An internal error occured; gw_nw_buf_decode failed to initialize ioptr
|
| |
|
Contact Unisys Technical Support
|
|
|
Memory allocation failure
|
| |
|
An internal error occured; gw_nw_buf_decode failed to allocate XATMI_typed_buffer
|
| |
|
Contact Unisys Technical Support
|
|
|
|
| |
|
Buffer type not defined in the buffer type switch
|
| |
|
Examine the application and the configuration to determine which buffer type is being used. GWOSITP only supports standard TUXEDO buffer types over the domain gateway. If the buffer type is VIEW, VIEW32, then also examine the environment variables VIEWDIR, VIEWFILES, VIEWDIR32, and VIEWFILES32
|
|
|
conversion invalid from < %s > to < %s >
|
| |
|
Conversion from a 16-bit buffer to 32-bit buffer, or vice versa, is not allowed
|
| |
|
Make sure conversion specified is between two 16-bit buffers, or between two 32-bit buffers
|
|
|
Service < %s > is denied Access
|
| |
|
The user has been denied access to the specified service. The Remote domain from which this call was initiated is not specified in the Access Control list for this service.
|
| |
|
Check the Access Control list and add the Remote Domain if necessary and restart the Gateway process.
|
|
|
|
| |
|
An internal processing error has occurred. The ASN.1 buffer type to convert the view to is not X_OCTET, X_COMMON, or X_C_TYPE.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An internal processing error has occurred. The buffer to convert to X_OCTET was null.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An internal processing error has occurred. The buffer to convert to X_COMMON was null.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
The specified view file could not be found.
|
| |
|
Check to make sure that the view file exists and the VIEWFILES or VIEWFILES32 environment variables contain the specified view file name. Also check to make sure that the view file is located in the directory specified by the VIEWDIR or VIEWDIR32 environment variable.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
Invalid data type for X_COMMON
|
| |
|
The data type contained in the view is not a valid X_COMMON buffer data type. Valid X_COMMON data types are short, long, char, string, and carray.
|
| |
|
Look for further error which indicate the name of the VIEW buffer which is in error. Correct the View buffer to contain the correct data types or define the buffer as X_C_TYPE.
|
|
|
|
| |
|
An internal processing error has occurred. The buffer to convert to X_OCTET was null.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
The specified view file could not be found.
|
| |
|
Check to make sure that the view file exists and the VIEWFILES or VIEWFILES32 environment variables contain the specified view file name. Also check to make sure that the view file is located in the directory specified by the VIEWDIR or VIEWDIR32 environment variable.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
Invalid data type for X_C_TYPE
|
| |
|
The data type contained in the view is not a valid X_C_TYPE buffer data type. Valid X_C_TYPE data types are short, int, long, char, float, double, decimal, string, and carray.
|
| |
|
Look for further error which indicate the name of the VIEW buffer which is in error. Correct the View buffer to contain the correct data types or define the buffer as X_C_TYPE.
|
|
|
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An internal processing error has occurred. The buffer to convert to X_OCTET was null.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An internal processing error has occurred. The buffer to convert to X_C_TYPE was null.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
The specified view file could not be found.
|
| |
|
Check to make sure that the view file exists and the VIEWFILES or VIEWFILES32 environment variables contain the specified view file name. Also check to make sure that the view file is located in the directory specified by the VIEWDIR or VIEWDIR32 environment variable.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Invalid data type for X_C_TYPE
|
| |
|
The data type contained in the view is not a valid X_C_TYPE buffer data type. Valid X_C_TYPE data types are short, int, long, char, float, double, decimal, string, and carray.
|
| |
|
Look for further error which indicate the name of the VIEW buffer which is in error. Correct the View buffer to contain the correct data types or define the buffer as X_C_TYPE.
|
|
|
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
The specified view file could not be found.
|
| |
|
Check to make sure that the view file exists and the VIEWFILES or VIEWFILES32 environment variables contain the specified view file name. Also check to make sure that the view file is located in the directory specified by the VIEWDIR or VIEWDIR32 environment variable.
|
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Invalid data type for X_COMMON
|
| |
|
The data type contained in the view is not a valid X_COMMON buffer data type. Valid X_COMMON data types are short, long, char, string, and carray.
|
| |
|
Look for further error which indicate the name of the VIEW buffer which is in error. Correct the View buffer to contain the correct data types or define the buffer as X_C_TYPE.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Can't get local service < %s > from configuration file
|
| |
|
The service requested could not be found in the shared memory section defined by DM_LOCAL_SERVICES.
|
| |
|
Check the configuration files and verify that the service is defined as in the DM_LOCAL_SERVICES section. If necessary, Add the service definition and restart the OSITP Gateway process.
|
|
|
Incoming request not allowed access to any local services
|
| |
|
An incoming service call was denied access because the Remote Domain is not specified the ACL List for the local service.
|
| |
|
Look for further error messages which specify the local service which has been denied access. If access is required, add the remote domain to the services ACL list.
|
|
|
Can't find LSVC entry by rname %s
|
| |
|
The requested service could not be found in the shared memory DM_LOCAL_SERVICES section.
|
| |
|
Check the DM_LOCAL_SERVICES section of the configuration file for the requested service. If not found add the service and restart the OSITP Gateway process.
|
|
|
|
| |
|
The buffer type is not a valid buffer type.
|
| |
|
Look for further error which indicate the name of the buffer which is in error.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
View file must be specified
|
| |
|
The VIEW32 buffer did not have a buffer subtype.
|
| |
|
Check the tpalloc call and make sure it specifies a subtype. Look for further User log messages which specify the buffer in error.
|
|
|
|
| |
|
The buffer to be converted to X_C_TYPE is not a valid tpalloc buffer.
|
| |
|
Check the tpalloc call and make sure it specifies a subtype. Look for further User log messages which specify the buffer in error.
|
|
|
|
| |
|
The VIEW32 buffer did not have a buffer subtype.
|
| |
|
Check the tpalloc call and make sure it specifies a subtype. Look for further User log messages which specify the buffer in error.
|
|
|
Missing data element in received Data Stream
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Missing data element in received Data Stream
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Missing data element in received Data Stream
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Missing data element in received Data Stream
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Missing data element in received Data Stream
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Missing data element in received Data Stream
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
ASN.1 DECODE failed, out of short integer range
|
| |
|
The value to decode was larger than what would fit into a short integer.
|
| |
|
Modify the VIEW field to use a long integer, recompile the VIEW as necessary.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
ASN.1 DECODE failed, out of short integer range
|
| |
|
The value to decode was larger than what would fit into a short integer.
|
| |
|
Modify the VIEW field to use a long integer, recompile the VIEW as necessary.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
ASN.1 DECODE failed, out of short integer range
|
| |
|
The value to decode was larger than what would fit into a short integer.
|
| |
|
Modify the VIEW field to use a long integer, recompile the VIEW as necessary.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
ASN.1 DECODE failed, out of short integer range
|
| |
|
The value to decode was larger than what would fit into a short integer.
|
| |
|
Modify the VIEW field to use a long integer, recompile the VIEW as necessary.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
ASN.1 DECODE failed, out of integer range
|
| |
|
The value to decode was larger than what would fit into a integer.
|
| |
|
Modify the VIEW field to use a field which allows larger values, recompile the VIEW as necessary.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
ASN.1 DECODE failed, out of integer range
|
| |
|
The value to decode was larger than what would fit into a integer.
|
| |
|
Modify the VIEW field to use a field which allows larger values, recompile the VIEW as necessary.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
ASN.1 DECODE failed, float range out of local limit
|
| |
|
The value to decode was larger than what would fit into a float.
|
| |
|
Modify the VIEW field to use a double, recompile the VIEW as necessary.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
ASN.1 DECODE failed, float range out of local limit
|
| |
|
The value to decode was larger than what would fit into a float.
|
| |
|
Modify the VIEW field to use a double, recompile the VIEW as necessary.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
ASN.1 DECODE failed, double range out of local limit
|
| |
|
The value to decode was larger than what would fit into a double.
|
| |
|
Modify VIEW field to correct the problem.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
ASN.1 DECODE failed, double range out of local limit
|
| |
|
The value to decode was larger than what would fit into a double.
|
| |
|
Modify VIEW field to correct the problem.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
|
| |
|
An Internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
Received type does not match definition
|
| |
|
The received type does not match the definition specified by the VIEW.
|
| |
|
Look for further error messages which specify the VIEW buffer type in error. This can occur when the VIEW definition used by the calling program does not match the VIEW definition used by the receiving process. Check the VIEW definitions of client and server to make sure that are identical. If a VIEW definition has been modified, make sure the associated Gateway process has been restart as VIEW definitions are cached by the Gateways.
|
|
|
|
| |
|
An Internal error has occurred while trying to allocate space for the buffer conversion.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
%s is encountered while encoding VIEW %s/%s member/type (%d/%s) to a NATIVE A SERIES buffer.
|
| |
|
A data conversion error has occured while trying to encode the specified VIEW to a NATIVE A SERIES type buffer. The field in error is identified by the member index and type.
|
| |
|
Examine the specified VIEW to ensure that all field types are valid for NATIVE A SERIES compatible fields. Refer to the section on NATIVE A SERIES data conversion in the BEA Tuxedo Mainframe Adapter for OSI TP User Guide to determine the exact cause of the error.
|
|
|
%s encountered while decoding a NATIVE A SERIES buffer to a VIEW %s/%s member/type (%d/%s).
|
| |
|
A data conversion error has occured while trying to decode a NATIVE A SERIES buffer into the specified VIEW. The field in error is identified by the VIEW member index and type.
|
| |
|
Examine the specified VIEW to ensure that all field types are valid for NATIVE A SERIES compatible fields. Refer to the section on NATIVE A SERIES data conversion in the BEA Tuxedo Mainframe Adapter for OSI TP User Guide to determine the exact cause of the error.
|
|
|
ASN.1 buffer type received was not a valid NATIVE A SERIES, but the buffer type received is from a different encoding type.
|
| |
|
The remote domain encoding type is specified as NATIVE A SERIES, but the buffer type received is from a different encoding type.
|
| |
|
Check the encoding type of the Remote domain to ensure that the encoding type is NATIVE A SERIES.
|
|
|
Cannot malloc fd structures
|
| |
|
An Internal error has occurred while trying to allocate space for internal structures.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
This line indicates the time and date that the gwnwinit.c module was built.
|
| |
|
|
|
|
Malloc communication control structure failed
|
| |
|
An Internal error has occurred while trying to allocate space for internal structures.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
|
| |
|
The OSITP Gateway process is exiting.
|
| |
|
|
|
|
Specified environmental variable GW_DFLT_TRANTIME out of valid range, ignored!
|
| |
|
The GW_DFLT_TRANTIME is larger than what will fit into a long integer.
|
| |
|
A default value of 300: seconds will be used. If this is not desired, correct the GW_DFLT_TRANTIME environment variable and restart the Gateway.
|
|
|
SECURITY is set to %s, but dmconfig LDOM security is not set to DM_PW, userid will not be passed.
|
| |
|
You have set the SECURITY to USER_AUTH, ACL, MANDATORY_ACL in the ubbconfig file, however, you did not set the SECURITY to DM_PW (link layer security) in the dmconfig file. The userid will not be passed to remote domains.
|
| |
|
If this is not the desired result, change the SECURITY in the dmconfig file for this local domain to DM_PW and check to make sure that any OSITPX remote domains for which the userid is to have passed has the OPTION set to SECURITY_SUPPORTED.
|
|
|
Malloc CID string buffer failed
|
| |
|
An Internal error has occurred while trying to allocate space for internal structures.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
Error occured while processing remote domains.
|
| |
|
An internal error has occured while processing the remote domain configuration parameters
|
| |
|
Look for prior errors in the log that identify the exact problem. Then check the remote domain configurations for errors. If unable to identify the problem, contact Unisys Customer Support.
|
|
|
Internal data structure not allocated yet
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Internal protocol error, missing routing information
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Remote OSITP domain not defined locally
|
| |
|
An incoming service call was received from a remote domain which is not defined in the DM_REMOTE_DOMAINS section of the configuration file.
|
| |
|
Add the necessary remote domain definition to DM_REMOTE_DOMAIN and DM_OSITP sections of the configuration file and restart the Gateway.
|
|
|
Internal data structure not allocated yet
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
A remote domain name was a NULL string.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Internal data structure not allocated yet
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Remote OSITP domain (%s) not defined in DM_OSITP
|
| |
|
An incoming service call was received from the specified remote domain which is not defined in the DM_REMOTE_DOMAINS section of the configuration file.
|
| |
|
Add the necessary remote domain definition to DM_REMOTE_DOMAINS and DM_OSITPX sections of the configuration file and restart the Gateway.
|
|
|
Your TMA OSI TP license is either invalid or expired
|
| |
|
Check your license file to make sure that is has not expired and that it contains the correct OSI TP License information.
|
| |
|
Correct the license file and restart the Gateway. For more help Contact Unisys Customer Support.
|
|
|
Version of Unisys (%d) and BEA (%d) binaries do not match
|
| |
|
The versions of the Unisys and BEA dlls and executable are not compatible.
|
| |
|
Reinstall the Software and restart the OSITP Gateway. For more help, contact Unisys Customer support.
|
|
|
Bad input arguments, unable to create instance
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Could not get RDOM Cache entry
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
RDOM %s OSITP address not configured
|
| |
|
The OSITP configuration parameters for the specified RDOM are not configured in the domain configuration file.
|
| |
|
Verify that a valid entry for the specified RDOM is present in DM_OSITPX section of the domain configuration file. If not, correct the problem and restart the gateway as necessary.
|
|
|
Unable to get remote domain information from shmem
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
A bad return code was received from set_new_action or gw_new_action for the specified message type. This is an internal processing error.
|
| |
|
Look for additional log messages which might be related to this error. Contact Unisys Customer Support.
|
|
|
Could not make new action
|
| |
|
A bad return code was received by set_new_action from gw_new_action.
|
| |
|
Look for additional log messages which might be related to this error. Contact Unisys Customer Support.
|
|
|
Dropping polled action, no free contexts
|
| |
|
A bad return code was received in set_new_action from gw_nw_CreateInstance or gw_nw_GetNwCtxByAction.
|
| |
|
Look for additional log messages which might be related to this error. Contact Unisys Customer Support.
|
|
|
Could not make new action
|
| |
|
A bad return code was received by set_new_action from gw_new_action.
|
| |
|
Look for additional log messages which might be related to this error. Contact Unisys Customer Support.
|
|
|
Dropping polled action, no free contexts
|
| |
|
A bad return code was received by set_new_action from gw_nw_SetNwCtx.
|
| |
|
Look for additional log messages which might be related to this error. Contact Unisys Customer Support.
|
|
|
queue entry type unknown - %x
|
| |
|
A protocol error has occurred in gw_nw_poll. An invalid entry type has been encountered.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Dropping polled action, context has been free
|
| |
|
Network data has been received for a Network Context which no longer exists.
|
| |
|
|
|
|
Call to service (%s) aborted due to lack of system Resources
|
| |
|
Not enough system resources were available to complete the processing of this service call.
|
| |
|
For more information Contact Unisys Customer Support.
|
|
|
Call to service (%s) failed with TPNOENT"
|
| |
|
The remote service requested does not exist at the remote domain.
|
| |
|
Either the service requested does not exists or the service requested exists but is not the correct type (conversational/non-conversational).
|
|
|
User <%s> is denied access to Service <%s>
|
| |
|
The user does not have access to services.
|
| |
|
The userid is not a valid userid. The userid must be added to the tpusr file by the Tuxedo System Administrator.
|
|
|
Cannot create shared mem nettxid
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Transaction table full, rejecting remote request!
|
| |
|
The number of outstanding tranactions exceeds the maximum allowed under the currenct configuration. This could be the MAXGTT or MAXTRAN value.
|
| |
|
To allow more transactions, increase the appropriate configuration parameter and reload the appropriate configuation file and restart the gateway process.
|
|
|
OSI TP protocol error, shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Unable to assign id to incoming conversation
|
| |
|
The maximum number of conversations allowed, as defined by MAXCONV, has been exceeded.
|
| |
|
To allow more conversations, increase the appropriate configuration parameter and reload the appropriate configuation file and restart the gateway process.
|
|
|
No conversation id associated with this fd
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Blocking timeout occurred, deleting fd
|
| |
|
A blocking timeout has occurred on a request to a remote host.
|
| |
|
Examine the ULOG for more information concerning the reason for the failure. Check configuration and increase the BLOCKTIME value, if needed.
|
|
|
Conversation id not found
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, DiaFSM state(%d), shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Could not find transaction node, shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, dial state(%d), shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Protocol error, dial state(%d), shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Invalid conversation context
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An attempt to send a reply to the called failed.
|
| |
|
Look for further Stack vendor errors for more information as to why this failure occurred.
|
|
|
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Could not find transaction node!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Unable to obtain remote domain info from shared memory
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Unable to obtain ositp info from rdom
|
| |
|
The DM_OSITPX section for a remote domain is not defined in the domain configuration file.
|
| |
|
Make the necessary corrections to the domain configuration file, reload the file, and restart the OSITP gateway process.
|
|
|
Cannot realloc fd structures
|
| |
|
An Internal error has occurred while trying to allocate space for Network Context structure.
|
| |
|
Increase the system parameters to allow more memory per process and restart the OSITP gateway process.
|
|
|
Remote domain name(%s) not found
|
| |
|
The specified remote domain is not defined in the domain configuration file.
|
| |
|
Add the remote domain information to the domain configuration file, reload the file, and restart the OSITP gateway process.
|
|
|
gw_tx_end returned failure
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Invalid input transaction id
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Exceeding local transaction limit
|
| |
|
The number of local transaction allowed, as defined by MAXTRAN, has been exceeded.
|
| |
|
To increase the number allowed, Increase the MAXTRAN parameter and restart the OSITP gateway process.
|
|
|
Branch does not belong to this transaction
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Exceeding local transaction limit
|
| |
|
The number of local transaction allowed, as defined by MAXTRAN, has been exceeded.
|
| |
|
To increase the number allowed, Increase the MAXTRAN parameter and restart the OSITP gateway process.
|
|
|
Branch does not belong to this transaction
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Transaction branch does not exist
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Invalid input file descriptor
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Transaction branch already exists
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Invalid input file descriptor
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Corrupted or uninitialized file descriptor
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Allocating Network Transaction table failed
|
| |
|
The memory could not be allocated for the Network Transaction table.
|
| |
|
Adjust system parameters to allow more memory or fewer Transactions and restart the OSITP Gateway process.
|
|
|
Bad input transaction identification
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Bad input transaction identification
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Invalid transaction look up table entry
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Invalid or corrupted network context descriptor %d
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Invalid conversation descriptor %d
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Invalid action descriptor %d
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Invalid context descriptor %d
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Invalid action descriptor %d
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Invalid context descriptor %d
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Possible orphaned conversation %d
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Invalid action descriptor
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Invalid action descriptor %d
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Maximum system context limit already reached
|
| |
|
The Maximum number (32767) of system context structures have been created. It is possible that there is a memory leak.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Corrupted or uninitialized file descriptor
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Invalid conversation descriptor
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Remote domain(%s) XATMI encoding not specified, use default
|
| |
|
The XATMI encoding type for the Remote Domain has not been configured in the DM_OSITPX section. The default XATMI encoding type is being used.
|
| |
|
No action is necessary, unless the default encoding type is not desired. If the default is not desired, add the XATMI_ENCODING parameter value for the specified remote domain, reload the domain config file, and restart the OSITP gateway process.
|
|
|
Remote OSITP domain %s address not configured
|
| |
|
The DM_OSITPX section is not defined for the given Remote Domain.
|
| |
|
Add the DM_OSITPX section to the configuration file, reload the domain config file, and restart the OSITP gateway process.
|
|
|
Wrong remote domain type(%s)
|
| |
|
The remote domain type is not OSITP.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Cannot get status of security file
|
| |
|
The security file does not exist.
|
| |
|
Check the configuration and make sure the security file exists or reconfigure the system such that security is off.
|
|
|
Cannot find appkey for user name [%s]
|
| |
|
The specified username appkey does not exists in the security file.
|
| |
|
Add the user appkey to the security file or use a username which is defined in the security file.
|
|
|
Cannot find user name for appkey [%d]
|
| |
|
The specified appkey does not exists in the security file.
|
| |
|
Add the user appkey to the security file or use a username whose appkey is defined in the security file.
|
|
|
Cannot open security file %s
|
| |
|
The security file does not exist.
|
| |
|
Check the configuration and make sure the security file exists or reconfigure the system such that security is off.
|
|
|
failed to insert blob segment into transaction table!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support.
|
|
|
Event stack overflow, shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support
|
|
|
Protocol error, msg state(%d), shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support
|
|
|
Could not find transaction table entry, shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support
|
|
|
Protocol error, node state(%d), shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support
|
|
|
Could not find transaction node, shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support
|
|
|
Protocol error, msg state(%d), shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support
|
|
|
Protocol error, msg state(%d), shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support
|
|
|
Protocol error, msg state(%d), shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support
|
|
|
Protocol error, msg state(%d), shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support
|
|
|
Could not find transaction node, shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support
|
|
|
Could not find transaction node, shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support
|
|
|
Could not find transaction node, shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support
|
|
|
Could not find transaction node, shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support
|
|
|
Protocol error, node state(%d), shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support
|
|
|
Protocol error, node state(%d), shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support
|
|
|
Protocol error, node state(%d), shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support
|
|
|
Protocol error, node state(%d), shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support
|
|
|
Protocol error, node state(%d), shutdown Gateway!
|
| |
|
An internal processing error has occurred.
|
| |
|
Contact Unisys Customer Support
|
|
|
No OSI/TP service provider, shutdown OSITP domain gateway
|
| |
|
The local OSITP domain is not defined in the DM_OSITPX section of the domain configuration file.
|
| |
|
Check the domain configuration file definition and add the DM_OSITPX information for the Local Domain if necessary, reload the domain configuration file and restart the OSITP gateway process.
|
