Input: [Parameter] status [Default] - [Description]

Output: Single letter value defining the initial status of this worker: 'D' is disabled, 'S' is stopped, 'I' is ignore-errors, 'H' is hot-standby and 'E' is in an error state. Status can be set (which is the default) by prepending with '+' or cleared by prepending with '-'. Thus, a setting of 'S-E' sets this worker to Stopped and clears the in-error flag.


Input: [Parameter] timeout [Default] ProxyTimeout [Description]

Output: Connection timeout in seconds. The number of seconds Apache waits for data sent by / to the backend.


Input: [Parameter] ttl [Default] - [Description]

Output: Time To Live for the inactive connections above the smax connections in seconds. Apache will close all connections that has not been used inside that time period.


Input: [Type Code] BILL [Type Description] Billing Address [Ref Data Name]

Output: Address Type

Reference Data - Tutorial4 Best Practice in MDM


Input: [Type Code] DEL_1 [Type Description] Delivery Address [Ref Data Name]

Output: Address Type

Reference Data - Tutorial4 Best Practice in MDM


Input: [Type Code] WH [Type Description] Warehouse [Ref Data Name]

Output: Address Type

Reference Data - Tutorial4 Best Practice in MDM


Input: [Type Code] CANC [Type Description] Cancelled [Ref Data Name]

Output: Order Status

Reference Data - Tutorial4 Best Practice in MDM


Input: [Type Code] COM [Type Description] Completed [Ref Data Name]

Output: Order Status

Reference Data - Tutorial4 Best Practice in MDM


Input: [Type Code] DEL [Type Description] Delivered [Ref Data Name]

Output: Order Status

Reference Data - Tutorial4 Best Practice in MDM


Input: [Type Code] PAID [Type Description] Paid [Ref Data Name]

Output: Order Status

Reference Data - Tutorial4 Best Practice in MDM


Input: [Type Code] PT [Type Description] Part-Filled [Ref Data Name]

Output: Order Status

Reference Data - Tutorial4 Best Practice in MDM


Input: [Type Code] AmEx [Type Description] American Express [Ref Data Name]

Output: Payment Method

Reference Data - Tutorial4 Best Practice in MDM


Input: [Type Code] CHK [Type Description] Check or Cheque [Ref Data Name]

Output: Payment Method

Reference Data - Tutorial4 Best Practice in MDM


Input: [Type Code] CSH [Type Description] Cash [Ref Data Name]

Output: Payment Method

Reference Data - Tutorial4 Best Practice in MDM


Input: [Type Code] DD [Type Description] Direct Debit [Ref Data Name]

Output: Payment Method

Reference Data - Tutorial4 Best Practice in MDM


Input: [Type Code] MC [Type Description] Master Card [Ref Data Name]

Output: Payment Method

Reference Data - Tutorial4 Best Practice in MDM


Input: [Type Code] Book [Type Description] Book [Ref Data Name]

Output: Product Type

Reference Data - Tutorial4 Best Practice in MDM


Input: [Type Code] CD [Type Description] CD [Ref Data Name]

Output: Product Type

Reference Data - Tutorial4 Best Practice in MDM


Input: [Type Code] Coffee [Type Description] Coffee [Ref Data Name]

Output: Product Type

Reference Data - Tutorial4 Best Practice in MDM


Input: [Type Code] DVD [Type Description] DVD [Ref Data Name]

Output: Product Type

Reference Data - Tutorial4 Best Practice in MDM


Input: [Type Code] General [Type Description] General [Ref Data Name]

Output: Product Type

Reference Data - Tutorial4 Best Practice in MDM


Input: [Type Code] TBD [Type Description] To Be Determined [Ref Data Name]

Output: Product Type

Reference Data - Tutorial4 Best Practice in MDM


Input: [Variable name] PLC_AT_DEST_AREA_TAG [Default] none [Description] resource name of an area transition door's destination area [Type]

Output: string


Input: [Variable name] PLC_AT_DEST_TAG [Default] none [Description] resource name of the waypoint within that area to send the PC to. [Type]

Output: string


Input: [Variable name] PLC_AT_WORLD_MAP_ACTIVE_1 to 5 [Default] none [Description] resource name of pins on the world map that should be made active when the player uses this area transition to reach the world map. [Type]

Output: string


Input: [Variable name] PLC_CODEX_FLAG [Default] -1 [Description] Flag within the CODEX_PLOT plot that is set when this placeable is examined. [Type]

Output: int


Input: [Variable name] PLC_CODEX_PLOT [Default] none [Description] resource name of a plot containing a codex page that is given to the player when this placeable is examined. [Type]

Output: string


Input: [Variable name] PLC_COUNTER_1 to 3 [Default] 0 [Description] generic counter variables [Type]

Output: int


Input: [Variable name] PLC_DO_ONCE_A and B [Default] 0 [Description] flags for behaviors that happen only once [Type]

Output: int


Input: [Variable name] PLC_FLIP_COVER_USE_COUNT [Default] 0 [Description] Flip cover has been removed from the default ruleset [Type]

Output: int


Input: [Variable name] PLC_SPAWN_NON_INTERACTIVE [Default] 0 [Type]

Output: int


Input: [Variable name] TS_TREASURE_GENERATED [Description] See Treasure system [Type]

Output: int


Input: [Description] implementation name of server [Name]

Output: implementationName

PHP/YAZ Connection Options


Input: [Description] implementation version of server [Name]

Output: implementationVersion

PHP/YAZ Connection Options


Input: [Description] implementation ID of server [Name]

Output: implementationId

PHP/YAZ Connection Options


Input: [Description] schema for retrieval. By default, no schema is used. Setting this option is equivalent to using function yaz_schema() [Name]

Output: schema

PHP/YAZ Connection Options


Input: [Description] record syntax for retrieval. By default, no syntax is used. Setting this option is equivalent to using function yaz_syntax() [Name]

Output: preferredRecordSyntax

PHP/YAZ Connection Options


Input: [Description] offset for first record to be retrieved via yaz_search() or yaz_present(). First record is numbered has a start value of 0. Second record has start value 1. Setting this option in combination with option count has the same effect as calling yaz_range() except that records are numbered from 1 in yaz_range() [Name]

Output: start

PHP/YAZ Connection Options


Input: [Description] maximum number of records to be retrieved via yaz_search() or yaz_present(). [Name]

Output: count

PHP/YAZ Connection Options


Input: [Description] element-set-name for retrieval. Setting this option is equivalent to calling yaz_element(). [Name]

Output: elementSetName

PHP/YAZ Connection Options


Input: [Name] InternetGatewayDevice.Capabilities.PerformanceDiagnostic. [Requirement]


Input: [Name] UploadTransports [Requirement]


Input: [Name] InternetGatewayDevice.UploadDiagnostics. [Requirement]


Input: [Name] DiagnosticsState [Requirement]


Input: [Name] Interface [Requirement]


Input: [Name] UploadURL [Requirement]


Input: [Name] DSCP [Requirement]


Input: [Name] EthernetPriority [Requirement]


Input: [Name] ROMTime [Requirement]


Input: [Name] BOMTime [Requirement]


Input: [Name] EOMTime [Requirement]


Input: [Name] TestFileLength [Requirement]


Input: [Name] TotalBytesSent [Requirement]


Input: [Button] D-Pad Up [Function]

Output: Increase block size


Input: [Button] D-Pad Down [Function]

Output: Decrease block size


Input: [Button] D-Pad Left [Function]

Output: Rotate left


Input: [Button] D-Pad Right [Function]

Output: Rotate right


Input: [Button] A Button [Function]

Output: Grab/place block


Input: [Button] B Button [Function]

Output: [Hold] Copy block/[Press] Delete block


Input: [Button] Point Remote [Function]

Output: Move cursor


Input: [Button] Control Stick [Function]

Output: Rotate building area/Zoom in or out


Input: [Key to Press] Alt-Period [Description]

Output: Line Next


Input: [Key to Press] Alt-Comma [Description]

Output: Line Prior


Input: [Key to Press] Alt-Apostrophe [Description]

Output: Spelling/Grammar Next


Input: [Key to Press] Alt-Semicolon [Description]

Output: Spelling/Grammar Prior


Input: [Key to Press] Alt-Right Bracket [Description]

Output: Revision Next


Input: [Key to Press] Alt-Left Bracket [Description]

Output: Revision Prior


Input: [Key to Press] Insert-Right Arrow [Description]

Output: Cell Right


Input: [Key to Press] Insert-Left Arrow [Description]

Output: Cell Left


Input: [Key to Press] Insert-Up Arrow [Description]

Output: Cell Up


Input: [Key to Press] Insert-Down Arrow [Description]

Output: Cell Down


Input: [Key to Press] Control-Insert-Left Arrow [Description]

Output: To First Cell of Row


Input: [Key to Press] Control-Insert-Right Arrow [Description]

Output: To Last Cell of Row


Input: [Key to Press] Control-Insert-Up Arrow [Description]

Output: To First Cell of Column


Input: [Key to Press] Control-Insert-Down Arrow [Description]

Output: To Last Cell of Column


Input: [Key to Press] Insert-Home [Description]

Output: To Top Left Cell


Input: [Key to Press] Insert-End [Description]

Output: To Bottom Right Cell


Input: [Key to Press] Shift-Insert-Down Arrow [Description]

Output: Row


Input: [Key to Press] Shift-Insert-Left Arrow [Description]

Output: From Row Start


Input: [Key to Press] Shift-Insert-Right Arrow [Description]

Output: Row To End


Input: [Key to Press] Shift-Insert-Up Arrow [Description]

Output: First Row Cell


Input: [Key to Press] Alt-Insert-Down Arrow [Description]

Output: Column


Input: [Key to Press] Alt-Insert-Left Arrow [Description]

Output: From Column Start


Input: [Key to Press] Alt-Insert-Right Arrow [Description]

Output: Column To End


Input: [Key to Press] Alt-Insert-Up Arrow [Description]

Output: First Column Cell


Input: [Key to Press] Insert-Numpad-Enter [Description]

Output: Current Cell


Input: [Key to Press] Insert-E [Description]

Output: Element Properties


Input: [Key to Press] Insert-Tab [Description]

Output: Page Navigation


Input: [Key to Press] Alt-Shift-H [Description]

Output: Headers and Totals


Input: [Key to Press] Alt-Shift-M [Description]

Output: Monitor Cells


Input: [Key to Press] Alt-Shift-! [Description]

Output: Monitor Cell 1


Input: [Key to Press] Alt-Shift-@ [Description]

Output: Monitor Cell 2


Input: [Key to Press] Alt-Shift-# [Description]

Output: Monitor Cell 3


Input: [Key to Press] Alt-Shift-$ [Description]

Output: Monitor Cell 4


Input: [Key to Press] Alt-Shift-% [Description]

Output: Monitor Cell 5


Input: [Key to Press] Alt-Shift-^ [Description]

Output: Monitor Cell 6


Input: [Key to Press] Alt-Shift-& [Description]

Output: Monitor Cell 7


Input: [Key to Press] Alt-Shift-Star [Description]

Output: Monitor Cell 8


Input: [Key to Press] Alt-Shift-( [Description]

Output: Monitor Cell 9


Input: [Key to Press] Alt-Shift-) [Description]

Output: Monitor Cell 10


Input: [Key to Press] Alt-Shift-A [Description]

Output: Any Monitor Cell


Input: [Key to Press] Alt-Shift-T [Description]

Output: Read Total Cell


Input: [Key to Press] Alt-Shift-C [Description]

Output: Read Comment


Input: [Key to Press] Alt-Shift-F [Description]

Output: Read Formula


Input: [Key to Press] Alt-Shift-P [Description]

Output: Previous Cell


Input: [Key to Press] Insert-C [Description]

Output: Outlook Calendar


Input: [PREFIX] CONSTRUCT [2] DESCRIBE [3] ASK [BASE]

Output: SELECT


Input: [PREFIX] LIMIT [2] OFFSET [3] DISTINCT [4] REDUCED [BASE]

Output: ORDER BY


Input: [PREFIX] FROM NAMED [2] WHERE [BASE]

Output: FROM


Input: [PREFIX] OPTIONAL [2] UNION [3] FILTER [4] a [BASE]

Output: GRAPH


Input: [PREFIX] LANG [2] LANGMATCHES [3] DATATYPE [4] BOUND [5] sameTERM [BASE]

Output: STR


Input: [PREFIX] isIRI [2] isLITERAL [3] REGEX [4] true [5] false [6] isBLANK [BASE]

Output: isURI


Input: [field] size [description]

Output: A human-readable description of the file size (translated by locale).


Input: [field] bytes [description]

Output: The file size in bytes.


Input: [field] path [description]

Output: Returns the canonical path to the file or folder.


Input: [field] is_dir [description]

Output: Whether the given entry is a folder or not.


Input: [field] is_deleted [description]

Output: Whether the given entry is deleted (only included if deleted files are being returned).


Input: [field] rev [description]

Output: A unique identifier for the current revision of a file. This field is the same rev as elsewhere in the API and can be used to detect changes and avoid conflicts.


Input: [field] hash [description]

Output: A folder's hash is useful for indicating changes to the folder's contents in later calls to /metadata. This is roughly the folder equivalent to a file's rev.


Input: [field] thumb_exists [description]

Output: True if the file is an image that can be converted to a thumbnail via the /thumbnails call.


Input: [field] photo_info [description]

Output: Only returned when the include_media_info parameter is true and the file is an image. A dictionary that includes the creation time (time_taken) and the GPS coordinates (lat_long).


Input: [field] video_info [description]

Output: Only returned when the include_media_info parameter is true and the file is a video. A dictionary that includes the creation time (time_taken), the GPS coordinates (lat_long), and the length of the video in milliseconds (duration).


Input: [field] icon [description]

Output: The name of the icon used to illustrate the file type in Dropbox's icon library.


Input: [field] modified [description]

Output: The last time the file was modified on Dropbox, in the standard date format (not included for the root folder).


Input: [field] client_mtime [description]

Output: For files, this is the modification time set by the desktop client when the file was added to Dropbox, in the standard date format. Since this time is not verified (the Dropbox server stores whatever the desktop client sends up), this should only be used for display purposes (such as sorting) and not, for example, to determine if a file has changed or not.


Input: [field] root [description]

Output: The root or top-level folder depending on your access level. All paths returned are relative to this root level. Permitted values are either dropbox or app_folder.


Input: [field] revision [description]

Output: A deprecated field that semi-uniquely identifies a file. Use rev instead.


Input: [field] shared_folder [description]

Output: This field will be included for shared folders. The value is a dictionary with the field id. If the include_membership parameter is passed, there will additionally be a membership field and a groups field. See /shared_folders for a sample shared folder response.


Input: [field] read_only [description]

Output: For shared folders, this field specifies whether the user has read-only access to the folder. For files within a shared folder, this specifies the read-only status of the parent shared folder.


Input: [field] parent_shared_folder_id [description]

Output: For files within a shared folder, this field specifies the ID of the containing shared folder.


Input: [field] modifier [description]

Output: For files within a shared folder, this field specifies which user last modified this file. The value is a user dictionary with the fields uid (user ID), display_name, and, if the linked account is a member of a Dropbox for Business team, same_team (whether the user is on the same team as the linked account). If this endpoint is called by a Dropbox for Business app and the user is on that team, a member_id field will also be present in the user dictionary. If the modifying user no longer exists, the value will be null.


Input: [Name] name [Required] yes [Description] datasource name, used as a Spring bean suffix, e.g. ‘ds2′ [Type]

Output: String

An Army of Solipsists » Blog Archive » A Grails Plugin for Multiple DataSources


Input: [Name] readOnly [Required] no, defaults to false [Description] if true, the datasource and corresponding transactional services will be read-only [Type]

Output: boolean

An Army of Solipsists » Blog Archive » A Grails Plugin for Multiple DataSources


Input: [Name] driverClassName [Required] yes [Description] same as in DataSource [Type]

Output: String

An Army of Solipsists » Blog Archive » A Grails Plugin for Multiple DataSources


Input: [Name] url [Required] yes [Description] same as in DataSource [Type]

Output: String

An Army of Solipsists » Blog Archive » A Grails Plugin for Multiple DataSources


Input: [Name] username [Required] no [Description] same as in DataSource [Type]

Output: String

An Army of Solipsists » Blog Archive » A Grails Plugin for Multiple DataSources


Input: [Name] password [Required] no [Description] same as in DataSource [Type]

Output: String

An Army of Solipsists » Blog Archive » A Grails Plugin for Multiple DataSources


Input: [Name] dbCreate [Required] yes [Description] same as in DataSource [Type]

Output: String

An Army of Solipsists » Blog Archive » A Grails Plugin for Multiple DataSources


Input: [Name] dialect [Required] yes (no autodetect) [Description] same as in DataSource [Type]

Output: String or Class

An Army of Solipsists » Blog Archive » A Grails Plugin for Multiple DataSources


Input: [Name] jndiName [Required] no [Description] same as in DataSource [Type]

Output: String

An Army of Solipsists » Blog Archive » A Grails Plugin for Multiple DataSources


Input: [Name] pooled [Required] no, defaults to false [Description] same as in DataSource [Type]

Output: boolean

An Army of Solipsists » Blog Archive » A Grails Plugin for Multiple DataSources


Input: [Name] loggingSql [Required] no, defaults to false [Description] same as in DataSource [Type]

Output: boolean

An Army of Solipsists » Blog Archive » A Grails Plugin for Multiple DataSources


Input: [Name] logSql [Required] no, defaults to false [Description] same as in DataSource [Type]

Output: boolean

An Army of Solipsists » Blog Archive » A Grails Plugin for Multiple DataSources


Input: [Name] environments [Required] no, defaults to [‘development’, ‘test’, ‘production’] [Description] list of environments this DataSource should be active in [Type]

Output: List

An Army of Solipsists » Blog Archive » A Grails Plugin for Multiple DataSources


Input: [Name] domainClasses [Required] yes [Description] the domain classes that should use this DataSource [Type]

Output: List or List

An Army of Solipsists » Blog Archive » A Grails Plugin for Multiple DataSources


Input: [Name] services [Required] no [Description] short names of the services that should use this DataSource (same as Spring bean without ‘Service’, e.g. ‘user’ for UserService) [Type]

Output: List

An Army of Solipsists » Blog Archive » A Grails Plugin for Multiple DataSources


Input: [Option] -c [Description]

Output: Generate intermediate object file but does not attempt to link.

PGI - Compiling and Linking C/C++ Programs | ARSC


Input: [Option] -g [Description]

Output: Adds information for debugging to the object file and/or executable.

PGI - Compiling and Linking C/C++ Programs | ARSC


Input: [Option] -I [Description]

Output: Tells the preprocessor to search in directory for include or module files.

PGI - Compiling and Linking C/C++ Programs | ARSC


Input: [Option] -L [Description]

Output: Tells the linker to search in directory for libraries.

PGI - Compiling and Linking C/C++ Programs | ARSC


Input: [Option] -O3 [Description]

Output: Higher level of optimization than -O2 (the default optimization level).

PGI - Compiling and Linking C/C++ Programs | ARSC


Input: [Option] -fast [Description]

Output: Higher level optimization (default is -O2). This flag should be used in both compilation andlinking steps.

PGI - Compiling and Linking C/C++ Programs | ARSC


Input: [Option] -Mipa [Description]

Output: Tells the compiler to perform interprocedural analysis. This option can be very timeconsuming to perform. This flag should be used in both compilation and linking steps.

PGI - Compiling and Linking C/C++ Programs | ARSC


Input: [Option] -Mconcur [Description]

Output: Enables autoparallelization. Additional options can be used with -Mconcur to provide morefine-grained control of autoparallelization, see man pgcc or man pgCC for details.

PGI - Compiling and Linking C/C++ Programs | ARSC


Input: [Option] -Minfo [Description]

Output: Instructs the compiler to report optimizations that are made.

PGI - Compiling and Linking C/C++ Programs | ARSC


Input: [Option] -Mneginfo [Description]

Output: Instructs the compiler to report optimizations that are not made.

PGI - Compiling and Linking C/C++ Programs | ARSC


Input: [Option] -mp [Description]

Output: Enables parallelization via OpenMP directives.

PGI - Compiling and Linking C/C++ Programs | ARSC


Input: [Rule] required [Description] returns false if the form element is empty. [Parameter]

Output: no


Input: [Rule] matches [Description] returns false if the form element value does not match the one in the parameter. [Example] matches[other_element] [Parameter]

Output: yes


Input: [Rule] valid_email [Description] returns false if the form element value is not a valid email address. [Parameter]

Output: no


Input: [Rule] valid_emails [Description] returns false if any value provided in a comma separated list is not a valid email. [Parameter]

Output: no


Input: [Rule] min_length [Description] returns false if the form element value is shorter than the parameter. [Example] min_length[6] [Parameter]

Output: yes


Input: [Rule] max_length [Description] returns false if the form element value is longer than the parameter. [Example] max_length[8] [Parameter]

Output: yes


Input: [Rule] exact_length [Description] returns false if the form element value length is not exactly the parameter. [Example] exact_length[4] [Parameter]

Output: yes


Input: [Rule] greater_than [Description] returns false if the form element value is less than the parameter after using parseFloat. [Example] greater_than[10] [Parameter]

Output: yes


Input: [Rule] less_than [Description] returns false if the form element value is greater than the parameter after using parseFloat. [Example] less_than[2] [Parameter]

Output: yes


Input: [Rule] alpha [Description] returns false if the form element contains anything other than alphabetical characters. [Parameter]

Output: no


Input: [Rule] alpha_numeric [Description] returns false if the form element contains anything other than alpha-numeric characters. [Parameter]

Output: no


Input: [Rule] alpha_dash [Description] returns false if the form element contains anything other than alphanumeric characters, underscores, or dashes. [Parameter]

Output: no


Input: [Rule] numeric [Description] returns false if the form element contains anything other than numeric characters. [Parameter]

Output: no


Input: [Rule] integer [Description] returns false if the form element contains anything other than an integer. [Parameter]

Output: no


Input: [Rule] decimal [Description] returns false if the form element contains anything other than a decimal. [Parameter]

Output: no


Input: [Rule] is_natural [Description] returns false if the form element contains anything other than a natural number: 0, 1, 2, 3, etc. [Parameter]

Output: no


Input: [Rule] is_natural_no_zero [Description] returns false if the form element contains anything other than a natural number, but not zero: 1, 2, 3, etc. [Parameter]

Output: no


Input: [Rule] valid_ip [Description] returns false if the supplied IP is not valid. [Parameter]

Output: no


Input: [Rule] valid_base64 [Description] returns false if the supplied string contains anything other than valid Base64 characters. [Parameter]

Output: no


Input: [Rule] valid_credit_card [Description] returns false if the supplied string is not a valid credit card [Parameter]

Output: no


Input: [Rule] valid_url [Description] returns false if the supplied string is not a valid url [Parameter]

Output: no


Input: [Rule] is_file_type [Description] returns false if the supplied file is not part of the comma separated list in the paramter [Example] is_file_type[gif,png,jpg] [Parameter]

Output: yes


Input: [NAME] MYSPACE MYSPACEMAIL [Size (in MB)] Unlimited [SMTP] NO [POP or IMAP]

Output: NO


Input: [NAME] YAHOO [Size (in MB)] Unlimited [SMTP] NO [Comment(s)] Does not like file storage ;) [POP or IMAP]

Output: NO


Input: [NAME] AIM (by AOL) [Size (in MB)] Unlimited [SMTP] YES but NOSPAM!!! [Comment(s)] Very high QoS / does not like file storage ;) [POP or IMAP]

Output: YES


Input: [NAME] MAIL2WORLD [Size (in MB)] Unlimited [SMTP] NO [Comment(s)] Max 50MB per day [POP or IMAP]

Output: NO


Input: [NAME] ZOHO MAIL [Size (in MB)] Unlimited [SMTP] YES but NOSPAM!!! [Comment(s)] Only for personnal and clever use [POP or IMAP]

Output: YES


Input: [NAME] REDIFFMAIL (rediff) [Size (in MB)] Unlimited [SMTP] NO [Comment(s)] Accept high attachments ;) [POP or IMAP]

Output: NO


Input: [NAME] GMAIL [Size (in MB)] 15000 or more (see tooltip) [SMTP] YES but NOSPAM !!! [Comment(s)] Can forgot mails [POP or IMAP]

Output: YES


Input: [NAME] GMX from GMX.NET [Size (in MB)] Unlimited [SMTP] YES but NOSPAM !!! [Comment(s)] A part of 1AND1 enterprise Exist in FR and ES (5 Go too) and in in Deutsch with 1 GB only. [POP or IMAP]

Output: YES


Input: [NAME] HOTMAIL / OUTLOOK.COM [Size (in MB)] 5000 to 500000 [SMTP] YES but NOSPAM !!! [Comment(s)] High storage is given if u regurarly manange your mails [POP or IMAP]

Output: YES


Input: [NAME] LAVABIT (closed) [Size (in MB)] 1000 [SMTP] YES but NOSPAM !!! [Comment(s)] Closed in August 2013 due to PRISM/Snowden crisis) [POP or IMAP]

Output: YES


Input: [NAME] UNLIMITEDMAIL.ORG [Size (in MB)] 30 [SMTP] YES but NOSPAM !!! [POP or IMAP]

Output: YES


Input: [NAME] VFEMAIL.NET [Size (in MB)] 50 [SMTP] YES but NOSPAM !!! [Comment(s)] Can be slow to send mail [POP or IMAP]

Output: YES


Input: [NAME] LAPOSTE.NET [Size (in MB)] 1000 [SMTP] YES but NOSPAM !!! [Comment(s)] ONLY FOR FRENCH USERS ! Send a snail mail to confirm identity [POP or IMAP]

Output: YES


Input: [NAME] NAME [Size (in MB)] Size (in MB) [SMTP] SMTP [Comment(s)] Comment(s) [POP or IMAP]

Output: POP or IMAP


Input: [Type] File [Since] - [Description] The directory containing the Java classes. [Name]

Output: classesDirectory

Maven Lutece plugin - lutece:site-assembly


Input: [Type] File [Since] - [Description] The directory containing the default configuration files. [Name]

Output: defaultConfDirectory

Maven Lutece plugin - lutece:site-assembly


Input: [Type] File [Since] - [Description] A temporary directory used to hold the exploded version of the webapp. [Name]

Output: explodedDirectory

Maven Lutece plugin - lutece:site-assembly


Input: [Type] String [Since] - [Description] The name of the generated WAR file. [Name]

Output: finalName

Maven Lutece plugin - lutece:site-assembly


Input: [Type] File [Since] - [Description] The project's output directory [Name]

Output: outputDirectory

Maven Lutece plugin - lutece:site-assembly


Input: [Type] String [Since] - [Description] The output date format. Default value is: yyyyMMdd.HHmmss. [Name]

Output: utcTimestampPattern

Maven Lutece plugin - lutece:site-assembly


Input: [Type] File [Since] - [Description] The source directory for webapp components. [Name]

Output: webappSourceDirectory

Maven Lutece plugin - lutece:site-assembly


Input: [Type] broadcast_not_found [Description]

Output: The specified broadcast id is not valid.


Input: [Type] broadcast_removed [Description]

Output: The owner of this broadcast chose to remove the specified broadcast.


Input: [Type] broadcast_not_archived [Description]

Output: The owner of the specified broadcast chose to disable archiving, hence it only existed as a live stream.


Input: [Type] broadcast_not_available [Description]

Output: The specified broadcast is currently unavailable for some unspecified reason.


Input: [Type] broadcast_no_access [Description]

Output: You don't have permission to access to the specified broadcast. This error is returned if you try to access a private broadcast.


Input: [Type] user_not_available [Description]

Output: The user account that the selected broadcast was produced with is not available anymore. This error is returned when the user has closed the account as well as when account is temporarily or permanently blocked by the administrators.


Input: [User] Application [Boss] Application used

Output: He posts a letter, and informs his PA about it.

Tips to Remember the functions of OSI Layer ~ COMPUTER KORNER


Input: [User] Presentation [Boss] Personal assistant (PA)

Output: PA says, “Ok Sir! I will forward this parcel, if needed I will do the job of translation and encryption and passes the message to Legal Adviser!"

Tips to Remember the functions of OSI Layer ~ COMPUTER KORNER


Input: [User] Session [Boss] Legal Advisor

Output: On getting the parcel, he checks it, and decides whether it is wise to send it and checks if their office is in good terms with the different office; and then he passes the message Mail Manager

Tips to Remember the functions of OSI Layer ~ COMPUTER KORNER


Input: [User] Transport [Boss] Mail Manager

Output: He gets the parcel, and then he thinks that “Oh My God! Such a big parcel, let me break the parcel and make segments(chunks) of it ”, he further numbers the chunks so that it can be combined to make the parcel by the receiving party. Next he contacts the Mail manager of the receiving office, and says, “hey I will be sending your office some segments, please let me know when you receive the segments” and then passes the segments to Mail Room.

Tips to Remember the functions of OSI Layer ~ COMPUTER KORNER


Input: [User] Network [Boss] Mail Room

Output: When the Mail Room receives the segments, people working there, adds From and To address to each segments, and now the segments are known as packets. And now these packets are handed to Mail Service Department.(Mail Room is more concerned about the location address of the receiving party, but not the exact address, which is the house number)

Tips to Remember the functions of OSI Layer ~ COMPUTER KORNER


Input: [User] Data Link [Boss] Mail Service

Output: When the Mail Service Department, receives the packets it adds the physical address of the office, which is the house number, and then makes a check of the packets for any mismatch or loss by the above layers. Then places the result on the packets, and now what we have is a Frame. Again the Frame has to have some kind of medium so that it can reach the receiving party. It decides the medium and then hands over to the decided medium.

Tips to Remember the functions of OSI Layer ~ COMPUTER KORNER


Input: [User] Physical [Boss] Medium

Output: The Frames are converted to BITS, before it was handed to the medium. Now medium, which can be a Van, Train, Cargo, Airplane, etc..takes it, and starts for the receiving party.

Tips to Remember the functions of OSI Layer ~ COMPUTER KORNER


Input: [0] ctrl a [description] create new window [flags]


Input: [0] ctrl a [description] set window name [flags]


Input: [0] ctrl a [description] show all window [flags]


Input: [0] 3 [description] ctrl a [flags]

Output: switch to window 3


Input: [0] " [description] ctrl a [flags]

Output: choose window


Input: [0] ctrl a [flags]

Output: switch between window


Input: [description] d [flags]

Output: ctrl a


Input: [0] detach window [description] ? [flags]

Output: ctrl a


Input: [0] help [description] [ [flags]

Output: ctrl a


Input: [Reason Code] 100 [Reply Flag (SCMP)] SOK [Description]

Output: Successful transaction

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 101 [Reply Flag (SCMP)] DMISSINGFIELD [Possible Action] See the reply fields missingField_0...N for which fields are invalid. Resend the request with the correct information. [Description]

Output: Declined - The request is missing one or more fields

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 102 [Reply Flag (SCMP)] DINVALIDDATA [Possible Action] See the reply fields invalidField_0...N for which fields are invalid. Resend the request with the correct information. [Description]

Output: Declined - One or more fields in the request contains invalid data

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 104 [Reply Flag (SCMP)] DDUPLICATE [Possible Action] Resend the request with a unique merchantReferenceCode value. [Description]

Output: Declined - The merchantReferenceCode sent with this authorization request matches the merchantReferenceCode of another authorization request that you sent in the last 15 minutes.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 110 [Reply Flag (SCMP)] SPARTIALAPPROVAL [Possible Action] See "Partial Authorizations," page 64. [Description]

Output: Partial amount was approved

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 150 [Reply Flag (SCMP)] ESYSTEM [Possible Action] See the documentation for your CyberSource client (SDK) for information about how to handle retries in the case of system errors. [Description]

Output: Error - General system failure.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 151 [Reply Flag (SCMP)] ETIMEOUT [Possible Action] To avoid duplicating the transaction, do not resend the request until you have reviewed the transaction status in the Business Center. See the documentation for your CyberSource client (SDK) for information about how to handle retries in the case of system errors. [Description]

Output: Error - The request was received but there was a server timeout. This error does not include timeouts between the client and the server.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 152 [Reply Flag (SCMP)] ETIMEOUT [Possible Action] To avoid duplicating the transaction, do not resend the request until you have reviewed the transaction status in the Enterprise Business Center. See the documentation for your CyberSource client (SDK) for information about how to handle retries in the case of system errors. [Description]

Output: Error: The request was received, but a service did not finish running in time.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 200 [Reply Flag (SCMP)] DAVSNO [Possible Action] You can capture the authorization, but consider reviewing the order for the possibility of fraud. [Description]

Output: Soft Decline - The authorization request was approved by the issuing bank but declined by CyberSource because it did not pass the Address Verification Service (AVS) check.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 201 [Reply Flag (SCMP)] DCALL [Possible Action] Call your processor to possibly receive a verbal authorization. For contact phone numbers, refer to your merchant bank information. [Description]

Output: Decline - The issuing bank has questions about the request. You do not receive an authorization code programmatically, but you might receive one verbally by calling the processor.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 202 [Reply Flag (SCMP)] DCARDEXPIRED [Possible Action] Request a different card or other form of payment. [Description]

Output: Decline - Expired card. You might also receive this if the expiration date you provided does not match the date the issuing bank has on file. Note: The ccCreditService does not check the expiration date; instead, it passes the request to the payment processor. If the payment processor allows issuance of credits to expired cards, CyberSource does not limit this functionality.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 203 [Reply Flag (SCMP)] DCARDREFUSED [Possible Action] Request a different card or other form of payment. [Description]

Output: Decline - General decline of the card. No other information provided by the issuing bank.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 204 [Reply Flag (SCMP)] DCARDREFUSED [Possible Action] Request a different card or other form of payment. [Description]

Output: Decline - Insufficient funds in the account.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 205 [Reply Flag (SCMP)] DCARDREFUSED [Possible Action] Refer the transaction to your customer support center for manual review. [Description]

Output: Decline - Stolen or lost card.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 207 [Reply Flag (SCMP)] DCARDREFUSED [Possible Action] Wait a few minutes and resend the request. [Description]

Output: Decline - Issuing bank unavailable.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 208 [Reply Flag (SCMP)] DCARDREFUSED [Possible Action] Request a different card or other form of payment. [Description]

Output: Decline - Inactive card or card not authorized for card-not-present transactions.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 209 [Reply Flag (SCMP)] DCARDREFUSED [Possible Action] Request a different card or other form of payment. [Description]

Output: Decline - American Express Card Identification Digits (CID) did not match.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 210 [Reply Flag (SCMP)] DCARDREFUSED [Possible Action] Request a different card or other form of payment. [Description]

Output: Decline - The card has reached the credit limit.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 211 [Reply Flag (SCMP)] DCARDREFUSED [Possible Action] Request a different card or other form of payment. [Description]

Output: Decline - Invalid Card Verification Number (CVN).

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 220 [Reply Flag (SCMP)] DCHECKREFUSED [Possible Action] Request a different form of payment. [Description]

Output: Decline - Generic Decline.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 221 [Reply Flag (SCMP)] DCHECKREFUSED [Possible Action] Review the order and contact the payment processor. [Description]

Output: Decline - The customer matched an entry on the processor's negative file.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 222 [Reply Flag (SCMP)] DCHECKREFUSED [Possible Action] Review the order or request a different form of payment. [Description]

Output: Decline - customer's account is frozen

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 230 [Reply Flag (SCMP)] DCV [Possible Action] You can capture the authorization, but consider reviewing the order for the possibility of fraud. [Description]

Output: Soft Decline - The authorization request was approved by the issuing bank but declined by CyberSource because it did not pass the card verification number (CVN) check.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 231 [Reply Flag (SCMP)] DINVALIDCARD [Possible Action] Request a different card or other form of payment. [Description]

Output: Decline - Invalid account number

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 232 [Reply Flag (SCMP)] DINVALIDDATA [Possible Action] Contact your merchant bank to confirm that your account is set up to receive the card in question. [Description]

Output: Decline - The card type is not accepted by the payment processor.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 233 [Reply Flag (SCMP)] DINVALIDDATA [Possible Action] Request a different card or other form of payment. [Description]

Output: Decline - General decline by the processor.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 234 [Reply Flag (SCMP)] DINVALIDDATA [Possible Action] Do not resend the request. Contact Customer Support to correct the configuration problem. [Description]

Output: Decline - There is a problem with your CyberSource merchant configuration.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 235 [Reply Flag (SCMP)] DINVALIDDATA [Possible Action] Issue a new authorization and capture request for the new amount. [Description]

Output: Decline - The requested amount exceeds the originally authorized amount. Occurs, for example, if you try to capture an amount larger than the original authorization amount.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 236 [Reply Flag (SCMP)] DINVALIDDATA [Possible Action] Wait a few minutes and resend the request. [Description]

Output: Decline - Processor failure.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 237 [Reply Flag (SCMP)] DINVALIDDATA [Possible Action] No action required. [Description]

Output: Decline - The authorization has already been reversed.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 238 [Reply Flag (SCMP)] DINVALIDDATA [Possible Action] No action required. [Description]

Output: Decline - The transaction has already been settled.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 239 [Reply Flag (SCMP)] DINVALIDDATA [Possible Action] Correct the amount and resend the request. [Description]

Output: Decline - The requested transaction amount must match the previous transaction amount.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 240 [Reply Flag (SCMP)] DINVALIDDATA [Possible Action] Confirm that the card type correlates with the credit card number specified in the request, then resend the request. [Description]

Output: Decline - The card type sent is invalid or does not correlate with the credit card number.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 241 [Reply Flag (SCMP)] DINVALIDDATA [Possible Action] No action required. [Description]

Output: Decline - The referenced request id is invalid for all follow-on transactions.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 242 [Reply Flag (SCMP)] DNOAUTH [Possible Action] Request a new authorization, and if successful, proceed with the capture. [Description]

Output: Decline - The request ID is invalid. You requested a capture, but there is no corresponding, unused authorization record. Occurs if there was not a previously successful authorization request or if the previously successful authorization has already been used in another capture request.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 243 [Reply Flag (SCMP)] DINVALIDDATA [Possible Action] No action required. [Description]

Output: Decline - The transaction has already been settled or reversed. This reason code is specifically for Japan.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 246 [Reply Flag (SCMP)] DNOTVOIDABLE [Possible Action] No action required. [Description]

Output: Decline - The capture or credit is not voidable because the capture or credit information has already been submitted to your processor. Or, you requested a void for a type of transaction that cannot be voided.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 247 [Reply Flag (SCMP)] DINVALIDDATA [Possible Action] No action required. [Description]

Output: Decline - You requested a credit for a capture that was previously voided.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 248 [Reply Flag (SCMP)] DBOLETODECLINED [Description]

Output: Decline - The boleto request was declined by your processor.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 250 [Reply Flag (SCMP)] ETIMEOUT [Possible Action] To avoid duplicating the transaction, do not resend the request until you have reviewed the transaction status in the Enterprise Business Center. [Description]

Output: Error - The request was received, but there was a timeout at the payment processor.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 251 [Reply Flag (SCMP)] DCARDREFUSED [Possible Action] Request a different card or other form of payment. [Description]

Output: Decline - The Pinless Debit card's use frequency or maximum amount per use has been exceeded.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 254 [Reply Flag (SCMP)] DINVALIDDATA [Possible Action] Submit a follow-on credit by including a request ID in the credit request. A follow-on credit must be requested within 60 days of the authorization. To process stand-alone credits, contact your CyberSource account representative to find out if your processor supports stand-alone credits. [Description]

Output: Decline - Account is prohibited from processing stand-alone refunds.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 400 [Reply Flag (SCMP)] DSCORE [Possible Action] You can capture the authorization, but consider reviewing the order for the possibility of fraud. [Description]

Output: Soft Decline - Fraud score exceeds threshold.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 450 [Reply Flag (SCMP)] DINVALIDADDRESS [Possible Action] Ask the customer to verify the address information and resend the request. [Description]

Output: Apartment number missing or not found.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 451 [Reply Flag (SCMP)] DINVALIDADDRESS [Possible Action] Ask the customer to verify the address information and resend the request. [Description]

Output: Insufficient address information.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 452 [Reply Flag (SCMP)] DINVALIDADDRESS [Possible Action] Ask the customer to verify the address information and resend the request. [Description]

Output: House/Box number not found on street.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 453 [Reply Flag (SCMP)] DINVALIDADDRESS [Possible Action] Ask the customer to verify the address information and resend the request. [Description]

Output: Multiple address matches were found.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 454 [Reply Flag (SCMP)] DINVALIDADDRESS [Possible Action] Ask the customer to verify the address information and resend the request. [Description]

Output: P.O. Box identifier not found or out of range.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 455 [Reply Flag (SCMP)] DINVALIDADDRESS [Possible Action] Ask the customer to verify the address information and resend the request. [Description]

Output: Route service identifier not found or out of range.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 456 [Reply Flag (SCMP)] DINVALIDADDRESS [Possible Action] Ask the customer to verify the address information and resend the request. [Description]

Output: Street name not found in Postal code.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 457 [Reply Flag (SCMP)] DINVALIDADDRESS [Possible Action] Ask the customer to verify the address information and resend the request. [Description]

Output: Postal code not found in database.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 458 [Reply Flag (SCMP)] addressIDADDRESS [Possible Action] Ask the customer to verify the address information and resend the request. [Description]

Output: Unable to verify or correct address.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 459 [Reply Flag (SCMP)] DINVALIDADDRESS [Possible Action] Ask the customer to verify the address information and resend the request. [Description]

Output: Multiple addres matches were found (international)

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 460 [Reply Flag (SCMP)] DINVALIDADDRESS [Possible Action] Ask the customer to verify the address information and resend the request. [Description]

Output: Address match not found (no reason given)

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 461 [Reply Flag (SCMP)] DINVALIDADDRESS [Possible Action] Verify the character set that you are using to process transactions. [Description]

Output: Unsupported character set

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 475 [Reply Flag (SCMP)] DAUTHENTICATE [Description]

Output: The cardholder is enrolled in Payer Authentication. Please authenticate the cardholder before continuing with the transaction.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 476 [Reply Flag (SCMP)] DAUTHENTICATIONFAILED [Description]

Output: Encountered a Payer Authentication problem. Payer could not be authenticated.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 480 [Reply Flag (SCMP)] DREVIEW [Description]

Output: The order is marked for review by Decision Manager

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 481 [Reply Flag (SCMP)] DREJECT [Description]

Output: The order has been rejected by Decision Manager

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 520 [Reply Flag (SCMP)] DSETTINGS [Possible Action] Do not capture the authorization without further review. Review the ccAuthReply_avsCode, ccAuthReply_cvCode, and ccAuthReply_authFactorCode fields to determine why CyberSource rejected the request. [Description]

Output: Soft Decline - The authorization request was approved by the issuing bank but declined by CyberSource based on your Smart Authorization settings.

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 700 [Reply Flag (SCMP)] DRESTRICTED [Possible Action] Reject the customer's order. [Description]

Output: The customer matched the Denied Parties List

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 701 [Reply Flag (SCMP)] DRESTRICTED [Possible Action] Reject the customer's order. [Description]

Output: Export bill_country/ship_country match

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 702 [Reply Flag (SCMP)] DRESTRICTED [Possible Action] Reject the customer's order. [Description]

Output: Export email_country match

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Reason Code] 703 [Reply Flag (SCMP)] DRESTRICTED [Possible Action] Reject the customer's order. [Description]

Output: Export hostname_country/ip_country match

CyberSource Support Center - What do the various Reason Codes indicate?


Input: [Source Attribute] label [Meaning]

Output: A label to place on the message arc, or label to use for an entity. This is reproduced literally above the message arc or in place of the entity name. When used as a message arc label this may also contain parameters or required text. If a \n is encountered, it will be interpreted as a newline, placing text below the arc as well as above it in the normal position, or expanding entity tiles onto more lines.

Mscgen: A Message Sequence Chart Renderer


Input: [Source Attribute] URL [Meaning]

Output: When generating the image, colour the label in blue. If generating an image map, create an entry for the label to the specified URL. If the message sequence chart is to be embedded in Doxygen documentation, the URL maybe specified as \ref xxx where xxx is the name of some documented element; in this case a link to the element will automatically be made.

Mscgen: A Message Sequence Chart Renderer


Input: [Source Attribute] ID [Meaning]

Output: Adds a superscript identifier to the label. Typically this maybe a number such that specific elements can be identified and referred to in surrounding descriptive text.

Mscgen: A Message Sequence Chart Renderer


Input: [Source Attribute] IDURL [Meaning]

Output: Similar to the URL attribute, but links from the ID text rather than the message label. This has the same semantics as the URL attribute, but is only of use if an arc also has an ID.

Mscgen: A Message Sequence Chart Renderer


Input: [Source Attribute] arcskip [Meaning]

Output: This offsets the vertical position at which an arc reaches its destination entity.

Mscgen: A Message Sequence Chart Renderer


Input: [Source Attribute] linecolour, linecolor [Meaning]

Output: For arcs or entities, set the line to the specified colour.

Mscgen: A Message Sequence Chart Renderer


Input: [Source Attribute] textcolour, textcolor [Meaning]

Output: For arcs or entities, set label text to the specified colour.

Mscgen: A Message Sequence Chart Renderer


Input: [Source Attribute] textbgcolour, textbgcolor [Meaning]

Output: For arcs or entities, set a colour for the text background block. Sets the fill colour for 'box', 'abox', 'rbox' and 'note' shapes.

Mscgen: A Message Sequence Chart Renderer


Input: [Source Attribute] arclinecolour, arclinecolor [Meaning]

Output: Only meaningful on a entity, this sets the default line colour for all arcs that originating from that entity. This can be overridden by linecolour attributes on specific arcs as desired.

Mscgen: A Message Sequence Chart Renderer


Input: [Source Attribute] arctextcolour, arctextcolor [Meaning]

Output: Only meaningful on a entity, this sets the default text colour for all arcs that originating from that entity. This can be overridden by textcolour attributes on specific arcs as desired.

Mscgen: A Message Sequence Chart Renderer


Input: [Source Attribute] arctextbgcolour, arctextbgcolor [Meaning]

Output: Only meaningful on a entity, this sets the default colour for the text background for all arc oriniationg from that entity. This can be overridden by textbgcolour attributes on specific arcs as desired.

Mscgen: A Message Sequence Chart Renderer


Input: [var] object_preparationtable [Objects Display Name]

Output: Preparation Table

Modding guide - Prison Architect Wiki - Prison Architect community wiki


Input: [var] object_vegetableseeds [Objects Display Name]

Output: Vegetable Seeds

Modding guide - Prison Architect Wiki - Prison Architect community wiki


Input: [var] object_rawpotato [Objects Display Name]

Output: Potato

Modding guide - Prison Architect Wiki - Prison Architect community wiki


Input: [var] object_rawcabbage [Objects Display Name]

Output: Cabbage

Modding guide - Prison Architect Wiki - Prison Architect community wiki


Input: [var] object_compost [Objects Display Name]

Output: Compost

Modding guide - Prison Architect Wiki - Prison Architect community wiki


Input: [var] object_shed [Objects Display Name]

Output: Shed

Modding guide - Prison Architect Wiki - Prison Architect community wiki


Input: [var] room_vegetablepatch [Objects Display Name]

Output: Vegetable Patch

Modding guide - Prison Architect Wiki - Prison Architect community wiki


Input: [var] research_farming [Objects Display Name]

Output: Farming

Modding guide - Prison Architect Wiki - Prison Architect community wiki


Input: [var] researchtooltip_farming [Objects Display Name]

Output: Allows you to place a vegetable patch in your prison and train your prisoners to grow vegetables that can contribute to your kitchens ingredients pool.

Modding guide - Prison Architect Wiki - Prison Architect community wiki


Input: [var] reformprogram_horticulture [Objects Display Name]

Output: Horticulture

Modding guide - Prison Architect Wiki - Prison Architect community wiki


Input: [var] material_farmland [Objects Display Name]

Output: Compost

Modding guide - Prison Architect Wiki - Prison Architect community wiki


Input: [var] equipment_trowel [Objects Display Name]

Output: Trowel

Modding guide - Prison Architect Wiki - Prison Architect community wiki


Input: [var] tooltip_seeds_compost [Objects Display Name]

Output: Seeds need to be planted in Compost before they will grow and produce vegetables.

Modding guide - Prison Architect Wiki - Prison Architect community wiki


Input: [var] tooltip_seeds_needtending [Objects Display Name]

Output: This plant needs to be tended before it will grow more vegetables.

Modding guide - Prison Architect Wiki - Prison Architect community wiki


Input: [var] job_custom_tendvegetables [Objects Display Name]

Output: Tend Vegetables

Modding guide - Prison Architect Wiki - Prison Architect community wiki


Input: [Name] None [Defined Value] WSEV_NONE [Type]

Output: Not occurs


Input: [Name] INITIALIZE [Defined Value] WSEV_INITIALIZE [Type]

Output: When the instance is initilized.


Input: [Name] DELETE [Defined Value] WSEV_DELETE [Type]

Output: When the instance is released.


Input: [Name] ACTIVATE [Defined Value] WSEV_ACTIVATE [Type]

Output: When the instance is activated.


Input: [Name] FOCUS-CH [Defined Value] WSEV_FOCUS_CH [Type]

Output: When the instance gets or loses the keyboard focus.


Input: [Name] VISIBLE-CH [Defined Value] WSEV_VISIBLE_CH [Type]

Output: When the WSNvis property is changed.


Input: [Name] PARENT-VISIBLE-CH [Defined Value] WSEV_PARENT_VISIBLE_CH [Type]

Output: When the visible property of the parent instance is changed.


Input: [Name] RESIZE [Defined Value] WSEV_RESIZE [Type]

Output: When the instance is resized.


Input: [Name] MOUSE-IN [Defined Value] WSEV_MOUSE_IN [Type]

Output: When the mouse pointer comes into the area


Input: [Name] MOUSE-OUT [Defined Value] WSEV_MOUSE_OUT [Type]

Output: When the mouse pointer goes out of the area.


Input: [Name] MOUSE-PRESS [Defined Value] WSEV_MOUSE_PRESS [Type]

Output: When the mouse pointer is pressed.


Input: [Name] MOUSE-RELEASE [Defined Value] WSEV_MOUSE_RELEASE [Type]

Output: When the mouse pointer is released.


Input: [Name] MOUSE-MOVE [Defined Value] WSEV_MOUSE_MOVE [Type]

Output: When the mouse pointer moves in the area.


Input: [Unit] Meter [Symbol] m [Dimensions] L [Quantity]

Output: Length

Difference Between Fundamental and Derived Quantities | Fundamental vs Derived Quantities


Input: [Unit] Kilogram [Symbol] kg [Dimensions] M [Quantity]

Output: Mass

Difference Between Fundamental and Derived Quantities | Fundamental vs Derived Quantities


Input: [Unit] Seconds [Symbol] s [Dimensions] T [Quantity]

Output: Time

Difference Between Fundamental and Derived Quantities | Fundamental vs Derived Quantities


Input: [Unit] Ampère [Symbol] A [Quantity]

Output: Electric Current

Difference Between Fundamental and Derived Quantities | Fundamental vs Derived Quantities


Input: [Unit] Kelvin [Symbol] K [Quantity]

Output: Thermodynamic Temp.

Difference Between Fundamental and Derived Quantities | Fundamental vs Derived Quantities


Input: [Unit] Mole [Symbol] mol [Quantity]

Output: Amount of Substance

Difference Between Fundamental and Derived Quantities | Fundamental vs Derived Quantities


Input: [Unit] Candela [Symbol] cd [Quantity]

Output: Luminous intensity

Difference Between Fundamental and Derived Quantities | Fundamental vs Derived Quantities


Input: [Filename] ca.crt [Purpose] Root CA certificate [Secret] NO [Needed By]

Output: server + all clients


Input: [Filename] ca.key [Purpose] Root CA key [Secret] YES [Needed By]

Output: key signing machine only


Input: [Filename] dh{n}.pem [Purpose] Diffie Hellman parameters [Secret] NO [Needed By]

Output: server only


Input: [Filename] server.crt [Purpose] Server Certificate [Secret] NO [Needed By]

Output: server only


Input: [Filename] server.key [Purpose] Server Key [Secret] YES [Needed By]

Output: server only


Input: [Filename] client1.crt [Purpose] Client1 Certificate [Secret] NO [Needed By]

Output: client1 only


Input: [Filename] client1.key [Purpose] Client1 Key [Secret] YES [Needed By]

Output: client1 only


Input: [Filename] client2.crt [Purpose] Client2 Certificate [Secret] NO [Needed By]

Output: client2 only


Input: [Filename] client2.key [Purpose] Client2 Key [Secret] YES [Needed By]

Output: client2 only


Input: [Filename] client3.crt [Purpose] Client3 Certificate [Secret] NO [Needed By]

Output: client3 only


Input: [Filename] client3.key [Purpose] Client3 Key [Secret] YES [Needed By]

Output: client3 only


Input: [Classic Key] Home [Equivalent CUA key] F12 or Numeric Pad Plus [Function]

Output: Cursor to command line (also executes pending prefix commands)


Input: [Classic Key] Ctrl+Home [Equivalent CUA key] Ctrl+Page Up [Function]

Output: Cursor to upper left of window


Input: [Classic Key] Ctrl+End [Equivalent CUA key] Ctrl+Delete [Function]

Output: Delete through end of line


Input: [Classic Key] Ctrl+Page Up [Equivalent CUA key] Ctrl+Home [Function]

Output: Cursor to beginning of file


Input: [Classic Key] Ctrl+Page Down [Equivalent CUA key] Ctrl+End [Function]

Output: Cursor to end of file


Input: [Classic Key] Numeric Pad Plus or Ctrl+Enter [Equivalent CUA key] Ctrl+Numeric Pad Enter or Shift+Ctrl+Enter [Function]

Output: Toggle between file and prefix areas


Input: [Classic Key] Enter or Numeric Pad Enter [Equivalent CUA key] Ctrl+Enter [Function]

Output: In file area: Move to beginning of next line


Input: [Classic Key] Tab (in Insert Mode) [Equivalent CUA key] F4 [Function]

Output: Move to next Tab column


Input: [Classic Key] Ctrl+A [Equivalent CUA key] Shift+Ctrl+A [Function]

Output: Adjust text to cursor position


Input: [Classic Key] Ctrl+C [Equivalent CUA key] Shift+Ctrl+C [Function]

Output: Center line


Input: [Classic Key] Ctrl+F [Equivalent CUA key] Shift+Ctrl+F [Function]

Output: Format paragraph


Input: [Classic Key] Ctrl+P [Equivalent CUA key] Shift+Ctrl+P [Function]

Output: Begin a new paragraph


Input: [Classic Key] Ctrl+X [Equivalent CUA key] Shift+Ctrl+X [Function]

Output: Display parent directory in DIR.DIR


Input: [Classic Key] Alt+A [Equivalent CUA key] F2 [Function]

Output: Add a line


Input: [Classic Key] Alt+F [Equivalent CUA key] Ctrl+I [Function]

Output: Fill box block


Input: [Classic Key] Alt+H [Equivalent CUA key] F1 [Function]

Output: Access Help system


Input: [Classic Key] Alt+O [Equivalent CUA key] Shift+Ctrl+O [Function]

Output: Overlay box


Input: [Classic Key] Alt+W [Equivalent CUA key] Shift+Ctrl+W [Function]

Output: Delete word


Input: [Classic Key] F10 [Equivalent CUA key] Ctrl+Tab or Ctrl+F6 [Function]

Output: Cycle to next document window


Input: [Classic Key] F12 [Equivalent CUA key] Shift+F12 [Function]

Output: Toggle between command line and file area


Input: [Code] 100 [Meaning] Continue [Description]

Output: Confirms the client about the arrival of the first part of the request and informs to continue with the rest of the request or ignore if the request has been fulfilled


Input: [Code] 101 [Meaning] Switching Protocols [Description]

Output: Informs the client about the server switching the protocols to that specified in the Upgrade message header field during the current connection.


Input: [Code] 200 [Meaning] OK [Description]

Output: Standard response for successful requests


Input: [Code] 201 [Meaning] Created [Description]

Output: Request fulfilled and new resource created


Input: [Code] 202 [Meaning] Accepted [Description]

Output: Request accepted, but not yet processed


Input: [Code] 203 [Meaning] Non-Authoritative Information [Description]

Output: Returned meta information was not the definitive set from the origin server.


Input: [Code] 204 [Meaning] No Content [Description]

Output: Request succeeded without requiring the return of an entity-body


Input: [Code] 205 [Meaning] Reset Content [Description]

Output: Request succeeded but require resetting of the document view that caused the request


Input: [Code] 206 [Meaning] Partial Content [Description]

Output: Partial GET request was successful


Input: [Code] 300 [Meaning] Multiple Choices [Description]

Output: Requested resource has multiple choices at different locations.


Input: [Code] 301 [Meaning] Moved Permanently [Description]

Output: Resource permanently moved to a different URL.


Input: [Code] 302 [Meaning] Found [Description]

Output: Requested resource was found under a different URL but the client should continue to use the original URL.


Input: [Code] 303 [Meaning] See Other [Description]

Output: Requested response is at a different URL and can be accessed only through a GET command.


Input: [Code] 304 [Meaning] Not Modified [Description]

Output: Resource not modified since the last request.


Input: [Code] 305 [Meaning] Use Proxy [Description]

Output: Requested resource should be accessed through the proxy specified in the location field.


Input: [Code] 306 [Meaning] No Longer Used [Description]

Output: Reserved for future use


Input: [Code] 307 [Meaning] Temporary Redirect [Description]

Output: Resource has been moved temporarily to a different URL.


Input: [Code] 400 [Meaning] Bad Request [Description]

Output: Syntax of the request not understood by the server.


Input: [Code] 401 [Meaning] Not Authorized [Description]

Output: Request requires user authentication


Input: [Code] 402 [Meaning] Payment Required [Description]

Output: Reserved for future use.


Input: [Code] 403 [Meaning] Forbidden [Description]

Output: Server refuses to fulfill the request.


Input: [Code] 404 [Meaning] Not Found [Description]

Output: Document or file requested by the client was not found.


Input: [Code] 405 [Meaning] Method Not Allowed [Description]

Output: Method specified in the Request-Line was not allowed for the specified resource.


Input: [Code] 406 [Meaning] Not Acceptable [Description]

Output: Resource requested generates response entities that has content characteristics not specified in the accept headers.


Input: [Code] 407 [Meaning] Proxy Authentication Required [Description]

Output: Request requires the authentication with the proxy.


Input: [Code] 408 [Meaning] Request Timeout [Description]

Output: Client fails to send a request in the time allowed by the server.


Input: [Code] 409 [Meaning] Conflict [Description]

Output: Request was unsuccessful due to a conflict in the state of the resource.


Input: [Code] 410 [Meaning] Gone [Description]

Output: Resource requested is no longer available with no forwarding address


Input: [Code] 411 [Meaning] Length Required [Description]

Output: Server doesn’t accept the request without a valid Content-Length header field.


Input: [Code] 412 [Meaning] Precondition Failed [Description]

Output: Precondition specified in the Request-Header field returns false.


Input: [Code] 413 [Meaning] Request Entity Too Large [Description]

Output: Request unsuccessful as the request entity is larger than that allowed by the server


Input: [Code] 414 [Meaning] Request URL Too Long [Description]

Output: Request unsuccessful as the URL specified is longer than the one, the server is willing to process.


Input: [Code] 415 [Meaning] Unsupported Media Type [Description]

Output: Request unsuccessful as the entity of the request is in a format not supported by the requested resource


Input: [Code] 416 [Meaning] Requested Range Not Satisfiable [Description]

Output: Request included a Range request-header field without any range-specifier value


Input: [Code] 417 [Meaning] Expectation Failed [Description]

Output: Expectation given in the Expect request-header was not fulfilled by the server.


Input: [Code] 422 [Meaning] Unprocessable Entity [Description]

Output: Request well-formed but unable to process because of semantic errors


Input: [Code] 423 [Meaning] Locked [Description]

Output: Resource accessed was locked


Input: [Code] 424 [Meaning] Failed Dependency [Description]

Output: Request failed because of the failure of a previous request


Input: [Code] 426 [Meaning] Upgrade Required [Description]

Output: Client should switch to Transport Layer Security


Input: [Code] 500 [Meaning] Internal Server Error [Description]

Output: Request unsuccessful because of an unexpected condition encountered by the server.


Input: [Code] 501 [Meaning] Not Implemented [Description]

Output: Request unsuccessful as the server could not support the functionality needed to fulfill the request.


Input: [Code] 502 [Meaning] Bad Gateway [Description]

Output: Server received an invalid response from the upstream server while trying to fulfill the request.


Input: [Code] 503 [Meaning] Service Unavailable [Description]

Output: Request unsuccessful to the server being down or overloaded.


Input: [Code] 504 [Meaning] Gateway Timeout [Description]

Output: Upstream server failed to send a request in the time allowed by the server.


Input: [Code] 505 [Meaning] HTTP Version Not Supported [Description]

Output: Server does not support the HTTP version specified in the request.


Input: [Column name] ItemID ... Notes [Record attribute (note 1)] change form standard attributes [Data type]

Output: refer to the ChangeView reference

ChangePairView & ChangePairMasterView reference


Input: [Column name] ItemId_Child ... Notes_Child [Record attribute (note 1)] affected item standard attributes [Data type]

Output: refer to the ItemView reference

ChangePairView & ChangePairMasterView reference


Input: [Column name] LineNumber [Record attribute (note 1)] affected item row number [Data type]

Output: integer

ChangePairView & ChangePairMasterView reference


Input: [Column name] ReleaseRevision [Record attribute (note 1)] if affected item was released: new iteration's revision identifier [Data type]

Output: string

ChangePairView & ChangePairMasterView reference


Input: [Column name] ReleaseLifecycle [Record attribute (note 1)] if affected item was released: new iteration's lifecycle [Data type]

Output: Lifecycle Name

ChangePairView & ChangePairMasterView reference


Input: [Column name] ReleaseNote [Record attribute (note 1)] if affected item was released: new iteration's Release description [Data type]

Output: string

ChangePairView & ChangePairMasterView reference


Input: [Column name] CancelRevision [Record attribute (note 1)] if affected item was canceled: old iteration's revision identifier [Data type]

Output: string

ChangePairView & ChangePairMasterView reference


Input: [Column name] CancelLifecycle [Record attribute (note 1)] if affected item was canceled: old iteration's lifecycle [Data type]

Output: Lifecycle Name

ChangePairView & ChangePairMasterView reference


Input: [Column name] CancelNote [Record attribute (note 1)] if affected item was canceled: old iteration's Release description [Data type]

Output: string

ChangePairView & ChangePairMasterView reference


Input: [0] Field [1] Type [2]

Output: Description


Input: [0] intCollDebugRate [1] Integer [2]

Output: Used by FmtCollLine to indicate how often debugging records should be writted for Collection data.


Input: [0] intCollFileSize [1] Const Integer = 500 [2]

Output: How many collection records to put into one file.


Input: [0] intLastPos [1] Integer [2]

Output: The last position in strOutput that has data.


Input: [0] intPass [1] Integer [2]

Output: Used in SrcLocnOthLocn.


Input: [0] intRcdCnt [1] Integer [2]

Output: Counts the Collection or Observation records comprising one Area List in butBldPlantList.


Input: [0] intTgtLth [1] Integer [2]

Output: The target length of the output string.


Input: [0] intTypesRcd [1] Integer [2]

Output: Counter for stepping through Types that were described from a Location.


Input: [0] intXrefRcd [1] Integer [2]

Output: Counter for stepping through tblXref records.


Input: [0] lngAreaCnt [1] Long Integer [2]

Output: Counts the Areas while the Area Lists are being prepared.


Input: [0] lngAreaIncr [1] Long Integer [2]

Output: The amount to increment the System Meter for each Area in the Area Lists.


Input: [0] lngAreaCollIncr [1] Long Integer [2]

Output: SysMeter value for each record while building Area Lists.


Input: [0] lngMeterBase [1] Long Integer [2]

Output: The base amount for the System Meter.


Input: [0] rsttblAltFT [1] Recordset [2]

Output: A recordset containing any records with the Alternate File Type attribute.


Input: [0] rsttblArtAttr [1] Recordset [2]

Output: A recordset containing a record from tblArticle


Input: [0] rsttblColl [1] Recordset [2]

Output: A recordset containing records from tblCollection. Used in subroutines but_GWB_Coll_List_Click and FmtCollLine.


Input: [0] rsttblHTML [1] Recordset [2]

Output: Recordset in tblHTML.


Input: [0] rsttblLocnAlt [1] Recordset [2]

Output: Used in SrcLocnOthLocn.


Input: [0] rsttblPgfAlt [1] Recordset [2]

Output: Used in SrcPgfOthPgf. when looking up information about the other article when preparing references to other articles.


Input: [0] rsttblXref [1] Recordset [2]

Output: A record set in tblXref.


Input: [0] rsttblTypes [1] Recordset [2]

Output: A record set in tblTypes.


Input: [0] strArtAssist [1] String [2]

Output: Provide assistance to authors of articles.


Input: [0] strCollIn [1] String [2]

Output: Used in GetCollInfo


Input: [0] strCurArtAuthor [1] String [2]

Output: Used in ExArticle


Input: [0] strCurArticle [1] String [2]

Output: Base URL of the current article.


Input: [0] strCurAltFileType [1] String [2]

Output: Current value of the alternate file type for the current web site.


Input: [0] strCurArtPage [1] String [2]

Output: The current Page of the current Article.


Input: [0] strCurArtRefTitle [1] String [2]

Output: The article title of the current article while preparing article references. Used in SrcPgfLocn.


Input: [0] strCurArtTitle [1] String [2]

Output: The title of the current article.


Input: [0] strCurDBName [1] String [2]

Output: The name of the current data base.


Input: [0] strCurFAQFT [1] String [2]

Output: The file type of the first page in the FAQ. Set in early in butGWB_Articles. If there is no FAQ, then the value is set to .html as a default.


Input: [0] strCurLetter [1] String [2]

Output: For Keeping track of the first letter of locations.


Input: [0] strcurYear [1] String [2]

Output: Used in ExLetters to keep track of the year.


Input: [0] strDBInput [1] String [2]

Output: An input string for the name of the current data base.


Input: [0] strInpArticle [1] String [2]

Output: used by ExArticles


Input: [0] strInpArtPage [1] String [2]

Output: Input value of page of current article


Input: [0] strinpYear [1] String [2]

Output: Used in ExLetters to extract the year in each letter.


Input: [0] strLitCitPage [1] String [2]

Output: When in butGWB_Articles, indicates the Article Page on which the Literature Cited Topic occurs.


Input: [0] strLocnAnchIn [1] String [2]

Output: Used as argument to SrcLocnTypes and SrcTypesLocn.


Input: [0] strLocnArtBase [1] String [2]

Output: Article base when looking for a location.


Input: [0] strLocnLetter [1] String [2]

Output: Parameter to SrcLocnLetter.


Input: [0] strLocnLocn [1] String [2]

Output: Parameter to SrcLocnOthLocn.


Input: [0] strLocnParaNbr [1] String [2]

Output: Paragraph number when looking for a location.


Input: [0] strLocnProlog [1] String [2]

Output: Used by SrcLocnOthLocn to hold the "See also:"


Input: [0] strLocnRefType [1] String [2]

Output: Indicates the form of the location reference that is being requested.


Input: [0] strMaxPgAltFT [1] String [2]

Output: The highest page number of the current Article that should use the Alternate Filetype. Set in GetArtAttr, used in butGWB_Articles. Used in: · SrcBibPgf, when preparing links to Literature Cited in an Article. Note: the slightly different usage here than in other places.


Input: [0] strOut [1] String [2]

Output: A string for this routine to put its data into. The subroutine WriteData will clean this variable out as the data is written to the output file.


Input: [0] strPgfArtBase [1] String [2]

Output: Parameter to SrcPgfOthPgf.


Input: [0] strPgfLocn [1] String [2]

Output: Parameter to SrcPgfLocn


Input: [0] strPgfParaNbr [1] String [2]

Output: Parameter to SrcPgfOthPgf.


Input: [0] strPhoArtBase [1] String [2]

Output: Used in SrcPhotoArticles


Input: [0] strPhoLetter [1] String [2]

Output: Parameter to SrcPhotoLetter, gives the Anchor of the letter for which photographs are to be found.


Input: [0] strPhoLocn [1] String [2]

Output: Parameter tp SrcPhotoLocn, gives the anchor of the location for which photographs are to be found.


Input: [0] strPhoParaNbr [1] String [2]

Output: Used in SrcPhotoArticles


Input: [0] strPhotoURLIn [1] String [2]

Output: Used in GetPhotoInfo as the primary argument.


Input: [0] strPrevArtPage [1] String [2]

Output: Pointer to relative URL of the previous article page.


Input: [0] strPrevCollPage [1] String [2]

Output: Pointer to the relative URL of the previous collection page.


Input: [0] strTB [1] String [2]

Output: Temporary buffer for debugging purposes


Input: [0] strTypeAnchIn [1] String [2]

Output: Used as argument to SrcLocnTypes


Input: [0] strURLIn [1] String [2]

Output: Parameter to SrcLocnPhoto which creates a list of locations for which the Photo was used.


Input: [Parameter name] page.margin.top [What it specifies]

Output: Top of page edge to top of header area.


Input: [Parameter name] region.before.extent [What it specifies]

Output: Height of header area, from top of the header text to the bottom of the header area.


Input: [Parameter name] body.margin.top [What it specifies]

Output: Top of header area to top of main text area.


Input: [Parameter name] body.margin.bottom [What it specifies]

Output: Bottom of main text area to bottom of footer area.


Input: [Parameter name] region.after.extent [What it specifies]

Output: Height of footer area, from the top of the footer area to the bottom of the footer text.


Input: [Parameter name] page.margin.bottom [What it specifies]

Output: Bottom of footer area to bottom of page edge.


Input: [Button] L [Shortcut Keys] Alt+L [Behavior]

Output: To select the language in which the Invoice is to be printed.


Input: [Button] I [Shortcut Keys] Alt+I [Behavior]

Output: To preview the Invoice


Input: [Button] T [Shortcut Keys] Alt+T [Behavior]

Output: To change the Report Titles


Input: [Button] G [Shortcut Keys] Alt+G [Behavior]

Output: To select the Page range for printing


Input: [Button] R [Shortcut Keys] Alt+R [Behavior]

Output: To change the method of printing


Input: [Button] F [Shortcut Keys] Alt+F [Behavior]

Output: To change the print format/mode


Input: [Button] C [Shortcut Keys] Alt+C [Behavior]

Output: To increase/change the number of copies to print, and also to choose the type of copy to be printed


Input: [Button] S [Shortcut Keys] Alt+S [Behavior]

Output: To change/select the Printer


Input: [Name] WACS_T_LLCORNER [Unicode] 0x2517 [Default] + [Description]

Output: thick lower left corner


Input: [Name] WACS_T_URCORNER [Unicode] 0x2513 [Default] + [Description]

Output: thick upper right corner


Input: [Name] WACS_T_LRCORNER [Unicode] 0x251b [Default] + [Description]

Output: thick lower right corner


Input: [Name] WACS_T_LTEE [Unicode] 0x252b [Default] + [Description]

Output: thick tee pointing right


Input: [Name] WACS_T_RTEE [Unicode] 0x2523 [Default] + [Description]

Output: thick tee pointing left


Input: [Name] WACS_T_BTEE [Unicode] 0x253b [Default] + [Description]

Output: thick tee pointing up


Input: [Name] WACS_T_TTEE [Unicode] 0x2533 [Default] + [Description]

Output: thick tee pointing down


Input: [Name] WACS_T_HLINE [Unicode] 0x2501 [Default] - [Description]

Output: thick horizontal line


Input: [Name] WACS_T_VLINE [Unicode] 0x2503 [Default] | [Description]

Output: thick vertical line


Input: [Name] WACS_T_PLUS [Unicode] 0x254b [Default] + [Description]

Output: thick large plus or crossover


Input: [Name] WACS_D_ULCORNER [Unicode] 0x2554 [Default] + [Description]

Output: double upper left corner


Input: [Name] WACS_D_LLCORNER [Unicode] 0x255a [Default] + [Description]

Output: double lower left corner


Input: [Name] WACS_D_URCORNER [Unicode] 0x2557 [Default] + [Description]

Output: double upper right corner


Input: [Name] WACS_D_LRCORNER [Unicode] 0x255d [Default] + [Description]

Output: double lower right corner


Input: [Name] WACS_D_RTEE [Unicode] 0x2563 [Default] + [Description]

Output: double tee pointing left


Input: [Name] WACS_D_LTEE [Unicode] 0x2560 [Default] + [Description]

Output: double tee pointing right


Input: [Name] WACS_D_BTEE [Unicode] 0x2569 [Default] + [Description]

Output: double tee pointing up


Input: [Name] WACS_D_TTEE [Unicode] 0x2566 [Default] + [Description]

Output: double tee pointing down


Input: [Name] WACS_D_HLINE [Unicode] 0x2550 [Default] - [Description]

Output: double horizontal line


Input: [Name] WACS_D_VLINE [Unicode] 0x2551 [Default] | [Description]

Output: double vertical line


Input: [Name] WACS_D_PLUS [Unicode] 0x256c [Default] + [Description]

Output: double large plus or crossover


Input: [Class] SOA [Function] Defines the start of a zone or a subzone; subordinate records inherit parameters [Typical RDATA] Multiple fields [RR Name]

Output: Start Of Authority

Domain Name System - Citable Version - Citizendium


Input: [Class] A [Function] Specifies the IPv4 address for a host [Typical RDATA] IPv4 Address [RR Name]

Output: Address IPv4

Domain Name System - Citable Version - Citizendium


Input: [Class] AAAA [Function] Specifies the IPv6 address for a host [Typical RDATA] IPv6 Address [RR Name]

Output: Address IPv6

Domain Name System - Citable Version - Citizendium


Input: [Class] PTR [Function] Reverse mapping of address to name [Typical RDATA] Name [RR Name]

Output: "Pointer"

Domain Name System - Citable Version - Citizendium


Input: [Class] CNAME [Function] Specifies an alias name for an address [Typical RDATA] Address [RR Name]

Output: Canonical name

Domain Name System - Citable Version - Citizendium


Input: [Class] NS [Function] (usually) An address of a name server one level of domain hierarchy above the current domain [Typical RDATA] Address [RR Name]

Output: Name server

Domain Name System - Citable Version - Citizendium


Input: [Class] MX [Function] Defines the start of a zone or a subzone; subordinate records inherit parameters [Typical RDATA] A 16 bit preference value (lower is better) followed by a host name willing to act as a mail exchange for the owner domain. [RR Name]

Output: Mail exchanger

Domain Name System - Citable Version - Citizendium


Input: [Type] Numeric [Description] The maximum flow setpoint presently in use by the UCM.Units: percent [Presentation Name]

Output: Active Max Flow Setpoint

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] The minimum flow setpoint presently in use by the UCM.Units: percent [Presentation Name]

Output: Active Min Flow Setpoint

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] Indicates if at least one of the UCM's thumbwheel inputs has been used to request that the air valve be driven to its maximum position/flow. 0=No, 1=Yes [Presentation Name]

Output: Air Valve Drive Max: Local Ovrd

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] This is the calculated value of the flow in terms of cubic feet per minute (CFM). [Presentation Name]

Output: Air Valve Flow

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] This property indicates the UCM-resident value of the maximum flow setpoint. This value is represented in terms of percent of the nominal size rating of the unit. [Presentation Name]

Output: Air Valve Max Flow Stpnt: Local

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] This property indicates the UCM-resident edited cooling minimum flow setpoint. This value is represented in terms of percent of the nominal size rating of the unit. [Presentation Name]

Output: Air Valve Min Flow Stpnt: Local

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Multi-State [Description] The flow override condition of the UCM. 1=Open 2=Closed 3=Min 4=Max 5=Auto [Presentation Name]

Output: Air Valve Override Status

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] Indicates the percent open position of the air valve. Range: 0 to 100% [Presentation Name]

Output: Air Valve Position

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] Indicates if the UCM is using position control. 0=No (Flow control) 1=Yes (Position control) Note: Position control is used when the flow sensor has failed or does not exist. [Presentation Name]

Output: Air Valve Position Control Used

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] The index value used to determine the nominal CFM rating of the unit. [Presentation Name]

Output: Air Valve Size Index

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] This property indicates the UCM-resident edited heating minimum flow setpoint. This value is represented in terms of percent of the nominal size rating of the unit. [Presentation Name]

Output: Air Vlv Min Heat Flow Stpnt: Loc

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] Indicates the temperature reported by the optional thermistor connected to the auxiliary sensor input on the UCM. Range: 25 to 190°F [Presentation Name]

Output: Auxiliary Temperature

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] Indicates if the UCM is presently calibrating its air valve (taking a zero flow reading). 0=Normal, 1=Recalibrate [Presentation Name]

Output: Calibration in Effect

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Multi-State [Description] This is the heat/cool call status of the UCM.0=“ “: The UCM has a vote but is not currently calling for heating or cooling. 1=“H”: Heat Caller 2=“H+”: Strong Heat Caller 3=“C”: Cool Caller 4=“C+”: Strong Cool Caller 5=“Tag”: The UCM has had problems reaching its setpoint and has been tagged by the CCP. It does not have a heat/cool vote. 6=“N/V”: The UCM does not get a heat/cool vote because its zone temp has failed; it is edited to not have a vote; or it has been flow overridden to closed. [Presentation Name]

Output: Call Status

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] This property will be Down if the UCM is not communicating with the Central Control Panel or if the Central Control Panel is not communicating with the BCU. 0=Down, 1=Up [Presentation Name]

Output: Communication State

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] The heat/cool control action is automatically determined by the VariTrac II Central Control Panel for each UCM. The Central Control Panel determines a UCM's heat/cool control action by comparing the system's supply air temperature with the UCM's zone temperature. The control action will indicate if there is warm or cold air in the supply duct. 0=Heating, 1=Cooling [Presentation Name]

Output: Control Action

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] Indicates if the UCM is occupied. 0=Occupy, 1=Unoccupy [Presentation Name]

Output: Control Mode

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] The value used by the control offset function to adjust the setpoints when the control offset is active. Range: 0 to 5F [Presentation Name]

Output: Control Offset Value

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] The active cooling setpoint does not go below this limit regardless of the source of the setpoint. Range: 45 to 100F [Presentation Name]

Output: Cooling Setpoint Low Limit

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] The actual cooling setpoint in use by the UCM. Range: 45 to 95F [Presentation Name]

Output: Cooling Setpoint: Active

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] Indicates if the auxiliary temperature sensor has failed or does not exist. 0=Normal, 1=Failed [Presentation Name]

Output: Diag: Aux Sensor Fail

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] Indicates if the flow sensor has failed or does not exist.0=Normal, 1=Failed [Presentation Name]

Output: Diag: Flow Sensor Fail

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] Indicates if any of the wireless zone sensors associated with the UCM are reporting a low battery voltage. 0=No, 1=Yes [Presentation Name]

Output: Diag: Low Battery Exists

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] Indicates if all thumbwheel setpoints associated with this UCM have failed. This takes into account wireless thermostats, if used. 0=Normal, 1=Failed [Presentation Name]

Output: Diag: Setpoint Fail Global

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] Indicates if all the zone sensors associated with this UCM have failed. This takes into account wireless thermostats, if used. 0=Normal, 1=Failed [Presentation Name]

Output: Diag: Zone Sensor Fail Global

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] Indicates whether the UCM controls the parallel fan based on a temperature or flow setpoint. 0=Temp, 1=Flow This property only applies to parallel fan- powered VAVs. [Presentation Name]

Output: Fan Control Method: Local

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] If “Fan Control Method: Local” is “Temp”, this offset determines when the parallel fan is energized. This property is specified as a temperature offset above the zone heating setpoint. Range: 0 to 10°FThis property only applies to parallel fan-powered VAVs. [Presentation Name]

Output: Fan Control Offset

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] If “Fan Control Method: Local” is “Flow”, this setpoint determines when the parallel fan is energized. This setpoint is expressed as a percentage of the unit's nominal size rating. Range: 0 to 100% This property only applies to parallel fan- powered VAVs. [Presentation Name]

Output: Fan Control Setpoint: Local

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] Indicates if the UCM is configured to control a fan.0=No Fan, 1=Fan Present [Presentation Name]

Output: Fan Exists

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] The state of the UCM's fan output. 0=Off, 1=On [Presentation Name]

Output: Fan Output

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] If the unit is configured to have a fan, this property indicates the fan type. 0=Parallel Fan, 1=Serial Fan [Presentation Name]

Output: Fan Type

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] The state of the UCM's heat output(s). 0=Off, 1=On [Presentation Name]

Output: Heat Active

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] Indicates if the UCM is configured to control its heat outputs. 0=No Heat Available, 1=Heating Available [Presentation Name]

Output: Heat Exists

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] The active heating setpoint does not go above this limit regardless of the source of the setpoint. Range: 45 to 100F [Presentation Name]

Output: Heat Setpoint High Limit

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] This value is subtracted from the thumbwheel setpoint to determine the active heating setpoint when the thumbwheel setpoint is enabled. Range: 2 to 10°F [Presentation Name]

Output: Heat Setpoint Offset: Local

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] Indicates if the UCM is allowed to have a heat/cool vote and can influence the CCP's changeover calculations.0=Disabled, 1=Auto [Presentation Name]

Output: Heat/Cool Vote Enable

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] The heating setpoint currently being used by the UCM.Range: 45 to 95F [Presentation Name]

Output: Heating Setpoint: Active

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Character [Description] This is the name of the UCM. This name differs from the “Object Name” in that it is stored at the VariTrac II Central Control Panel. [Presentation Name]

Output: Local Name

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Object ID [Description] Unique hexadecimal identifier of this particular object. This ID is used internally to identify a standard object. [Presentation Name]

Output: Object Identifier

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Character [Description] This property allows the assignment of a unique printable name to the object for user identification. [Presentation Name]

Output: Object Name

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Object Type [Description] This property designates the object's type (e.g., VariTrac II CCP VAV UCM). [Presentation Name]

Output: Object Type

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] The UCM-resident edited occupied cooling setpoint.Range: 45 to 95°F [Presentation Name]

Output: Occupied Cool Setpoint: Local

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] The UCM-resident edited occupied heating setpoint.Range: 45 to 95°F [Presentation Name]

Output: Occupied Heat Setpoint: Local

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] Used to calculate the ventilation ratio during occupied operation. Units: CFM. Range: 0 to 100% of the unit's nominal size rating. [Presentation Name]

Output: Occupied OA Required Setpoint

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Object ID [Description] Specifies the VariTrac II CCP System object to which this UCM belongs. [Presentation Name]

Output: Parent ID

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] This property identifies the security class to be used for access privileges to the given object. [Presentation Name]

Output: Security Class

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] The version of software loaded into the UCM. [Presentation Name]

Output: Software Revision

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] The composite thumbwheel setpoint which takes into account wireless thermostat values. Range: 45 to 95F [Presentation Name]

Output: Thumbwheel Composite

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] Indicates if the thumbwheel setpoint is in use. 0=No Thermostat Setpoint,1=Thermostat Setpoint [Presentation Name]

Output: Thumbwheel Setpoint Enable

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] The number (1-16) by which the UCM is known within the CCP. [Presentation Name]

Output: UCM Number

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] Indicates if the UCM is configured to control a VariTrane or VariTrac box. 0=Not VariTrac, 1=VariTracThis property only applies if “Unit Type is Trane” is Yes. [Presentation Name]

Output: Unit Type

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] Indicates if the UCM is configured to control a Trane unit (as opposed to a generic unit). 0=No, 1=Yes [Presentation Name]

Output: Unit Type is Trane

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] The UCM-resident, edited, unoccupied cooling setpoint.Range: 45 to 95°F [Presentation Name]

Output: Unoccupied Cool Setpoint: Local

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] The UCM-resident edited unoccupied heating setpoint. Range: 45 to 95°F [Presentation Name]

Output: Unoccupied Heat Setpoint: Local

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Binary [Description] Indicates if the local thumbwheel override to unoccupied is initiated. 0=No, 1=Yes [Presentation Name]

Output: Unoccupied Override: Local

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] Object instance update tag. This tag is used to indicate that the nonvolatile memory resident data within the particular instance has changed. The workstation is the primary user of this property. [Presentation Name]

Output: Update Tag

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] This ratio is calculated by dividing the outdoor air requirement by the current flow or damper position.Note: During unoccupied operation, the Unoccupied Outdoor Air Requirement (edited at the CCP) is used in this calculation. [Presentation Name]

Output: Ventilation Ratio Calc

VariTrac II Central Control Panel VAV Boxes


Input: [Type] Numeric [Description] The actual zone temperature being used by the UCM which takes into account wireless thermostat values, if used. Range: 0 to 125°F [Presentation Name]

Output: Zone Temp Composite

VariTrac II Central Control Panel VAV Boxes


Input: [Group] M11 [Check level] 1 [Status]

Output: In good shape Words to standardize subgroup generators required Gap versions of integral reps needed


Input: [Group] M12 [Status]

Output: In reasonable shape


Input: [Group] M22 [Status]

Output: One char 0 representation to copy. 12M22.2 rep to sort out. Checks to do. Class lists for 12M22(.2) are essential to check virtue


Input: [Group] M23 [Check level] 0 [Status]

Output: In good shape


Input: [Group] M24 [Check level] 0 [Status]

Output: In reasonable shape Integral representation not copied


Input: [Group] J1 [Check level] 1 [Status]

Output: In reasonable shape


Input: [Group] J2 [Check level] 0 [Status]

Output: In reasonable shape - integral rep to copy


Input: [Group] J3 [Check level] 0 [Status]

Output: In reasonable shape Words for G.2 required.


Input: [Group] J4 [Check level] 1 [Status]

Output: In good shape


Input: [Group] HS [Check level] 0 [Status]

Output: In reasonable shape Integral rep not copied


Input: [Group] McL [Check level] 0 [Status]

Output: In reasonable shape - integral rep to copy Word for auto to copy. Words for G.2 to calculate