15.00 - Completion Message - FastLoad

Teradata FastLoad Reference

prodname
FastLoad
vrm_release
15.00
category
Programming Reference
featnum
B035-2411-034K

Completion Message

The completion message indicates that the Teradata FastLoad job was either paused or terminated, depending on whether the job was in the loading phase or not:

Table 38 describes the possible LOGOFF command Completion messages.

 

Table 38: LOGOFF Command Completion Messages 

Job

Teradata FastLoad Response Layout

If the Job is in the loading phase

*** 16:09:18 Logging off all sessions
*** 16:09:21 Total processor time used = '0.374402 Seconds'
    .        Start : Fri Jan 10 16:08:59 2014
    .        End   : Fri Jan 10 16:09:21 2014
    .        Highest return code encountered = '4'.
*** 16:09:21 FastLoad Paused

If the Job is not in the loading phase

**** 16:11:42 Logging off all sessions
**** 16:11:45 Total processor time used = '0.358802 Seconds'
     .        Start : Fri Jan 10 16:11:20 2014
     .        End   : Fri Jan 10 16:11:45 2014
     .        Highest return code encountered = '0'.
**** 16:11:45 FDL4818 FastLoad Terminated

Note: After FastLoad successfully requests disconnecting all sessions, it displays either “FDL4818 FastLoad Paused” or “FDL4818 FastLoad Terminated,” but all the sessions might not be logged off (disconnected).

LOGON

Purpose  

The LOGON command establishes one or more Teradata FastLoad sessions with the Teradata Database.

Syntax  

Standard LOGON Syntax

Single Signon LOGON Syntax

where:

 

Syntax Element

Description

username

If the database does not support EON feature, a user identifier can have up to 30 bytes.

If the database supports EON feature, a user identifier can have up to 128 characters.

password

Password associated with the username.

If the database does not support EON feature, a password can have up to 30 bytes.

If the database supports EON feature, a password can have up to 128 characters.

Passwords that contain special characters must be enclosed in double quotes.

tdpid

Optional character string that identifies the name of a TDP.

The tdpid string can have from 1 to 8 characters.

Networkattached systems: The tdpid string can have up to 256 characters and can be a domain name system (DNS) name.

The tdpid is the name of the host entered in the network hosts file. If this field is not supplied, tdpid defaults to the TDP established for the user by the system administrator.

Mainframeattached systems: The tdpid string must be in the form:

    TDPn

where n is the TDP identifier.

acctid

Account associated with the username

If the database does not support EON feature, a account identifier can have up to 30 bytes.

If the database supports EON feature, a account identifier can have up to 128 characters.

If omitted, Teradata FastLoad uses the default account identifier defined when the user was created.

Usage Notes

Table 39 describes the things to consider when using the LOGON command.

 

Table 39: Usage Notes for LOGON 

Topic

Usage Notes

Logon Parameters

For standard logon, the parameters (tdpid, username, password, and acctid) are used in all sessions established with the Teradata Database. The LOGON command may occur only once.

For single signon logon, if the Gateway to Teradata Database is configured to use single signon (SSO), and the user is already logged on to the Teradata client machine, the machine name, user name, and password are not required in the LOGON command. The user name and password combination specified when the user logged on to the Teradata client machine are authenticated via network security for a single signon such that valid Teradata users will be permitted to log on to the Teradata Database. The use of SSO is strictly optional, unless the Gateway has been configured to accept only SSOstyle logons.

To connect to a Teradata Database other than the one currently logged on, the TDPid must be included in the LOGON command. If the TDPid is not specified, the default contained in clispb.dat will be used. Refer to the Teradata Call-Level Interface Version 2 Reference for Network-Attached Systems (B035‑2418) for information about setting defaults.

To be interpreted correctly, the TDPid must be followed by the slash separator (‘/’) to distinguish the TDPid from a Teradata Database username. For example, to connect to slugger, enter one of the following:

    .LOGON slugger/;

    .LOGON slugger/,,'acctinfo';

If an account ID is to be used, the optional account ID must be specified in the LOGON command.

Note: To prevent the password from appearing in the script, use Teradata Wallet. Refer to Security Administration (B0351100) and the appropriate installation guide for more information.

Starting Teradata FastLoad

The LOGON command starts a Teradata FastLoad job and automatically establishes:

  • Two Teradata SQL sessions
  • A number of Teradata FastLoad sessions
  • Note: When Teradata FastLoad attempts to connect the Main SQL session the first time and the Teradata Database is down, Teradata FastLoad displays an error message and terminates.

    Note: When Teradata FastLoad attempts to connect the Main SQL session but not the first time, or the Auxiliary SQL session, or the data sessions and the Teradata Database is down. Teradata FastLoad retries to connect 16 times; if the Teradata Database is still down, Teradata FastLoad displays an error message and terminates.

    Number of Sessions

    The number of Teradata FastLoad sessions depends on the system limitations described in “Session Limits” on page 59.

    Number of Sessions (continued)

     

    Teradata FastLoad attempts to connect sessions, in groups of 16, until either:

  • The number of sessions specified with a SESSIONS command are connected
  • A Teradata Database Error 2632 is returned
  • Some other session limit is reached
  • Note: If the number that was specified in a SESSIONS command exceeds the number of available sessions, Teradata FastLoad logs only the number of available sessions.

    Reported Sessions

    After a LOGON command is entered, Teradata FastLoad reports the number of Teradata FastLoad sessions that are logged on. The Teradata SQL sessions are not included in this report.

    Character Support

    Current multi-byte character support of an object name is limited to 30 bytes for the database that does not support EON and limited to 128 characters for the database that supports EON.

    The limitation applies to username, passwd, and account in the logon string.

    CLI treats logon strings of UTF‑8 and other Teradata-supported multi‑byte character sets (Chinese, Japanese, Korean) as ASCII. CLI does not convert before parsing, so some logon strings with multi-byte characters (or a combination of multi-byte characters plus ASCII) could fail if the total size of an object name is over 30 bytes for the database that does not support EON and is over 128 characters for the database that supports EON.

    The work around is to create object names that are less than 30 bytesfor the database that does not support EON are less than 128 characters for the database that supports EON.

    Example  

    The following command example logs on user Peterson:

    LOGON DBC/peterson,HTims ;