Set preferences

This topic describes the Transfer CFT tasks that you can define in the Preference window, such as:

  • Modify Tooltip variables
  • Define Date and Time display
  • Define filter and buffer properties
  • View version history
Note Commands are submitted to the current CFTCOM. You can select the CFTCOM in the Default COM field of the Transfer CFT files management window.

Commands and transfers that are affected by the current CFTCOM include:

  • Transfer command wizards
  • Delete catalog records
  • File management
  • Switch
  • Purge
  • Mquery

In the Options menu, click Preferences. The Preferences window is displayed.

General parameters tab

Option

Description

Date and Time format

Date pattern: Defines the display pattern for the date in Log and Catalog.

Time pattern: Defines the display pattern for the time in Log and Catalog.

Result: Displays the date and time in the format pattern that you select.

[See Date and Time format patterns]

Tooltip delay

Defines the general parameters for the Tooltip display delay.

  • Initial delay: enter the number of milliseconds before the tooltip is displayed
  • Dismiss delay: enter the number of milliseconds before the tooltip disappears
  • Reshow delay: enter the number of milliseconds before the tooltip is displayed again

Advanced properties

This field enables you to define advanced buffer properties.

Properties buffer: Click Clear now Empties the fields properties internal buffer

Object column lists: Restore default returns each object to the default column settings

View version history

Click View to display the complete version history

Option

Description

Minimum time for filter updates

Enter the minimum time, in seconds, before checking for filter updates

Catalog properties

Define the Default catalog refresh for an automatic refresh for the transfer filter

Log properties

Define the Default log refresh for an automatic refresh of the log filter

Display warning above

Displays a warning message when the entire catalog, above the selected number of rows, is requested

Date and Time format

The Date and Time format option in the Preferences window enables you to define how the date and time are displayed in the Log and Catalog. You can modify the current format pattern as needed in this window.

In the Date format field enter the letters that represent the date format pattern you want. In the Time format field enter the letters that represent the time format pattern you want. You can use the letters in the Date and Time Patterns table below to define the pattern.

The resulting format is displayed below the Time and Date fields in the Preferences window. Click Ok to confirm your selection.

Date and Time patterns

Date and time formats are specified by date and time pattern strings. Within date and time pattern strings, un-quoted letters from 'A' to 'Z' and from 'a' to 'z' are interpreted as pattern letters representing the components of a date or time string.

Text can be quoted using single quotes (') to avoid interpretation. "''" represents a single quote. All other characters are not interpreted; they are copied into the output string during formatting, or are matched against the input string during parsing.

The following pattern letters are defined. All other characters from 'A' to 'Z' and from 'a' to 'z' are reserved.

Date and time table

Letter  

Date or Time Component

Presentation  

Examples  

G

Era designator

Text  

AD

y

Year

Year  

1996; 96  

M

Month in year

Month  

July; Jul; 07  

w

Week in year

Number  

27

W  

Week in month

Number  

2

D

Day in year

Number  

189  

d

Day in month

Number  

10

F

Day of week in month

Number  

2

E

Day in week

Text  

Tuesday; Tue  

a

Am/pm marker  

Text  

PM

H

Hour in day (0-23)

Number  

 0

k

Hour in day (1-24)

Number  

24  

K

Hour in am/pm (0-11)

Number  

0

h

Hour in am/pm (1-12)

Number  

12

m

Minute in hour  

Number  

30

s

Second in minute

Number  

55

S

Millisecond  

Number  

978  

z

Time zone

General time zone  

Pacific Standard Time; PST; GMT-08:00  

Z  

Time zone  

RFC 822 time zone

-0800  

Pattern letters are usually repeated, as their number determines the exact presentation. For example dd represents two digits, as there can be two digits in the day of the month.

  • Text: For formatting, if the number of pattern letters is 4 or more, the full form is used; otherwise a short or abbreviated form is used if available. For parsing, both forms are accepted, independent of the number of pattern letters.
  • Number: For formatting, the number of pattern letters is the minimum number of digits, and shorter numbers are zero-padded to this amount. For parsing, the number of pattern letters is ignored unless it's needed to separate two adjacent fields.
  • Year: For formatting, if the number of pattern letters is 2, the year is truncated to 2 digits; otherwise it is interpreted as a number.

When parsing, if the number of pattern letters is more than 2, the year is interpreted literally, regardless of the number of digits. So the pattern "MM/dd/yyyy", "01/11/12" parses to Jan 11, 12 A.D.

For parsing with the abbreviated year pattern ("y" or "yy"), pattern fields must interpret the abbreviated year relative to some century. It does this by adjusting dates to be within 80 years before and 20 years after the time the date is created. For example, using a pattern of "MM/dd/yy" and a date created on Jan 1, 1997, the string "01/11/12" would be interpreted as Jan 11, 2012 while the string "05/04/64" would be interpreted as May 4, 1964.

During parsing, only strings consisting of exactly two digits are parsed into the default century. Any other numeric string, such as a one digit string, a three or more digit string, or a two digit string that is not all digits (for example, "-1"), is interpreted literally. So "01/02/3" or "01/02/003" are parsed, using the same pattern, as Jan 2, 3 AD. Likewise, "01/02/-3" is parsed as Jan 2, 4 BC.

  • Month: If the number of pattern letters is 3 or more, the month is interpreted as text; otherwise, it is interpreted as a number.
  • General time zone: Time zones are interpreted as text if they have names. For time zones representing a GMT offset value, the following syntax is used:

     GMTOffsetTimeZone:

             GMT Sign Hours : Minutes

     Sign: one of

             + -

     Hours:

             Digit

             Digit Digit

     Minutes:

             Digit Digit

     Digit: one of

             0 1 2 3 4 5 6 7 8 9

Hours must be between 0 and 23, and Minutes must be between 00 and 59. The format is independent of the local, and you must use digits from the Unicode standard Basic Latin block.

For parsing, RFC 822 time zones are also accepted.

  • RFC 822 time zone: For formatting, use the RFC 822 4-digit time zone format:

     RFC822TimeZone:

             Sign TwoDigitHours Minutes

     TwoDigitHours:

             Digit Digit

TwoDigitHours must be between 00 and 23. Other definitions are the same as for general time zones.

For parsing, general time zones are also accepted.

Examples

The following examples show how date and time patterns are interpreted in the U.S. locale. The given date and time are 2018-07-04 12:08:56 local time in the "U.S. Pacific Time" time zone.

Use this date and time pattern...

Resulting display for pattern...

"yyyy.MM.dd G 'at' HH:mm:ss z"  

2018.07.04 AD at 12:08:56 PDT

"EEE, MMM d, ''yy"  

Wed, Jul 4, '18

"h:mm a"  

12:08 PM

"hh 'o''clock' a, zzzz"  

12 o'clock PM, Pacific Daylight Time

"K:mm a, z"

0:08 PM, PDT

"yyyyy.MMMMM.dd GGG hh:mm aaa"  

02018.July.04 AD 12:08 PM  

"EEE, d MMM yyyy HH:mm:ss Z"  

Wed, 4 Jul 2018 12:08:56 -0700

"yyMMddHHmmssZ"

180704120856-0700

"yyyy-MM-dd'T'HH:mm:ss.SSSZ"

2018-07-04T12:08:56.235-0700

For more information on Time and Date pattern formats refer to: http://java.sun.com/j2se/1.4.2/docs/api/java/text/SimpleDateFormat.html

 

Related Links