Naming Conventions Sample Clauses

Naming Conventions. Always create user mailboxes the same as their iSeries User-Id. Use this same value for the POP3 Mail-Id, if possible. If you wish to use a different convention for your Internet addresses, then be sure to use the Mail-Id in both the Return Address and the Routing Entry. Given: Assign: User name: John Smith Mailbox: JOHN iSeries User-Id: JOHN Return address: jsmith@domain Mail-Id: JSMITH Routing entry: JSMITH KeyesMail Servers KeyesMail servers can be used to allow PC's to send and receive mail using a PC mail client or a Web browser. You do not need to activate the SMTP or POP3 servers if you already have a network mail server. Otherwise, these servers can eliminate the need for each PC to dial-up the Internet independently. It can also save you money by eliminating multiple accounts with an ISP, when you have the ISP define a single domain mail account for your entire company. Starting and Stopping the Servers You may start or stop the KeyesMail Servers either manually or using commands: Manually starting or stopping KeyesMail Servers:
Naming Conventions. Files MUST: • Be named as identified in the XML (see section 7).
Naming Conventions. A. Landlord and Tenant hereby acknowledge and agree that prior to the 1A Effective Date, Landlord has caused (i) Suite 1.14A in the Building to be renumbered to Suite 418A, (ii) Suite 1.5 in the Building to be renumbered to Suite 405, (iii) Suite 1.5.1 in the Building to be renumbered to Suite 407, and (iv) Suite 1.5.2 to be renumbered to Suite 409.
Naming Conventions. Sites sampled as part of the DOH Support (NSSP) Project are numbered according to DOH site naming conventions. All DOH sites begin with “DH” and are numbered sequentially with three digit numbers according to the order of site establishment by DOH. Note that there are breaks in the numbering sequence for DOH sample sites within the DOH Support (NSSP) Project because six sites were added to the project after the initial sites were established. Groundwater sites begin with “GW” and are numbered sequentially with three digit numbers. Water Database stores data and/or well location information for 446 groundwater sites numbered GW001 through GW446, including some wells that are located off-Reservation. Surface water sample sites begin with “SW” and are numbered sequentially with three digit numbers. Water Database stores data and site location information for 133 surface water sites numbered SW001 through SW133. These sites have been historically and/or are currently sampled.‌‌ Spill response sample sites begin with “SR” and are numbered sequentially with three digit numbers. Spill response sample sites are established when new sites will be sampled multiple times due to spill response or other water quality concerns. There are currently 23 spill response sample sites numbered SR001 through SR023.
Naming Conventions. 75 12.17 Annual Reporting Requirements................................................................. 75 12.18 Post Closing Assistance to Seller............................................................... 76 ARTICLE 13 OTHER POST-CLOSING AGREEMENTS...................................................... 76 13.1 Post-Closing Maintenance of and Access to Information............................ 76 13.2 Cost Reports............................................................................................ 77 13.3 Misdirected Payments............................................................................... 77 13.4 Collection of Pre-Closing Receivables and Special Accounts..................... 78 13.5 Cost Report Liabilities............................................................................... 78 13.6 Advances by Buyer................................................................................... 79 ARTICLE 14 INDEMNIFICATION....................................................................................... 79 14.1 Indemnification by Seller........................................................................... 79 14.2 Indemnification by Vanguard and Buyer..................................................... 80 14.3 Notice and Procedure............................................................................... 80 14.4 Notice and Control of Litigation................................................................ 80 14.5 Notice of Claim........................................................................................ 81 14.6 Mixed Claims........................................................................................... 81 14.7 Presumption of Liability............................................................................. 81 14.8 Disputed Claims........................................................................................ 81 14.9 Payment of Losses.................................................................................... 81 14.10 Limitations/DMC Assistance..................................................................... 82 14.11 Survival.................................................................................................... 82
Naming Conventions. This section will define a set of conventions for naming all parameters, functions, etc., such that their type is easily recognizable across specifications.
Naming Conventions. In UniBasic there are two types of variable names; a short var and a long var. The default is the short form: letter or letter+ digit for numeric variables, and letter or letter+ digit +$ for a string variable. Any variable ending with a dollar sign is automatically recognized as a string variable. To use the long variable names, the global environment variable LONGVARS is set, or you may issue the command: VARIABLE +. A long variable is named by a letter followed by up to 31 additional characters which may be letters, digits or underscore. Lower-case letters are equivalent to their upper-case counterparts. Some examples of variable names include: A B0 DATA_VALUE A$ B0$ PHONE_NUMBER$ By default, up to 348 different variable names may be used within each program. This value may be restricted or increased through the use of the environment variable MAXVARS, which defaults to 348. When you enter a program statement that includes a previously unused variable name, the variable count is compared to MAXVARS. If the defini- tion of this new variable will exceed the limit, the following error is displayed: Too many variables defined Once a variable name is in the internal variable table, it is not removed even if all occurrences of its use are removed. A program must be dumped to ASCII form and re-loaded (see the DUMP/LOAD/GET commands) in order to release unused variable names. To increase the number of variable names beyond 348 (to 1113), the MAXVARS environment variable must be set to “extended”. The number of variables will only be increased in newly created programs. To increase the number of variables in an existing program beyond 348, the program must be dumped to text and then reloaded while MAXVARS is set to “extended”. If you exceed the number of variable names allowed, use the VARIABLE command to locate one or more variables that could be removed from the program. Manually (or using an editor), remove all occurrences of the deleted variables. Next, DUMP the program to text, perform a NEW, and finally reload (LOAD or GET) and resave the program.
Naming Conventions. For the purposes of this Clause 26 (Confidentiality), whichever of the Owner, Operator or the Lessee that is disclosing Confidential Information shall be referred to as the "Disclosing Party" and whichever of the Owner, Operator or the Lessee that is receiving Confidential Information shall be referred to as the "Receiving Party".