|
Purpose Use the PAss subcommand to supply
a password or password phrase to a remote host.
Format
>>-PAss--password--+------------------+--+-----------+---------->
'-/newpass/newpass-' '-:userdata-'
>--+---------------------+-------------------------------------><
'-account_information-'
Parameters - password
- Specifies your password or password phrase on the remote host
used to log in to the FTP server.
- /newpass/newpass
- An optional parameter that resets a password or password phrase
to newpass.
Requirement: If the security product of your FTP server host is RACF® or another SAF-compliant security
product, password and newpass must both be passwords, or both be password phrases.
- :userdata
- The optional user data must be separated from the password information
by a colon (:). It can be any combination of up to 200 characters
except the colon and the space (blank). Beware 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 password.
Rules: - The PAss subcommand must be preceded by the User subcommand. For
some sites, the password completes your identification for access
control on the remote host.
- Do not place any spaces between the passwords and the slashes
(/), and the :userdata parameter.
- If the password or newpass parameter contains blanks, enclose the entire password/newpass/newpass:userdata sequence with quotation
marks. If the password, newpass, or user data parameter itself contains
a quotation mark, use the other style of quotation marks to enclose
the parameters.
Examples:
pass "What's up, Doc?"
pass "What's up, Doc?/Not
much; you?/Not much; you?"
pass "What's up, Doc?/Not
much; you?/Not much; you?:I-coded-userdata-today"
but not:
pass 'What's up, Doc?'
pass "What's up, Doc?"/"Not much; you?"/"Not much; you?"
pass "What's up, Doc?"/Not-much;-you?/Not-much;-you?
pass "What's up, Doc?/Not much; you?/Not much; you?":I-coded-userdata-today
- Enter the account information that contains blanks by enclosing
the entire account information parameter in quotation marks. You
can use single or double quotation marks. If the account information
itself contains a quotation mark, use the other style of quotation
marks to enclose the password phrase.
Example: Enter the account information What's up, Doc? as "What's up, Doc?", but not as 'What's up, Doc?'.
- Do not use quotation marks to enclose a password/newpass/newpass:userdata parameter sequence 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 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".
Restrictions: - A password, password phrase, 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 password,
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 password phrase "What's
up, Doc?" with the double quotation marks as part of the password
phrase cannot be entered at the z/OS FTP client because it contains 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 arguments password/newpass/newpass:userdata account_information, such that password and newpass are password phrases, you must take this
into account.
|