PTechDetailRecord Class

Properties   Methods   Events   Config Settings   Errors  

The PTechDetailRecord class is a tool used to create off-line Credit or Force transactions to be settled by the PTECHMANUALSETTLE class. The PTDetailRecord class may also be used to modify the XML aggregates returned by the PTECHCHARGE class's GetDetailAggregate method.

Syntax

dpaymentssdk.Ptechdetailrecord

Remarks

Credit and voice-authorization Capture transactions are off-line transactions. This means that there is no authorization of funds using the PTechCharge class. Instead, you must manually add these transactions to the settlement batch. The PTDetailRecord class can be used to create these transactions, which can then be added to the PTechManualSettle class's DetailRecords property.

To create a Credit, first set the TransactionType to dttCredit, and then set the IndustryType and EntryDataSource Next, set the Card, SettlementAmount, and the current TransactionDate and TransactionTime.

Since this is an off-line transaction, the SequenceNumber may be any value (except 0), and need not reflect the next available sequence number used for authorizations. Finally, set the PTechManualSettle class's DetailRecords array property with the value returned by the GetDetailAggregate method. You've just added a Credit to the settlement.

Voice authorization Capture transactions are similar to credits, with the exception that it requires a Voice Authorization code obtained from your acquiring bank's call center. Generally, the purchase of large high-dollar items (cars, appliances, etc) will require the merchant to call and receive a voice authorization. Once this code is received, it should be set to the ApprovalCode property. The following example shows a Force transaction in a Retail environment.

In addition to creating Credit and Force transactions, the PTechDetailRecord class can be used to adjust the Detail Records returned from the PTechCharge class to reflect changes in the SettlementAmount. The most common reasons to modify these detail records are to add a GratuityAmount (tip) to a charge (itResturant IndustryType), or to add additional charges for the itHotel IndustryType. Note that when the SettlementAmount differs from the original authorized amount, the AmountStatus must be updated to asAmountChanged.

Property List

---

The following is the full list of the properties of the class with short descriptions. Click on the links for further details.

Method List

---

The following is the full list of the methods of the class with short descriptions. Click on the links for further details.

Event List

---

The following is the full list of the events fired by the class with short descriptions. Click on the links for further details.

Config Settings

---

The following is a list of config settings for the class with short descriptions. Click on the links for further details.

AmountStatus Property (PTechDetailRecord Class)

Indicates whether SettlementAmount has been modified from the original authorization.

Syntax

public int getAmountStatus();


public void setAmountStatus(int amountStatus);


Enumerated values:
  public final static int asActualAmount = 0;
  public final static int asAmountChanged = 1;

Default Value

0

Remarks

Notes for the Hotel IndustryType:

To obtain the best interchange rate for Visa transactions in the Hotel IndustryType, the check out amount (SettlementAmount) must be within 15% of the original authorization amount. If the SettlementAmount is less than the original authorized amount by more than 15%, you must perform an authorization reversal using the PTechReversal class. This will immediately release funds from the cardholder's open to buy amount. The original transaction must then be settled for the new amount as usual. However, if the SettlementAmount exceeds the original authorized amount by more than 15%, you must submit an incremental authorization to make up the remaining amount. In this case even though there are two separate transactions, they are tied together with the same authorization code. Therefore, only the original authorization (with the newly updated SettlementAmount) is to be sent in the settlement.

Non-Visa transactions do not allow for Incrementals to tie transactions together, nor Reversals to release funds from the cardholder's open to buy amount. There are no restrictions on the difference between the SettlementAmount and the original authorization amount. However, if the merchant suspects that the final transaction amount will be substantially higher than the original authorization amount, the merchant should perform an additional authorization for the difference. This subsequent authorization must be sent to the host as a standard authorization-only transaction, and will not be tied in any way to the original transaction. Both transactions must be present in the settlement.

Notes for the Restaurant IndustryType:

For Visa transactions, to obtain the best interchange rate the SettlementAmount must be within 20% of the authorized amount. The initial authorization must be submitted for the actual transaction amount. It must not be altered to include an additional percentage that accounts for a tip being added before settlement.

The same rule applies to MasterCard transactions, with the exception that MasterCard allows the SettlementAmount to be within 25% of the authorized amount.

There are no rules concerning authorization and settlement amounts for other card types.

This information was accurate at the time this document was written. Please see the Processing and Interchange Guidelines (provided by Paymentech) for updates as well as additional information on interchange rate qualification.

ApprovalCode Property (PTechDetailRecord Class)

The Approval code returned in the response to the authorization linked to this transaction.

Syntax

public String getApprovalCode();


public void setApprovalCode(String approvalCode);

Default Value

""

Remarks

If this is a Forced transaction, ApprovalCode should contain the voice auth code received from the call center. If this is a Credit (Refund) transaction it should remain empty or be space filled.

AuthSource Property (PTechDetailRecord Class)

Indicates the source of the authorization code stored in ApprovalCode .

Syntax

public String getAuthSource();


public void setAuthSource(String authSource);

Default Value

""

Remarks

This field contains a one character code indicating the source of the ApprovalCode. The received code must be stored and submitted in the batch settlement.

Valid source codes:

* Currently in use by Japan Acquirer Services (JAS).

CardExpMonth Property (PTechDetailRecord Class)

Expiration month of the credit card specified by CardNumber .

Syntax

public int getCardExpMonth();


public void setCardExpMonth(int cardExpMonth);

Default Value

1

Remarks

This property contains the expiration date of the customer's credit card. This property must be in the range 1 - 12.

CardExpYear Property (PTechDetailRecord Class)

Expiration year of the credit card specified by CardNumber .

Syntax

public int getCardExpYear();


public void setCardExpYear(int cardExpYear);

Default Value

1

Remarks

This property contains the expiration date of the customer's credit card. This property must be in the range 1 - 12.

CardNumber Property (PTechDetailRecord Class)

Customer's credit card number from the original authorization request.

Syntax

public String getCardNumber();


public void setCardNumber(String cardNumber);

Default Value

""

Remarks

This field contains the customer's credit card number used in the original authorization request. This alphanumeric field can be a maximum of 22 characters long, excluding whitespace and dashes which are stripped out when the property is set.

CardType Property (PTechDetailRecord Class)

Type of the credit card.

Syntax

public String getCardType();


public void setCardType(String cardType);

Default Value

""

Remarks

Paymentech determines the type of credit card used for each authorization, and returns that value to the merchant in the response. The following is a list of card mnemonics and their meanings.

CVVResult Property (PTechDetailRecord Class)

Contains the returned CVV result code if it was requested.

Syntax

public String getCVVResult();


public void setCVVResult(String CVVResult);

Default Value

""

Remarks

If a CVV value was sent in the authorization request, then this one character field will contain the host returned Card Verification Value result code.

ECI Property (PTechDetailRecord Class)

Electronic Commerce Indicator from the original authorization request.

Syntax

public String getECI();


public void setECI(String ECI);

Default Value

""

Remarks

This field should be identical to the ECI property from the original authorization request. This property is used only for eCommerce and Direct Marketing (card not present) transactions, and is ignored for all Card Present (Retail) transactions.

EntryDataSource Property (PTechDetailRecord Class)

Should reflect the Entry Data Source sent in the original authorization request.

Syntax

public int getEntryDataSource();


public void setEntryDataSource(int entryDataSource);


Enumerated values:
  public final static int edsTrack1 = 0;
  public final static int edsTrack2 = 1;
  public final static int edsManualEntryTrack1Capable = 2;
  public final static int edsManualEntryTrack2Capable = 3;
  public final static int edsManualEntryNoCardReader = 4;
  public final static int edsTrack1Contactless = 5;
  public final static int edsTrack2Contactless = 6;
  public final static int edsManualEntryContactlessCapable = 7;
  public final static int edsIVR = 8;
  public final static int edsKiosk = 9;

Default Value

0

Remarks

If sending an off-line credit or capture this property should reflect the way in which the card was presented for the credit or capture.

The following data sources are supported - edsTrack1, edsTrack2, edsManualEntryTrack1Capable, edsManualEntryTrack2Capable, edsManualEntryNoCardReader, edsTrack1Contactless, edsTrack2Contactless, edsManualEntryContactlessCapable

This property is not available at design time.

GoodsIndicator Property (PTechDetailRecord Class)

Indicates the type of goods being sold by an e-Commerce merchant.

Syntax

public int getGoodsIndicator();


public void setGoodsIndicator(int goodsIndicator);


Enumerated values:
  public final static int giPhysicalGoods = 0;
  public final static int giDigitalGoods = 1;

Default Value

0

Remarks

If the merchant is selling physical goods (goods that are shipped or are otherwise tangible) this property must be set to giPhysicalGoods. If the merchant is selling Digital goods, such a membership, or any software or file that is delivered electronically, this field must be set to giDigitalGoods. This property is only valid when the IndustryType is set to itECommerce.

GratuityAmount Property (PTechDetailRecord Class)

Gratuity amount for settling restaurant industry transactions.

Syntax

public String getGratuityAmount();


public void setGratuityAmount(String gratuityAmount);

Default Value

""

Remarks

This field contains the gratuity (tip) amount of the transaction being settled. This amount is only sent when the PTechCharge class's IndustryType is set to "itRestaurant". If a transaction includes a GratuityAmount amount, the SettlementAmount must reflect the total of the original Authorized Amount plus the GratuityAmount.

This must be formatted as a dollar amount with a real decimal point, excluding the dollar sign. For instance "12.00".

Hotel Property (PTechDetailRecord Class)

Contains additional information required for the Hotel/Lodging industry.

Syntax

public PTechHotelInfo getHotel();


public void setHotel(PTechHotelInfo hotel);

Remarks

This property will be sent in both authorizations and detail records when the IndustryType is set to Hotel. At minimum, you should pass the expected Duration, ArrivalDate, expected DepartureDate, and SaleCode. You may pass the ExtraChargeAmount and ExtraChargesCode in the authorization, but those are normally not known until settlement. To process a reservation or any other transaction where the customer and his card are not physically present, set the PreferredCustomer field to True;. This will indicate to Paymentech that the transaction is a card-not-present authorization (PreferredCustomer must be set to False for normal card-present transaction processing).

Please refer to the PTechHotelInfo type for a complete list of fields.

IndustryType Property (PTechDetailRecord Class)

Determines the merchant's industry type.

Syntax

public int getIndustryType();


public void setIndustryType(int industryType);


Enumerated values:
  public final static int pitRetail = 0;
  public final static int pitDirectMarketing = 1;
  public final static int pitECommerce = 2;
  public final static int pitRestaurant = 3;
  public final static int pitHotel = 4;

Default Value

0

Remarks

This property sets the merchant's industry type. Valid values are shown in the table below:

Note: setting the IndustryType to itDirectMarketing or itECommerce will also reset the PINCapability to ppNoPIN.

* Restaurant orders taken over the phone should be processed as itDirectMarketing transactions. Hotel transactions should always be processed in the itHotel IndustryType. Setting the PTechHotelInfo.PreferredCustomer field to True.

InvoiceNumber Property (PTechDetailRecord Class)

Invoice Number from the original authorization request.

Syntax

public String getInvoiceNumber();


public void setInvoiceNumber(String invoiceNumber);

Default Value

""

Remarks

This property should be identical to the InvoiceNumber from the original authorization request.

Level2Data Property (PTechDetailRecord Class)

Supplies extra information for Commercial or Purchasing cards.

Syntax

public PTechLevel2 getLevel2Data();


public void setLevel2Data(PTechLevel2 level2Data);

Remarks

This property can be used to send additional Level II data that may qualify the merchant for a lower Interchange rate for this transaction. However, it is only valid for use with business or government Purchasing or Commercial Cards. This property is only valid for Sale and AuthOnly transactions. The PTechLevel2 type contains the following fields:

Please refer to the PTechLevel2 type for a complete list of fields.

NetworkId Property (PTechDetailRecord Class)

The Authorizing network Id from the original authorization response.

Syntax

public String getNetworkId();


public void setNetworkId(String networkId);

Default Value

""

Remarks

This property should be identical to the NetworkId returned from Paymentech in the authorization response.

SequenceNumber Property (PTechDetailRecord Class)

Sequence number of the transaction.

Syntax

public int getSequenceNumber();


public void setSequenceNumber(int sequenceNumber);

Default Value

1

Remarks

This should be identical to the sequence number sent in the original authorization.

ServerNumber Property (PTechDetailRecord Class)

Used for restaurant transactions: Id number of the server (waiter/waitress) making the transaction.

Syntax

public String getServerNumber();


public void setServerNumber(String serverNumber);

Default Value

""

Remarks

Each server should have his or her own unique Id number.

SettlementAmount Property (PTechDetailRecord Class)

The amount that the customer will be charged.

Syntax

public String getSettlementAmount();


public void setSettlementAmount(String settlementAmount);

Default Value

"0.00"

Remarks

This field contains the final settlement amount of the transaction. In most cases, this is the TransactionAmount from the original authorization request. However, you may settle a lesser amount (ie: Partial shipment or backordered stock). This field must always be greater than zero.

Note: If a transaction includes a GratuityAmount amount, the SettlementAmount must reflect the total of the original authorized amount plus the GratuityAmount (this is only applicable to the itResturant IndustryType).

This must be formatted as a dollar amount with a real decimal point, excluding the dollar sign. For instance "12.00".

Notes for the Hotel IndustryType:

To obtain the best interchange rate for Visa transactions in the Hotel IndustryType, the check out amount (SettlementAmount) must be within 15% of the original authorization amount. If the SettlementAmount is less than the original authorized amount by more than 15%, you must perform an authorization reversal using the PTechReversal class. This will immediately release funds from the cardholder's open to buy amount. The original transaction must then be settled for the new amount as usual. However, if the SettlementAmount exceeds the original authorized amount by more than 15%, you must submit an incremental authorization to make up the remaining amount. In this case even though there are two separate transactions, they are tied together with the same authorization code. Therefore, only the original authorization (with the newly updated SettlementAmount) is to be sent in the settlement.

Non-Visa transactions do not allow for Incrementals to tie transactions together, nor Reversals to release funds from the cardholder's open to buy amount. There are no restrictions on the difference between the SettlementAmount and the original authorization amount. However, if the merchant suspects that the final transaction amount will be substantially higher than the original authorization amount, the merchant should perform an additional authorization for the difference. This subsequent authorization must be sent to the host as a standard authorization-only transaction, and will not be tied in any way to the original transaction. Both transactions must be present in the settlement.

Notes for the Restaurant IndustryType:

For Visa transactions, to obtain the best interchange rate the SettlementAmount must be within 20% of the authorized amount. The initial authorization must be submitted for the actual transaction amount. It must not be altered to include an additional percentage that accounts for a tip being added before settlement.

The same rule applies to MasterCard transactions, with the exception that MasterCard allows the SettlementAmount to be within 25% of the authorized amount.

There are no rules concerning authorization and settlement amounts for other card types.

This information was accurate at the time this document was written. Please see the Processing and Interchange Guidelines (provided by Paymentech) for updates as well as additional information on interchange rate qualification.

TransactionDate Property (PTechDetailRecord Class)

Local Transaction Date from the original authorization response.

Syntax

public String getTransactionDate();


public void setTransactionDate(String transactionDate);

Default Value

"010101"

Remarks

This six digit field contains a local transaction date associated with the transaction being settled. If the transaction was authorized on-line, this field must contain the value returned in the original authorization response message. If the transaction was processed off-line, this field must contain a Point of Sale (POS) device generated date. This field must appear in MMDDYY format.

TransactionTime Property (PTechDetailRecord Class)

Local transaction time from the original authorization response.

Syntax

public String getTransactionTime();


public void setTransactionTime(String transactionTime);

Default Value

"000000"

Remarks

This six digit field contains a local transaction time associated with the transaction being settled. If the transaction was authorized on-line, this field must contain the value returned in the original authorization response message. If the transaction was processed off-line, this field must contain a Point of Sale (POS) device generated time. This field must appear in HHMMSS format.

TransactionType Property (PTechDetailRecord Class)

Indicates transaction type for this detail record.

Syntax

public int getTransactionType();


public void setTransactionType(int transactionType);


Enumerated values:
  public final static int dttSale = 1;
  public final static int dttCapture = 3;
  public final static int dttHotelNoShow = 4;
  public final static int dttCredit = 6;

Default Value

1

Remarks

This property indicates the type of transaction that is being settled.

Note that only credit card transactions are supported here. EBT, Stored Value, Debit, and Canadian Debit cards must be processed with the Host Capture System, and cannot be manually settled.

Note that transactions Voided with the PTechCharge class must be removed from the batch. Voided transactions must not be settled.

Config Method (Ptechdetailrecord Class)

Sets or retrieves a configuration setting.

Syntax

public String config(String configurationString);

Remarks

Config is a generic method available in every class. It is used to set and retrieve configuration settings for the class.

These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the class, access to these internal properties is provided through the Config method.

To set a configuration setting named PROPERTY, you must call Config("PROPERTY=VALUE"), where VALUE is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).

To read (query) the value of a configuration setting, you must call Config("PROPERTY"). The value will be returned as a string.

GetDetailAggregate Method (Ptechdetailrecord Class)

Returns an aggregate containing details of this transaction, which is then used for settlement.

Syntax

public String getDetailAggregate();

Remarks

This method returns an aggregate containing all of the required data to send a transaction to settlement. This aggregate must be passed to the PTechManualSettle class's DetailAggregate array property in order to settle the transaction. If you wish to view or change any part of the aggregate (such as adding a gratuity or additional info for an Installment payment), you may use the PTechDetailRecord class to do so.

Note: This method may only be called after a successful authorization. If the authorization was not successful the method throws an exception.

An example of how this method is used is shown below:

PTechCharge.Sale(); PTechManualSettle.DetailRecord[0] = PTechCharge.GetDetailAggregate();

ParseAggregate Method (Ptechdetailrecord Class)

Parses the aggregate returned from another class's GetDetailAggregate method.

Syntax

public void parseAggregate(String aggregate);

Remarks

This method takes the XML aggregate returned from the PTechCharge class, parses it, and then fills all the properties of the PTechDetailRecord class. While normally you can pass the results of the GetDetailAggregate method call directly to the PTechManualSettle class, sometimes it is necessary to adjust the contents of the XML aggregate first.

Reset Method (Ptechdetailrecord Class)

Clears all properties to their default values.

Syntax

public void reset();

Remarks

This method clears all properties to their default values.

Error Event (Ptechdetailrecord Class)

Information about errors during data delivery.

Syntax

public class DefaultPtechdetailrecordEventListener implements PtechdetailrecordEventListener {
  ...
  public void error(PtechdetailrecordErrorEvent e) {}
  ...
}

public class PtechdetailrecordErrorEvent {
  public int errorCode;
  public String description;
}

Remarks

The Error event is fired in case of exceptional conditions during message processing.

ErrorCode contains an error code and Description contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the Error Codes section.

PTechHotelInfo Type

Contains additional information required for the Hotel/Lodging industry.

Remarks

This type is used in both authorizations and detail records when processing transactions in the hotel/lodging industry type. At minimum, you should pass the expected Duration of stay, ArrivalDate, expected DepartureDate, and SaleCode. You may pass the ExtraChargeAmount and ExtraChargesCode in the authorization, but those are normally not known until settlement. To process a reservation or any other transaction where the customer and his card are not physically present, set the PreferredCustomer field to True;. This will indicate to Paymentech that the transaction is a card-not-present authorization (PreferredCustomer must be set to False for normal card-present transaction processing).

Fields

Constructors

public PTechHotelInfo();

PTechLevel2 Type

Level II Purchase or Commercial Card information.

Remarks

This type allows the merchant to specify additional fields for Commercial Cards or Purchasing Cards for business or government transaction. Supplying the PurchaseId, SalesTax, and ShipToZip for these credit cards can qualify the merchant for a lower Interchange rate.

Fields

Constructors

public PTechLevel2( purchaseId,  salesTax,  shipToZip);

public PTechLevel2();

Config Settings (Ptechdetailrecord Class)

The class accepts one or more of the following configuration settings. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the class, access to these internal properties is provided through the Config method.

PTechDetailRecord Config Settings

Base Config Settings

Trappable Errors (Ptechdetailrecord Class)

PTechDetailRecord Errors

	501   Property length is invalid
	502   Property is set with invalid data.
	504   Luhn digit check failed.
	505   Card date invalid.
	506   Card expired.
	517   Response length mismatch.
	546   Missing property for current method call.

Paymentech Server Errors:

The following is a list of error codes which may be returned by the Paymentech Server. In the case of a server-side error condition, the Code field will contain "E", the error code will be contained in the ApprovalCode field, and the description in Text

Paymentech Issuer Errors

Paymentech Format Errors

Paymentech Host / Setup Errors

Paymentech Debit / EBT Specific Errors

Paymentech Batch Management Errors (use the ErrorCode configuration setting to retrieve this information from the PTechHostSettle class.

HTTP Errors

	118   Firewall Error. Error description contains detailed message.
	143   Busy executing current method.
	151   HTTP protocol error. The error message has the server response.
	152   No server specified in URL
	153   Specified URLScheme is invalid.
	155   Range operation is not supported by server.
	156   Invalid cookie index (out of range).
	301   Interrupted.
	302   Can't open AttachedFile.

TCPClient Errors

	100   You cannot change the RemotePort at this time. A connection is in progress.
	101   You cannot change the RemoteHost (Server) at this time. A connection is in progress.
	102   The RemoteHost address is invalid (0.0.0.0).
	104   Already connected. If you want to reconnect, close the current connection first.
	106   You cannot change the LocalPort at this time. A connection is in progress.
	107   You cannot change the LocalHost at this time. A connection is in progress.
	112   You cannot change MaxLineLength at this time. A connection is in progress.
	116   RemotePort cannot be zero. Please specify a valid service port number.
	117   You cannot change the UseConnection option while the class is active.
	135   Operation would block.
	201   Timeout.
	211   Action impossible in control's present state.
	212   Action impossible while not connected.
	213   Action impossible while listening.
	301   Timeout.
	303   Could not open file.
	434   Unable to convert string to selected CodePage.
	1105   Already connecting. If you want to reconnect, close the current connection first.
	1117   You need to connect first.
	1119   You cannot change the LocalHost at this time. A connection is in progress.
	1120   Connection dropped by remote host.

SSL Errors

	270   Cannot load specified security library.
	271   Cannot open certificate store.
	272   Cannot find specified certificate.
	273   Cannot acquire security credentials.
	274   Cannot find certificate chain.
	275   Cannot verify certificate chain.
	276   Error during handshake.
	280   Error verifying certificate.
	281   Could not find client certificate.
	282   Could not find server certificate.
	283   Error encrypting data.
	284   Error decrypting data.

TCP/IP Errors

	10004   [10004] Interrupted system call.
	10009   [10009] Bad file number.
	10013   [10013] Access denied.
	10014   [10014] Bad address.
	10022   [10022] Invalid argument.
	10024   [10024] Too many open files.
	10035   [10035] Operation would block.
	10036   [10036] Operation now in progress.
	10037   [10037] Operation already in progress.
	10038   [10038] Socket operation on non-socket.
	10039   [10039] Destination address required.
	10040   [10040] Message too long.
	10041   [10041] Protocol wrong type for socket.
	10042   [10042] Bad protocol option.
	10043   [10043] Protocol not supported.
	10044   [10044] Socket type not supported.
	10045   [10045] Operation not supported on socket.
	10046   [10046] Protocol family not supported.
	10047   [10047] Address family not supported by protocol family.
	10048   [10048] Address already in use.
	10049   [10049] Can't assign requested address.
	10050   [10050] Network is down.
	10051   [10051] Network is unreachable.
	10052   [10052] Net dropped connection or reset.
	10053   [10053] Software caused connection abort.
	10054   [10054] Connection reset by peer.
	10055   [10055] No buffer space available.
	10056   [10056] Socket is already connected.
	10057   [10057] Socket is not connected.
	10058   [10058] Can't send after socket shutdown.
	10059   [10059] Too many references, can't splice.
	10060   [10060] Connection timed out.
	10061   [10061] Connection refused.
	10062   [10062] Too many levels of symbolic links.
	10063   [10063] File name too long.
	10064   [10064] Host is down.
	10065   [10065] No route to host.
	10066   [10066] Directory not empty
	10067   [10067] Too many processes.
	10068   [10068] Too many users.
	10069   [10069] Disc Quota Exceeded.
	10070   [10070] Stale NFS file handle.
	10071   [10071] Too many levels of remote in path.
	10091   [10091] Network subsystem is unavailable.
	10092   [10092] WINSOCK DLL Version out of range.
	10093   [10093] Winsock not loaded yet.
	11001   [11001] Host not found.
	11002   [11002] Non-authoritative 'Host not found' (try again or check DNS setup).
	11003   [11003] Non-recoverable errors: FORMERR, REFUSED, NOTIMP.
	11004   [11004] Valid name, no data record (check DNS setup).