z/OS Communications Server: IP User's Guide and Commands
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


User subcommand—Identify yourself to a host or change your TSO user ID password

z/OS Communications Server: IP User's Guide and Commands
SC27-3662-00

Purpose

Use the User subcommand to identify yourself to the remote host after opening a connection. If the remote host is a z/OS® FTP server, you can change your TSO user ID, password, or password phrase.

Format

Read syntax diagramSkip visual syntax diagram
>>-User--user_id--+--------------+-----------------------------><
                  '-| Password |-'   

Read syntax diagramSkip visual syntax diagram
Where Password is

|--password--+----------------------------+--+-----------+------>
             '-/new_password/new_password-'  '-:userdata-'   

>--+---------------------+--------------------------------------|
   '-account_information-'   

Parameters

user_id
Specifies your login name on the host.
password
Specifies your current password or password phase on the host. If you do not supply password when invoking the User subcommand, you are prompted to enter a password if the host requires a password to log in.
new_password/new_password
An optional parameter that specifies your new password or password phase on the host. You must enter the password twice.
Requirement: SAF-compliant security products such as RACF® require that password and new_password both be passwords, or both be password phrases.
:userdata
The optional user data must be separated from the password information by a colon (:) and can be any combination of up to 200 nonblank characters and numbers—except the colon. Care should be taken when using the back slash character (\) in combination with other characters, which might be interpreted as an escape sequence by the C compiler.
account_information
An optional parameter that will be supplied to the remote FTP server if the server requests account information after receiving the password.
Results:
  • Not all FTP servers support the userdata parameter. The z/OS FTP server interprets userdata as a character string and passes it to the server FTCHKPWD user exit routine.
  • If you enter your password or password phrase incorrectly, the client does not prompt you to enter the password again. You must reissue the User subcommand to enter the correct password.
  • If you do not specify password/new_password/new_password on the User subcommand, you can specify it when you are prompted for the password after entering the User subcommand. You can issue the User subcommand to change your TSO user_id password at any time during the FTP session.
Tips:
  • To avoid having your password print when coding your user ID and password as part of a CLIST or batch job, enter your user ID and password on separate lines.
  • You can use the NETRC data set to automatically provide the user ID, password and account information to log in to an FTP server.
Rules:
  • Do not place any spaces between the passwords and the slashes (/), and the user data.
  • Enter a password phrase that contains blanks by enclosing the entire password phrase in quotation marks. You can use single or double quotation marks. If the password phrase itself contains a quotation mark, use the other style of quotation marks to enclose the password phrase.
    Example: Enter the phrase What's up, Doc? as "What's up, Doc?", but not as 'What's up, Doc?'.

    This rule applies also to the account information and user IDs.

  • Do not use quotation marks to enclose a password phrase that is comprised only of any of the following characters:
    • Uppercase or lowercase letters
    • Numerals from 0 to 9
    • The following special characters:
      • @
      • #
      • $
      • -
      • {
      • .
      • (
      • )
      • *
      • %
      • +
    This rule applies also to user IDs and to the account information.
    Example: Enter the password phrase JoeIBMer@ibm.com as JoeIBMer@ibm.com, but not as 'JoeIBMer@ibm.com', nor as "JoeIBMer@ibm.com".
Note: When you use FTP through a proxy that requires two passwords with one for the firewall and the other for the remote system, specify both passwords by enclosing them in quotation marks.
Example: Enter the user IDs NAME1 and NAME2 as 'NAME1 NAME2', or as "NAME1 NAME2".
Restrictions:
  • A password phrase, user ID, or the account information that you enter at the z/OS FTP client must not contain both single quotation mark and double quotation mark characters. You can use either style of quotation marks in the user ID, password phrase, or account information, but not both.
    Example: The password phrase What's up, Doc? is valid because it contains only single quotation marks. You enter it at the z/OS FTP client as "What's up, Doc?". The phrase "What's up, Doc?" with the double quotation marks as part of the phrase cannot be entered at the z/OS FTP client because it contains both styles of quotation marks.

    If you enter the password/new_password/new_password argument, the sequence password/new_password cannot contain both single quotation mark and double quotation mark characters. You can use either style of quotation marks, but not both.

    Example: The password What's up, Doc? and new password Not much; what's up with you? are valid because the two password phrases contain only single quotation marks. You enter it at the z/OS FTP client as "What's up, Doc?/Not much; what's up with you?/Not much; what's up with you". The password phrases "What's up, Doc? " and He said, "not much; you?" cannot be entered as a password/new_password/new_password sequence at the z/OS FTP client because the password phrases use both styles of quotation marks.
  • When entering this subcommand in a USS environment, you can enter only up to 510 characters including the subcommand name. When entering the optional password argument as password/newpass/newpass:userdata account_information, such that password and newpass are password phrases, you must take this into account.
Related Topic: See NETRC data set for information about using NETRC.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2013
This information center is Built on Eclipse™ ( www.eclipse.org ).