Question3

Former Member — Sun, 06 Apr 2008 03:41:31 GMT

sir ,

This are question,

11.What are common transport errors and their codes?

12.Transport request types and its syntax

13.Where will u find transport error logs?

14.How to do transport at OS level?

15.How to transport objects from Production to Development?

16.How to define instances and operation modes?

Re: Question3

Former Member — Sun, 06 Apr 2008 04:17:36 GMT

following are the common transport codes and their error codes

Result code Value Meaning

kOTBadAddressErr -3150 The specified protocol address was in an incorrect format or contained illegal information.

kOTBadOptionErr -3151 The specified protocol options were in an incorrect format or contained illegal information.

kOTAccessErr -3152 The user does not have permission to negotiate the specified address or options.

kOTBadReferenceErr -3153 The specified EndpointRef or TEndpoint * does not refer to a valid endpoint.

kOTNoAddressErr -3154 The endpoint could not allocate an address, or an address was required and not supplied by the client.

kOTOutStateErr -3155 The function was issued in the wrong sequence.

kOTBadSequenceErr -3156 An invalid sequence number was specified, or a NULL call pointer was specified when rejecting a connection request.

kOTLookErr -3158 An asynchronous event has occurred on this endpoint.

kOTBadDataErr -3159 The amount of client data specified was not within the bounds allowed by the endpoint.

kOTBufferOverflowErr -3160 The number of bytes allocated to hold a result is greater than zero, but not sufficient to store the result.

kOTFlowErr -3161 The endpoint is in asynchronous mode, but the flow control mechanism prevents the endpoint from accepting any data at this time.

kOTNoDataErr -3162 This endpoint is in non-blocking mode, but no data is currently available. It is also returned by LookupName when no names are found.

kOTNoDisconnectErr -3163 No disconnect indication is available.

kOTNoUDErrErr -3164 No unit data error indication currently exists on this endpoint.

kOTBadFlagErr -3165 An invalid flag was specified.

kOTNoReleaseErr -3166 No orderly release indication currently exists on this endpoint.

kOTNotSupportedErr -3167 This action is not supported by this endpoint.

kOTStateChangeErr -3168 The endpoint is undergoing a transient state change. This error is returned when a function call is made while an endpoint is in the process of changing states. The client should wait for an event indicating the endpoint has finished changing state and call the function again.

Note: The equivalent state-change error code, TSTATECHNG, is not described in the 1992 X/Open XTI specification.

This error is also returned if you attempt to use an "incompatible" function while another operation is still ongoing (for example: calling SndUData while an OptionManagement call is still outstanding).

kOTStructureTypeErr -3169 An unsupported structure type was passed in the structType field. This error is also returned when the structType field is inconsistent with the endpoint type.

kOTBadNameErr -3170 The endpoint name is invalid.

kOTBadQLenErr -3171 The argument qlen when the endpoint was bound with Bind was zero.

kOTAddressBusyErr -3172 The requested address is in use, or this endpoint does not support multiple connections with the same local and remote addresses. This result code indicates that a connection already exists. As a return value for a Bind call, it may also indicate that no dynamic addresses are available for protocols or configuration methods that allow dynamic addressing.

kOTIndOutErr -3173 There are outstanding connection indications on the endpoint. All other connection indications must be handled either by rejecting them with SndDisconnect, or by accepting them with Accept.

kOTProviderMismatchErr -3174 The endpoint that is to accept the connection is not the same kind of endpoint as this one.

kOTResQLenErr -3175 When this endpoint was bound (see Bind), the qlen parameter was greater than zero. But to accept a connection on an alternate end-point, such as this one, the endpoint must be bound with a qlen parameter equal to zero.

kOTResAddressErr -3176 The address to which this endpoint is bound differs from that of the endpoint that received the connection request; thus, this endpoint cannot accept this connection request.

kOTQFullErr -3177 The maximum number of outstanding indications has been reached for the endpoint.

kOTProtocolErr -3178 An unspecified protocol error occurred.

kOTBadSyncErr -3179 A call to Sync was made at non-SystemTask time.

kOTCanceledErr -3180 An outstanding call was canceled.

kOTNoError 0000 The function completed execution without error.

kENOENTErr -3201 Requested information does not exist. This error literally means no such file or directory. In XTI (and Open Transport), a function returns this result when you try to open an endpoint or mapper that does not exist in the system, or to operate on an

kENIOErr -3204 An I/O error occurred.

kENXIOErr -3205 No such device or address.

kEBADFErr -3208 The provider reference or stream reference supplied to the function was not valid.

kEAGAINErr -3210 A provider is in non-blocking mode and cannot perform this operation now; Open Transport would have to block to complete the request. Try again later.

kENOMEMErr,kOTOutOfMemoryErr -3211 Open Transport cannot allocate enough memory to meet your request. Open Transport has run out of internal memory. This might happen, for example, if you are doing a lot of asynchronous sends and not acknowledging sends, which means that Open Transport has to copy the data being sent into its own internal buffers.

kEBUSYErr -3215 The device you are trying to access is busy and could not complete your request.

kOTDuplicateFoundErr -3216 You are attempting to register a port or other entity that already exists.

kEINVALErr -3221 You attempted an invalid operation, or you passed an invalid parameter.

kEDEADLKErr -3234 In order to complete the requested operation, the endpoint provider would have to block, and the endpoint is in nonblocking mode.

kEADDRINUSEErr -3247 The address is in use and is not available for the current function.

kEADDRNOTAVAILErr -3248 The address is not available or the requested address is not appropriate for the current function because the function requires a multicast address.

kENETDOWNErr -3249 TCP/IP error. The path to a network number is currently unavailable.

kENETUNREACHErr -3250 TCP/IP error. The path to a network number does not exist.

kENETRESETErr -3251 Unknown.

kECONNABORTEDErr -3252 Unknown.

kECONNRESETErr -3253 The connection was reset, possibly due to a problem with security and authentication.

kENOBUFSErr -3254 The operation failed because no buffer space was available.

kEISCONNErr -3255 Reserved.

kENOTCONNErr -3256 Reserved.

kESHUTDOWNErr -3257 An operation was aborted because the machine is shutting down. This error code is also used by sockets.

kETOOMANYREFSErr -3258 Unused error code.

kETIMEDOUTErr -3259 The requested operation timed out.

kECONNREFUSEDErr -3260 TCP/IP error code. The port is unreachable (as opposed to the host being unreachable). The positive version of this error code (kECONNREFUSED) is returned by Open Transport as a reason code in a disconnect message, indicating that the other side refused the connection.

kEHOSTDOWNErr -3263 TCP/IP error. A host address is currently unavailable.

kEHOSTUNREACHErr -3264 TCP/IP error. A host address cannot be reached.

kEPROTOErr -3269 A catastrophic error has occurred which probably renders the underlying stream unusable. This error is the same as the kTPROTOErr, but is used where an XTI error code is not appropriate.

kETIMEErr -3270 An Ioctl command has timed out instead of completing normally.

kENOSRErr -3271 Open Transport cannot allocate enough system resources (usually stream messages) to meet your request.

kOTClientNotInittedErr -3279 The client has not called the InitOpenTransport function or the InitOpenTransportUtilities function.

kOTPortHasDiedErr -3280 Your notifier is sent the event kOTProviderIsClosed and returns this result code if a port that your provider is using is disabled because it was unregistered.

kOTPortWasEjectedErr -3281 Your notifier is sent the event kOTProviderIsClosed and returns this result code.

kOTBadConfigurationErr -3282 Open Transport is attempting to bring up the TCP/IP stack but can't because it's improperly configured in the TCP/IP control panel.

kOTConfigurationChangedErr -3283 This is an event code that's sent to the client's notifier (the one you register with the OTRegisterAsClient function) when variister with the OTRegisterAsClient function) when various AppleTalk-related things (like the current zone) change.

kOTUserRequestedErr -3284 Your notifier is sent the event kOTProviderIsClosed and returns this result code if a port that your provider is using is disabled because the user switched configurations.

kOTPortLostConnection -3285 Your notifier is sent the event kOTProviderIsClosed and returns this result code if a port that your provider is using is disabled because it lost the connection.

Re: Question3

Former Member — Sun, 06 Apr 2008 04:21:19 GMT

Transport Request types

National Codes:

01 Emergency Transport Request

02 Urgent Transport Request

03 Special Transport Request

04 Planned Transport Request

Syntax::

If you want to copy the SAP defaults to your own check indicators and field values, or you want to maintain them, your changes are recorded in the correction and transport systems. By executing the corresponding transport request, you distribute your check indicators in the system. Objects in it have the following syntax:

R3TR SUSK <Transaction name>

<Transaction name> corresponds to the normal SAP transaction names. The check indicators and field values are included in the transport. Check indicators are saved in table USOBX_C, field values for the Profile Generator in table USOBT_C.

Do reward if helpful

Re: Question3

Former Member — Sun, 06 Apr 2008 04:30:43 GMT

you can import a transport request by using the command tp import request no . tp import all will import all the transports.Also mention the client to which u want the import.

find more at http://sap.ittoolbox.com/groups/technical-functional/sap-basis/importing-a-transport-request-at-os-level-1612271

Regarding instance and operation code, please visit http://help.sap.com/saphelp_nw70/helpdata/en/c4/3a5ed1505211d189550000e829fbbd/content.htm

I hope this solves your queries....

do reward if helpful or get back for further queries

topic Re: Question3 in Application Development and Automation Discussions

Question3

Re: Question3

Re: Question3

Re: Question3