DOCSLIB.ORG

IBM Websphere Transformation Extender

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
IBM Websphere Transformation Extender IBM WebSphere Transformation Extender Functions and Expressions Ve r s i o n 8.1 Note Before using this information, be sure to read the general information in “Notices” on page 209. October 2006 This edition of this document applies to IBM WebSphere Transformation Extender Version 8.1; and to all subsequent releases and modifications until otherwise indicated in new editions. To send us your comments about this document, email [email protected]. We look forward to hearing from you. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Chapter 1. Expressions and evaluations . .1 Expressions . .1 Component rule expressions evaluate to true or false . .1 Map rule expressions evaluate to data . .1 Literals . .1 Data object names . .2 Object names in map rules . .2 Object names in component rules . .2 Card name . .3 Local type name . .3 Partition list . .3 Component path . .4 Indexed object names . .4 Component paths separated by a colon . .4 Component paths separated by IN . .5 Comment object name . .5 Shorthand notation . .6 Evaluating expressions . .6 Card order can influence the order of evaluation sets . .7 Functions influence the number of evaluation sets . .8 Object names influence the number of evaluation sets . .9 Operators . .10 Arithmetic operators . .11 Text operators . .11 Logical operators . .11 Comparison operators . .11 Order of operator evaluation . .11 Operands . .12 Using functions in expressions . .12 Function arguments . .12 Input arguments . .13 Nested input arguments . .13 Output arguments . .14 Function arguments and evaluation . .14 Map names in expressions . .15 Evaluation of functional maps in an expression . .15 Expressions that evaluate to NONE . .16 When an operand evaluates to NONE . .16 When an input argument of a function evaluates to NONE . .16 When an input argument of a functional map evaluates to NONE . .17 When an input of an executable map evaluates to NONE . .17 Impact of track setting on order of output . .17 Evaluated expressions assigned to output items . .18 NONE assigned to an output number . .18 Automatic item format conversions . .18 Numeric precision . .19 Chapter 2. Using functions . .21 Functions in a component rule . .21 Functions in a map rule . .21 Chapter 3. Syntax of a function . .23 Chapter 4. Function argument syntax . .25 © Copyright IBM Corp. 2006 iii Chapter 5. General functions . .27 CLONE . .27 DEFAULT . .27 ECHOIN . .28 HANDLEIN . .28 REFORMAT . .30 Chapter 6. Bit manipulation and testing functions . .31 SETOFF . .31 SETON . .31 TESTOFF . .32 TESTON . .33 Chapter 7. Conversion functions . .35 BASE64TOTEXT . .35 BCDTOHEX . .35 BCDTOINT . .36 BCDTOTEXT . .37 CONVERT . .38 DATETONUMBER . .38 DATETOTEXT . .39 FROMBASETEN . .40 FROMDATETIME . .41 FROMNUMBER . .41 HEXTEXTTOSTREAM . .42 INT . .43 NUMBERTODATE . .44 NUMBERTOTEXT . .44 PACK . .45 PACKAGE . .46 QUOTEDTOTEXT . .46 SERIESTOTEXT . .47 STREAMTOHEXTEXT . .48 SYMBOL . .49 TEXTTOBASE64 . .50 TEXTTOBCD . .50 TEXTTODATE . .51 TEXTTONUMBER . .52 TEXTTOQUOTED . .52 TEXTTOTIME . .53 TEXTTOTIME . .54 TOBASETEN . .54 TODATETIME . .55 TONUMBER . .56 UNPACK . .57 UNZONE . .58 ZONE . .59 Chapter 8. Date/time functions . .63 ADDDAYS . .63 ADDHOURS . .64 ADDMINUTES . .64 CURRENTDATE . .65 CURRENTDATETIME . .66 CURRENTTIME . ..
Load more

Recommended publications
  • Owner's Manual
    OWNER’S MANUAL M197WD M227WD M237WD Make sure to read the Safety Precautions before using the product. Keep the User's Guide(CD) in an accessible place for furture reference. See the label attached on the product and give the information to your dealer when you ask for service. Trade Mark of the DVB Digital Video Broadcasting Project (1991 to 1996) ID Number(s): 5741 : M227WD 5742 : M197WD 5890 : M237WD PREPARATION FRONT PANEL CONTROLS I This is a simplified representation of the front panel. The image shown may be somewhat different from your set. INPUT INPUT Button MENU MENU Button OK OK Button VOLUME VOL Buttons PROGRAMME PR Buttons Power Button Headphone Button 1 PREPARATION <M197WD/M227WD> BACK PANEL INFORMATION I This is a simplified representation of the back panel. The image shown may be somewhat different from your set. 1 2 3 4 5 6 7 COMPONENT AV-IN 3 AUDIO IN IN (RGB/DVI) AV 1 AV 2 OPTICAL Y DIGITAL AV 1 AV 2 AUDIO OUT VIDEO AUDIO 1 B P VIDEO HDMI RGB IN (PC) (MONO) AC IN 2 PR L DVI-D ANTENNA L IN AC IN SERVICE R AUDIO ONLY RS-232C IN (CONTROL & SERVICE) R S-VIDEO 8 9 10 11 12 13 14 1 PCMCIA (Personal Computer Memory Card 7 Audio/Video Input International Association) Card Slot Connect audio/video output from an external device (This feature is not available in all countries.) to these jacks. 2 Power Cord Socket 8 SERVICE ONLY PORT This set operates on AC power. The voltage is indicat- ed on the Specifications page.
    [Show full text]
  • Simcom Confidential File
    FILE SIM868_Series_Hardware_Design_V1.06 CONFIDENTIAL SIMCOM Smart Machine Smart Decision Document Title SIM868 Series Hardware Design Version V1.06 Date 2017-07-13 Status Release Document Control ID SIM868_Series_Hardware_Design_V1.06 General Notes SIMCom offers this information as a service to its customers, to support application and engineering efforts that use the products designed by SIMCom. The information provided is based upon requirements FILEspecifically provided to SIMCom by the customers. SIMCom has not undertaken any independent search for additional relevant information, including any information that may be in the customer’s possession. Furthermore, system validation of this product designed by SIMCom within a larger electronic system remains the responsibility of the customer or the customer’s system integrator. All specifications supplied herein are subject to change. Copyright This document contains proprietary technical information which is the property of SIMCom Limited, copying of this document and giving it to others and the using or communication of the contents thereof, are forbidden without express authority. Offenders are liable to the payment of damages. All rights reserved in the event of grant of a patent or the registration of a utility model or design. All specification supplied herein are subject to change without notice at any time. Copyright © Shanghai SIMCom Wireless Solutions Ltd. 2017 CONFIDENTIAL SIMCOM SIM868_Series_Hardware_Design_V1.06 1 2017-07-13 Smart Machine Smart Decision Contents 1. Introduction
    [Show full text]
  • Progress Datadirect for ODBC Drivers Reference
    Progress® DataDirect® for ODBC Drivers Reference September 2020 Copyright © 2020 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved. These materials and all Progress® software products are copyrighted and all rights are reserved by Progress Software Corporation. The information in these materials is subject to change without notice, and Progress Software Corporation assumes no responsibility for any errors that may appear therein. The references in these materials to specific platforms supported are subject to change. Corticon, DataDirect (and design), DataDirect Cloud, DataDirect Connect, DataDirect Connect64, DataDirect XML Converters, DataDirect XQuery, DataRPM, Defrag This, Deliver More Than Expected, Icenium, Ipswitch, iMacros, Kendo UI, Kinvey, MessageWay, MOVEit, NativeChat, NativeScript, OpenEdge, Powered by Progress, Progress, Progress Software Developers Network, SequeLink, Sitefinity (and Design), Sitefinity, SpeedScript, Stylus Studio, TeamPulse, Telerik, Telerik (and Design), Test Studio, WebSpeed, WhatsConfigured, WhatsConnected, WhatsUp, and WS_FTP are registered trademarks of Progress Software Corporation or one of its affiliates or subsidiaries in the U.S. and/or other countries. Analytics360, AppServer, BusinessEdge, DataDirect Autonomous REST Connector, DataDirect Spy, SupportLink, DevCraft, Fiddler, iMail, JustAssembly, JustDecompile, JustMock, NativeScript Sidekick, OpenAccess, ProDataSet, Progress Results, Progress Software, ProVision, PSE Pro, SmartBrowser, SmartComponent, SmartDataBrowser,
    [Show full text]
  • Telit Modules Software User Guide
    APPLICABILITY TABLE SW Versions AT Ref. Guide Standards GC Family ( Compact ) GC864-QUAD 10.00.xx4 GC864-QUAD V2 10.00.xx4 GC864-DUAL V2 10.00.xx4 GE/GL Family ( Embedded ) GE864-QUAD 10.00.xx4 GE864-QUAD V2 10.00.xx4 GE864-QUAD Automotive V2 10.00.xx4 GE864-QUAD ATEX 10.00.xx4 GE864-DUAL V2 10.00.xx4 GE864-GPS 10.00.xx4 GE865-QUAD 10.00.xx4 GL865-DUAL 10.00.xx4 GL865-QUAD 10.00.xx5 [1] GSM/GPRS GL868-DUAL 10.00.xx4 GE910-QUAD 13.00.xx3 GE910-QUAD AUTO 13.00.xx5 GE910-GNSS 13.00.xx4 GL865-DUAL V3 16.00.xx2 GL865-QUAD V3 16.00.xx3 GL868-DUAL V3 16.00.xx2 GE910-QUAD V3 16.00.xx3 GE866-QUAD 16.00.xx3 GT Family ( Terminal ) GT863-PY 10.00.xx4 GT864-QUAD 10.00.xx4 GT864-PY 10.00.xx4 HE910 Family HE910 1 12.00.xx4 HE910-GA 12.00.xx4 HE910-D 12.00.xx4 HE910-EUR / HE910-EUD 12.00.xx4 HE910-EUG / HE910-NAG 12.00.xx4 HE910-NAR / HE910-NAD 12.00.xx4 [17] HSPA-GSM/GPRS UE/UL Family (Embedded) UE910-EUR / UE910-EUD 12.00.xx4 UE910-NAR / UE910-NAD 12.00.xx4 UL865-EUR / UL865-EUD 12.00.xx4 UL865-NAR / UL865-NAD 12.00.xx4 UL865-N3G 12.00.xx4 Note: the features described by the present document are provided by the products equipped with the software versions equal or higher than the versions shown in the table.
    [Show full text]
  • 2.16.840.1.113883.10.20.22.4.27.Pdf
    Figure 227: Tobacco Use (V2) Example <observation classCode="OBS" moodCode="EVN"> <!-- ** Tobacco use ** --> <templateId root="2.16.840.1.113883.10.20.22.4.85" extension="2014-06-09" /> <id root="45efb604-7049-4a2e-ad33-d38556c9636c" /> <code code="11367-0" codeSystem="2.16.840.1.113883.6.1" displayName="History of tobacco use" /> <statusCode code="completed" /> <effectiveTime> <!-- The low value reflects the start date of the observation/value (moderate smoker) --> <low value="20090214" /> <!-- The high value reflects the end date of the observation/value (moderate smoker) --> <high value="20110215" /> </effectiveTime> <value xsi:type="CD" code="160604004" displayName="Moderate cigarette smoker, 10- 19/day" codeSystem="2.16.840.1.113883.6.96" /> <author typeCode="AUT"> <time value="201209101145-0800" /> <assignedAuthor> <id extension="555555555" root="1.1.1.1.1.1.1.2" /> </assignedAuthor> </author> </observation> 3.108 Vital Sign Ob se rvation (V2) [observation: identifier urn:hl7ii:2.16.840.1.113883.10.20.22.4.27:2014-06-09 (open)] Table 503: Vital Sign Observation (V2) Contexts Contained By: Contains: Vital Signs Organizer (V3) (required) Author Participation (optional) Health Concern Act (V2) (optional) Risk Concern Act (V2) (optional) This template represents measurement of common vital signs. Vital signs are represented with additional vocabulary constraints for type of vital sign and unit of measure. The following is a list of recommended units for common types of vital sign measurements: Name Unit PulseOx % Height/Head Circumf cm Weight kg Temp Cel BP mm[Hg] Pulse/Resp Rate /min BMI kg/m2 HL7 CDA R2.1 IG: Consolidated CDA Templates for Clinical Note (US Realm), DSTU R2.1—Vol.
    [Show full text]
  • Urdu Alphabet
    Urdu alphabet The Urdu alphabet is the right-to-left alphabet used for the Urdu language. It is Urdu alphabet a modification of the Persian alphabet known as Perso-Arabic, which is itself a اردو ﺗ ﺠﯽ derivative of the Arabic alphabet. The Urdu alphabet has up to 58 letters.[1] With 39 basic letters and no distinct letter cases, the Urdu alphabet is typically written in the calligraphic Nastaʿlīq script, whereas Arabic is more commonly in the Naskh style. Usually, bare transliterations of Urdu into Roman letters (called Roman Urdu) omit many phonemic elements that have no equivalent in English or other languages commonly written in the Latin script. The National Language Authority of Pakistan has developed a number of systems with specific notations Example of writing in the Urdu to signify non-English sounds, but these can only be properly read by someone alphabet: Urdu already familiar with the loan letters. Type Abjad Languages Urdu, Balti, Burushaski, others Contents Parent Proto-Sinaitic systems History Phoenician Nastaʿlīq Alphabet Aramaic Differences from Persian alphabet Retroflex letters Nabataean Vowels Arabic Vowel chart Alif Perso-Arabic Wāʾo Ye Urdu The 2 he's alphabet Ayn Nun Ghunnah Unicode U+0600 to U+06FF range Hamza U+0750 to U+077F Diacritics U+FB50 to U+FDFF Iẓāfat U+FE70 to U+FEFF Computers and the Urdu alphabet Encoding Urdu in Unicode Software Romanization standards and systems See also References Sources External links History The Urdu language emerged as a distinct register of Hindustani well before the Partition of India. It is distinguished most by its extensive Persian influences (Persian having been the official language of the Mughal government and the most prominent lingua franca of the Indian subcontinent for several centuries before the solidification of British colonial rule during the 19th century).
    [Show full text]
  • Unicode for Linguists
    Unicode for Linguists Kevin Scannell INNET Summer School Gniezno, Poland 4 September 2013 Encoding basics ● Encoding: a mapping characters ↔ numbers ● Computers are good at storing numbers! ● Encodings don't care how chars are input ● Also not concerned with how they're displayed ● No fonts, formatting, boldface, etc. – just text! ● “Modularity”; three independent layers ● Confusion in part b/c it was not always so ● (keyboards and fonts bundled together) Fonts ● Again, correctly-encoded text stands on its own ● Sure, fonts let you to render text on the screen ● But you have good wide-coverage fonts already ● There are some exceptions of course: ● I I I I I I I I I I I I I I I I ● And some fonts are buggy... ● Especially stacked diacritics, ligatures The Joy of Text ● Unicode encodes “plain text” (and no more) ● Plain text is portable across platforms ● Plain text is long-lived ● Plain text is the ultimate “open” format ● Plain text is indexed by Google, “discoverable” ● No proprietary tools needed to manipulate text ● Plain text is easily viewable, editable ● Allows you to bring powerful Unix tools to bear ● Even marked-up text like XML counts! Encodings: Some History ● ASCII (1963); A-Za-z, 0-9, etc., map to 0-127 ● EBCDIC (1964); mapping to 0-255 (w/ gaps) ● ISO 8859 series (1987-); 0-255, extend ASCII ● Big5 (1984); traditional Chinese ● Shift JIS; Japanese ● GB2312/18030; simplified Chinese ● Literally hundreds of others ● Why was this so terrible? Alphabet soup IBM1124, CP424, ISO_10367-BOX, ECMA-128, ISO8859-1, KOI-7, CSIBM1137,
    [Show full text]
  • Limited Asbestos Inspection Report
    LIMITED ASBESTOS INSPECTION REPORT FOR CITY OF ROCK HILL 150 Johnson Street Rock Hill, SC 29731 (803) 817-5147 LOCATION Building #6-Apartments 866 and 868 Crest Street Rock Hill, South Carolina INSPECTION DATE: February 11, 2015 REPORT DATE: February 20, 2015 INSPECTORS Travis L. Shaw – SC-DHEC License #BI-01061, Exp. 04/01/15 (864) 316-9518 Travis Williams – SC-DHEC License #ASB-BI-00713, Exp. 11/18/15 (864) 640-7744 For Crossroads Environmental, LLC 1258 Boiling Springs Road Spartanburg, South Carolina 29303 (864) 541-8736 CRE Project #13455-IN February 20, 2015 Mr. Thomas Branche City of Rock Hill 150 Johnston Street Rock Hill, South Carolina 29731 Re: Asbestos Inspection Report Building #6-Apartments 866 and 868 Crest Street, Rock Hill, South Carolina CRE Project Number: 13455-IN Dear Mr. Branche: Crossroads Environmental, LLC (CRE) completed a limited asbestos inspection of Building #6-apartments (866 and 868) located at 866 and 868 Crest Street in Rock Hill, SC on February 11, 2015. The inspection was performed by two SC-DHEC Licensed Asbestos Inspectors, and in accordance with South Carolina Department of Health and Environmental Control (SC-DHEC) and Environmental Protection Agency (EPA) Requirements. A detailed summary table of the sampling is included in Attachment I; however, this report should be read in its entirety. Building Description Building #6-apartments 866 and 868 are adjoining units built over a concrete slab with a wood frame. The buildings’ exterior includes a shingled roof with vinyl siding over transite and metal framed windows. Sampling consisted of vinyl floor tiles and adhesives, drywall and joint compound, attic insulation, roof shingles and felt, and transite siding with felt and insulation.
    [Show full text]
  • Telit's Modules Software User Guide 1Vv0300784 Rev
    Telit's Modules Software User Guide 1vv0300784 Rev. 21 – 2017-11-10 SPECIFICATIONS ARE SUBJECT TO CHANGE WITHOUT NOTICE NOTICES LIST While reasonable efforts have been made to assure the accuracy of this document, Telit assumes no liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained herein. The information in this document has been carefully checked and is believed to be reliable. However, no responsibility is assumed for inaccuracies or omissions. Telit reserves the right to make changes to any products described herein and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Telit does not assume any liability arising out of the application or use of any product, software, or circuit described herein; neither does it convey license under its patent rights or the rights of others. It is possible that this publication may contain references to, or information about Telit products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that Telit intends to announce such Telit products, programming, or services in your country. COPYRIGHTS This instruction manual and the Telit products described in this instruction manual may be, include or describe copyrighted Telit material, such as computer programs stored in semiconductor memories or other media. Laws in the Italy and other countries preserve for Telit and its licensors certain exclusive rights for copyrighted material, including the exclusive right to copy, reproduce in any form, distribute and make derivative works of the copyrighted material.
    [Show full text]
  • Naming Text Encodings to Demystify Them
    Naming Text Encodings to Demystify Them Document #: P1885R6 Date: 2021-08-14 Programming Language C++ Audience: LEWG Reply-to: Corentin Jabot <[email protected]> Peter Brett <[email protected]> If you can’t name it, you probably don’t know what it is If you don’t know what it is, you don’t know what it isn’t Tony Van Eerd Target C++23 Abstract For historical reasons, all text encodings mentioned in the standard are derived from a locale object, which does not necessarily match the reality of how programs and systems interact. This model works poorly with modern understanding of text, ie the Unicode model separates encoding from locales which are purely rules for formatting and text transformations but do not affect which characters are represented by a sequence of code units. Moreover, the standard does not provide a way to query which encodings are expected or used by the environment, leading to guesswork and unavoidable UB. This paper introduces the notions of literal encoding, environment encoding, and a way to query them. Examples Listing the encoding #include <text_encoding> #include <iostream> void print(const std::text_encoding & c) { std::cout << c.name() << " (iana mib: " << c.mib() << ")\n" << "Aliases:\n"; 1 for(auto && a : c.aliases()) { std::cout << '\t' << a << '\n'; } } int main() { std::cout << "Literal Encoding: "; print(std::text_encoding::literal()); std::cout << "Wide Literal Encoding: "; print(std::text_encoding::wide_literal()); std::cout << "environment Encoding: "; print(std::text_encoding::environment());
    [Show full text]
  • Estimated Taxing District Property Tax Cap Credits
    2019 Estimated Property Tax Cap Impact by District Ripley County 001 | ADAMS TOWNSHIP-SUNMAN DEARBORN Unit Type Unit Code Unit Name Estimated Credits 1 0000 RIPLEY COUNTY $447 2 0001 ADAMS TOWNSHIP $43 4 1560 SUNMAN-DEARBORN COMMUNITY SCHOOL $1,756 CORP 6 1006 SOUTHEASTERN INDIANA SOLID WASTE $19 MGMT Taxing District Total: $2,264 002 | ADAMS TOWNSHIP-BATESVILLE SCHO Unit Type Unit Code Unit Name Estimated Credits 1 0000 RIPLEY COUNTY $49 2 0001 ADAMS TOWNSHIP $5 4 6895 BATESVILLE COMMUNITY SCHOOL $151 CORPORATION 5 0199 BATESVILLE PUBLIC LIBRARY $13 6 1006 SOUTHEASTERN INDIANA SOLID WASTE $2 MGMT Taxing District Total: $221 Report produced by DLGF on 7/19/2018 Page 861 of 1111 2019 Estimated Property Tax Cap Impact by District Ripley County 003 | BATESVILLE CITY-ADAMS TOWNSHIP Unit Type Unit Code Unit Name Estimated Credits 1 0000 RIPLEY COUNTY $3,625 2 0001 ADAMS TOWNSHIP $97 3 0447 BATESVILLE CIVIL CITY $8,483 4 6895 BATESVILLE COMMUNITY SCHOOL $11,147 CORPORATION 5 0199 BATESVILLE PUBLIC LIBRARY $998 6 1006 SOUTHEASTERN INDIANA SOLID WASTE $170 MGMT Taxing District Total: $24,521 004 | SUNMAN TOWN Unit Type Unit Code Unit Name Estimated Credits 1 0000 RIPLEY COUNTY $1,653 2 0001 ADAMS TOWNSHIP $40 3 0857 SUNMAN CIVIL TOWN $1,829 4 1560 SUNMAN-DEARBORN COMMUNITY SCHOOL $6,496 CORP 6 1006 SOUTHEASTERN INDIANA SOLID WASTE $70 MGMT Taxing District Total: $10,088 Report produced by DLGF on 7/19/2018 Page 862 of 1111 2019 Estimated Property Tax Cap Impact by District Ripley County 005 | BROWN TOWNSHIP Unit Type Unit Code Unit Name Estimated
    [Show full text]
  • Chapter 22, Symbols
    The Unicode® Standard Version 13.0 – Core Specification To learn about the latest version of the Unicode Standard, see http://www.unicode.org/versions/latest/. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trade- mark claim, the designations have been printed with initial capital letters or in all capitals. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc., in the United States and other countries. The authors and publisher have taken care in the preparation of this specification, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. The Unicode Character Database and other files are provided as-is by Unicode, Inc. No claims are made as to fitness for any particular purpose. No warranties of any kind are expressed or implied. The recipient agrees to determine applicability of information provided. © 2020 Unicode, Inc. All rights reserved. This publication is protected by copyright, and permission must be obtained from the publisher prior to any prohibited reproduction. For information regarding permissions, inquire at http://www.unicode.org/reporting.html. For information about the Unicode terms of use, please see http://www.unicode.org/copyright.html. The Unicode Standard / the Unicode Consortium; edited by the Unicode Consortium. — Version 13.0. Includes index. ISBN 978-1-936213-26-9 (http://www.unicode.org/versions/Unicode13.0.0/) 1.
    [Show full text]