About this Article

This article assumes you understand the basic components of URLs. It also assumes a working knowledge of XML and how it applies to your application needs.

Documentation Conventions

This article uses documentation conventions that closely resemble those used in other documentation.

This...Means...Example
<element>XML elements appear between brackets.<cics_response>
NotesNotes appear with thin borders above and below the paragraph. Notes: This is note text.
ALL CAPSCommand names appear in capitalized text.HB_TRANID
monospaceText that you see onscreen or enter at a keyboard appears in monospaced text.Type ENTER.

About XML

XML stands for eXtensible Markup Language, and is a data format for structured document exchange between applications. Like HTML, it is a markup language derived from SGML. However, unlike HTML, which the Internet community created to format information and display it across multiple platforms, XML is best suited to organize data for structured document exchange between applications. While HTML specifies how a document should appear, it does not describe what kind of information the document contains or how it is organized. In the example below, an eBusiness transaction has been converted to HTML for display in a web browser.


<html>
<head>
<title>Untitled Document</title>
</head>
<body bgcolor="#FFFFFF">
<table width="75%" border="1">
<tr>
<td>Part #</td>
<td>Item description</td>
<td>Availability (units)</td>
</tr>
<tr>
<td>123-ABC</td>
<td>Component A</td>
<td>12 </td>
</tr>
<tr>
<td>456-DEF</td>
<td>Component B</td>
<td>5</td>
</tr>
</table>
</body>
</html>


To parse this HTML and identify which items within the <td></td> tags are part numbers, item descriptions and number of units available can get very complex because HTML does not differentiate between the contents of each pair of tags.

XML allows you to organize information in a standard way that can enable back-end systems to conduct business transactions in a known format. For example, business partners can standardize on specific XML syntax to describe purchase orders and can then automate the transfer of that information across otherwise incompatible systems. The HTML document above could be rendered in XML as follows:


<?xml version="1.0" ?>
<response>
<catalogue_item>
<partnum>123-ABC</partnum>
<description>Component A</description>
<units>12 </units>
</catalogue_item>
<catalogue_item>
<partnum>456-DEF</partnum>
<description>Component B</description>
<units>5</units>
</catalogue_item>
</response>


The XML syntax is not only readable by humans, but the data can be easily parsed by applications or imported directly into databases, since all major databases now support the import and export of data in XML.  

Benefits of XML

The key benefit of retrieving host data in XML is that the information is completely independent of how you wish to display it. Because XML is an industry-standard markup language, it can be used for multiple purposes. For example, an eXtensible Style Language Transformation (XSLT) allows you to map XML tags and transform them to any other format. In the XML samples we have already seen, you could transform the XML into formats suitable for use with BizTalk, ebXML, UDDI, or any other growing eBusiness exchange technologies.

HostBridge accepts instructions from remote applications using XML documents. The elements of the XML documents control how HostBridge interacts with the CICS applications and provides input data for the CICS application fields. Element names parallel the parameter names passed to HostBridge using the HTTP query string interface. This section describes the structure of XML documents used to initiate BMS transactions and the unique elements they contain.

XML Structure

There are two sets of elements of the inbound document: parameters and fields. The elements contained within <parameter></parameter> correspond to HostBridge command parameters that control interactions with the CICS applications. The elements contained within <fields></fields> are input for named fields in the CICS application. Sample XML documents appear below.

The first example shows the initial XML documents sent to HostBridge to begin transactions with the CICS application. The <entry> element specifies the four-character transaction name and the <aid> element specifies the key used to submit the transaction to CICS.


<?xml version="1.0" ?>
<hostbridge>
<transaction>
<parameters>
<hb_tranid>jmpo</hb_tranid>
<hb_aid>enter</hb_aid>
</parameters>
</transaction>
</hostbridge>

The next examples show the XML document structure for subsequent transactions with HostBridge. Figure 2 shows a document that submits the value “IBM” in the company field using the PF3 key. The document also contains the token value returned by HostBridge following the initial transaction.


<?xml version="1.0" ?>
<hostbridge>
<transaction>
<parameters>
<hb_token>12345678</hb_token>
<hb_aid>pf3</hb_aid>
</parameters>
<fields>
<company>IBM</company>
</fields>
</transaction>
</hostbridge>

fields

  • Contains elements that identify fields and corresponding input data. (See Figure 2 above for an example.)

hostbridge

  • Identifies the XML document as containing HostBridge input data for use with a CICS transaction. Currently, HostBridge supports two input formats: hierarchical and flat.

The hierarchical format, which includes the <transaction>, <parameters>, and <fields> elements as shown below.


<?xml version="1.0" ?>
<hostbridge>
<transaction>
<parameters>
<hb_token>12345678</hb_token>
<hb_aid>pf3</hb_aid>
</parameters>
<fields>
<company>IBM</company>
</fields>
</transaction>
</hostbridge>



The flat format, which does not include the <transaction>, <parameters>, and <fields> elements appears below. To determine which elements are parameters and which are fields, HostBridge interprets all elements using the “hb_” prefix as parameters.


<?xml version="1.0" ?>
<hostbridge>
<hb_token>12345678</hb_token>
<hb_aid>pf3</hb_aid>
<company>IBM</company>
</hostbridge>


parameters

  • Contains the commands that tell HostBridge what to do and how to format the outbound XML response. (See the “HostBridge User Manual” for parameter descriptions.)

transaction

  • Contains the input data associated with a single CICS transaction.

SOAP Support

HostBridge provides native support for inbound requests as both basic XML documents and SOAP requests. This section explains the use of SOAP to conduct CICS transactions using HostBridge.

The examples below compare the structures of XML and SOAP documents sent to HostBridge to initiate a simple CICS transaction. The documents below tell HostBridge to use the Enter key to initiate the JMPO transaction without input data. To use HostBridge’s basic support for receiving an XML document to initiate a transaction, the XML would look like this.


<?xml version="1.0" ?>
<hostbridge>
<transaction>
<parameters>
<tranid>jmpo</tranid>
<aid>enter</aid>
</parameters>
</transaction>
</hostbridge>


According to the SOAP specification (found on www.w3c.org), the above XML document needs to be enclosed in what is called as SOAP envelope before it is sent to HostBridge. The XML document above contains only a few elements that contain the parameters HostBridge requires to conduct transactions with a CICS application. To initiate this same transaction using SOAP, the XML document contains extra information as shown below.


<?xml version="1.0" ?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV=”http://schemas.xmlsoap.org/soap/envelope/”>
<SOAP-ENV:Body>
<hb:hostbridge xmlns:”http://www.hostbridge.com/ns/”>
<hb:transaction>
<hb:parameters>
<hb:hb_tranid>jmpo</hb:hb_tranid>
<hb:hb_aid>enter</hb:hb_aid>
</hb:parameters>
</hb:transaction>
</hb:hostbridge>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>


Outbound XML

To make XML useful, the application that receives an XML document must understand the document vocabulary. XML is powerful in that companies can create named tags for each piece of data sent back and forth between applications. However, a change in the tag names can cause errors in the applications that receive and parse the XML for use in integration projects.

Each XML document returned from HostBridge to the requesting application conforms to a rigid structure comprised of elements and attributes. Each element or attribute describes a discreet piece of information that is useful to the application developer. The following index lists each element HostBridge can include in an XML document returned to a requesting application.

Element Index

abend_code

The <abend_code> element contains four-character codes if the CICS transaction that HostBridge calls abends. The abend code can contain letters and numbers.

aid

The <aid> element contains the attention identifier sent to CICS to execute the completed transaction. This value is sent as input to HostBridge using the HB_AID parameter.

Values

This element can have the following values.

CLEAR|CLRP|ENTER|MSRE|PA1|PA2|PA3|PEN|PF1|PF2|PF3|PF4|PF5|PF6|PF7|PF8| PF9|PF10|PF11|PF12|PF13|PF14|PF15|PF16|PF17|PF18|PF19|PF20|PF21|PF22| PF23|PF24|OPID|STRF|TRIG

Default

ENTER

attr

The <attr> element contains the field attribute information for the field. It breaks out the field attributes as shown below.

Attributes

This element can have the following attributes:

AttributeValueDescription
byte[number]The raw hexadecimal byte value of the field attribute byte
justifyl: left justification
r: right justification
Horizontal Justification. Indicates the horizontal justification for the input field.
dispy: indicates the field is displayed
n: indicates the field is hidden
Display/Nondisplay. Indicates whether this field is displayed on a 3270 terminal. ‘y’ indicates the field is displayed. ‘n’ indicates that the field is hidden from view.
proty: indicates a protected field that does not allow data to be entered
n: indicates unprotected fields
Protected/Unprotected. This indicates if the field is protected or unprotected. ‘y’ indicates protected which does not allow data to be entered. ‘n’ indicates unprotected which allows data to be entered into this field.
numy: accepts only numeric data
n: accepts alphanumeric data

Numeric/Alphhanumeric. Indicates whether a field accepts numeric or alphanumeric data. If ‘y’, only numeric values can be entered into this field. If ‘n’, any characters can be entered into this field. The numeric bit is context sensitive.

For unprotected fields, numeric is honored and the terminal should only allow numeric characters to be entered. It will return an error if you try to enter alpha characters.
For protected fields, you can place any content (Alpha, numeric, or special characters) in a protected field whether the numeric bit is set or not. When a protected field has numeric set, it means it is an auto skip field. The cursor will skip over these fields. Applications commonly place an unprotected field followed by an autoskip field so that as the operator fills the unprotected field the cursor skips to the next unprotected field due to the autoskip field.

inty: high intensity
n: normal intensity
High/Normal Intensity. Bright intensity field displays the data at a brighter than normal intensity. This is often used to highlight keywords, errors, or operator messages.
mdty: indicates a change to the field data
n: indicates no change made to the field.
Modified Data Tag. The modified data tag is turned on when fields are modified by the requesting application. When the requesting application sends an AID to HostBridge through a URL, the bridge facility only sends to CICS those fields that have been modified by the requesting application


camap_in

The <camap_in> element returns the name of the CAMAP used to create the input COMMAREA for the previous interaction. This element only appears with output from COMMAREA-based programs.

camap_out

The <camap_out> element returns the name of the CAMAP used to create the output COMMAREA for the previous interaction. This element only appears with output from COMMAREA-based programs.

cics_desc

The <cics_desc> element provides a description of the HostBridge error codes in the <cics_resp> element.

cics_resp

The <cics_resp> element identifies error codes related to Host Bridge errors. These include things such as errors during interactions with the 3270 bridge. HostBridge returns a decimal, numeric value when an error occurs during a transaction.

cics_resp2

The <cics_resp2> element displays a description that further qualifies the description returned in the <cics_desc> element. CICS applications sometimes use this when an error can have more than one cause. This is a decimal, numeric value.

command

The <command> element specifies which CICS API commands an application used to execute a CICS transaction.

Elements

This element can contain the following elements:

ElementDescription
<converse>CONVERSE command. Returns 3270 datastream in the XML document.
<send>SEND command. Returns 3270 datastream in the XML document.
<send_text>SEND TEXT command. Returns only text in the XML document.
<send_map>SEND MAP command. Returns field data in the XML document.
<send_control>SEND CONTROL command. Returns the control indicator values a CICS application sent to the facility.


Attributes

This element can have the following attributes:

AttributeValueDescription
src[text]Indicates the program that HostBridge used to generate XML output.


commarea

The <commarea> element contains data returned by an interaction with COMMAREA-based programs.

Attributes

This element can have the following attributes:

AttributeValueDescription
program[text]Indicates the COMMAREA-based program that HostBridge executed.


Elements

This element can contain the following elements:

ElementDescription
<fields>Contains data returned from a COMMAREA-based CICS program.
<parameters>Input and output data that control the interaction with a CICS application.
<status>Status information that indicates whether CICS encountered any errors during a transaction.


commarea_len

The <commarea_len> element returns the size of the COMMAREA used for the previous interaction. This element only appears with output from COMMAREA-based programs.

converse

The <converse> element indicates that the CICS applications executed the previous transaction using the CONVERSE command. The resulting XML document contains field data and literal screen text.

Attributes

This element can have the following attributes:

AttributeValueDescription
ErasenClears the facility buffer. For terminals, this would clear the screen.


Elements

This element can contain the following elements:

ElementDescription
<cursor>Indicates where CICS placed the cursor in the returned data following a transaction.
<fields>Contains field data returned from a CICS application following a completed transaction.
<screen>Contains the literal text from a 3270 screen.
<size>Indicates the number of rows and columns in the screen data.
<wcc>Indicates the write control character used.


convid

The <convid> element returns the eight-byte convid for the previous FEPI transaction as a 16-digit hex value. This element only appears with output from FEPI-based transactions.

The <copyright> element shows the copyright information for the HostBridge product.

Attributes

This element can have the following attributes:

AttributeValueDescription
info[text]Indicates the HostBridge copyright information.



cursor

The <cursor> element appears within <converse>, <send>, <send_map>, and <send_text> elements and indicates where CICS placed the cursor in the returned data following a transaction.

Attributes

This element can have the following attributes:

AttributeValueDescription
col[number]Identifies the column where CICS placed the cursor.
row[number]Identifies the row where CICS placed the cursor.
pos[number]Identifies the numeric position where CICS placed the cursor.
typeposA zero-based numeric value that identifies the exact position where CICS placed the cursor. This is a numeric position which has meaning on a 3270 terminal.  If the cursor is on or inside a field, the <field> element for the specified field will contain the <cursor_flag> element to indicate the cursor position within the XML document.



cursor_flag

The <cursor_flag> element indicates the field where CICS placed the cursor in the returned data following a transaction. This element only appears when the CICS application uses symbolic cursor positioning.

data

The <data> element contains data returned from a CICS application following a completed transaction. Output from a SEND TEXT transaction returns text to the requesting application.

Attributes

This element can have the following attributes:

AttributeValueDescription
len[number]Indicates the number of characters included in the output from a SEND TEXT transaction.


data_indicator

The <data_indicator> element indicates whether the CICS application used the MAPONLY, DATAONLY, or neither option with the SEND MAP command. The values associated with this element identify the options specified on the SEND MAP command. The values do not change the way in which HostBridge is used. They provide information to better understand the behavior of the host application. Some applications use these options in different contexts based on application flow. This provides subtle state information, which may be useful when accessing the application through HostBridge.

Values

This element can have the following values.

ValueDescription
map_and_dataCICS used neither MAPONLY nor DATAONLY to execute the SEND MAP command.
map_onlyCICS used MAPONLY to execute the SEND MAP command.
data_onlyCICS used DATAONLY to execute the SEND MAP command.



data_len_in

The <data_len_in> element identifies the length of the data string sent to HostBridge on the previous interaction. This element only appears with output from COMMAREA-based programs.

data_len_out

The <data_len_out> element identifies the length of the data string returned from HostBridge on the previous interaction. This element only appears with output from COMMAREA-based programs.

debug

The <debug> element is a decimal, numeric value indicating whether debug is enabled. Non-zero means enabled. This element only appears if debug is enabled. It is hidden if debug is disabled, which is the default.

desc

The <desc> element describes HostBridge numeric error codes returned in the <response> element. This is a human readable text description of the error message.

entry

The <entry> element contains the string used to execute the completed CICS transaction. Requesting applications send this value to HostBridge in the URL using the HB_ENTRY parameter. If the requesting application uses HB_TRANID and HB_DATA to execute a transaction, the <entry> element contains the equivalent entry string. The first four characters of this value appear within the <tran> element and the remaining characters appear within the <user_data> element.

erase

The <erase> element contains the list of fields erased by the HB_ERASE command during the previous transaction. If multiple fields were erased, the fields will appear in order with spaces between them (e.g., field_r1_c1 field_1 USER1).

extattr

The <extattr> element contains the extended attribute information for the field, as shown below.

Attributes

This element can have the following attributes:

AttributeValueDescription
colorred | pink | green | turq | yello | neutrColor. The color of the text in a field.
bgcolorred | pink | green | turq | yello | neutrBackground color. The color behind the text.
hlt

blink: blinking text | revrs: reverse video | undln: underlining

Highlighting. Indicates the presence of blinking text, reverse video, or underlining within a field.
val

mfil: mandatory fill | ment: mandatory enter | mfe: mandatory fill and enter | mt: mandatory trigger | mft: mandatory fill and trigger | met: mandatory enter and trigger

Validation. Indicates whether a field must be validated to make sure it contains data, must be filled, or is a trigger field.

Mandatory fill: A field that, if modified by operator, must be filled with characters other than null character before the operator can move the cursor out of the field or transmit any data from the display.

Mandatory enter: A field that must be modified by operator before the operator can transmit any data the display.

Trigger: A field that, if modified by the operator, is transmitted inbound as soon as the operator tries to move the cursor out of the field. This allows the application program to receive and to validate fields one by one.

outln

under: underling | right: right vertical line | over: overline | left: left vertical line | box: box

Outlining. This indicates the presence of text borders around a field.
transy: indicates the field is opaque | n: the field is not opaque.Transparency. If an input field is opaque, the underlying presentation space cannot be viewed. If the field is not opaque (meaning it is transparent) then the underlying presentation space can be viewed.



facility_like

The <facility_like> element specifies the defined terminal to use as a model for the bridge facility.

Default

CBRF (if no facility is specified)

facility_timeout

The <facilty_timeout> element indicates the number of seconds the 3270 bridge will maintain the facility used to execute a completed transaction. The 3270 bridge will tear down the facility if HostBridge does not receive another transaction before the timeout value elapses. Attempts to use the facility after the timeout will result in the creation of a new bridge facility and a new session with the CICS application.

field

The <field> element identifies symbolic fields available for use in a transaction.

Attributes

This element can have the following attributes:

AttributeValueDescription
col[number]Identifies the column where a field begins.
index[number]If a field name occurs multiple times in an XML document, the index number provides a unique identifier for each instance. (Default is 0.)
name[text]

For BMS transactions: Field name provided by BMS.
For 3270 transactions: Field name identifies the row/column coordinates where the field begins. In the example below, the name identifies a field beginning at row 1, column 1.

<field name=”field_r1_c1” row=”1” column=”1”>

3270 transactions with unformatted screens will return

<field name=”field_r1_c1” row=”1” column=”1”>

- or -

<field name=”field_0”>
(if the HB_USE_ORDER parameter was used on input)

row[number]Identifies the row where a field begins.



Elements

This element can contain the following elements:

ElementDescription
<attr>Contains the field attribute information for the field.
<cursor_flag>Appears if CICS placed the cursor in the field when it returned data following a transaction.
<extattr>Contains the extended attribute information for a field.
<name>Field name provided by BMS.
<value>Text placed within the field returned by CICS.



field_erase

The <field_erase> element indicates whether or not HostBridge erased the contents for empty name/value pairs on the previous transaction.

fields

The <fields> element contains the symbolic fields available for use in a transaction. These correspond to the named fields in the BMS map.

Attributes

This element can have the following attributes:

AttributeValueDescription
count[number]Indicates the number of <field> elements contained in the XML document, which corresponds to the total number of protected and unprotected fields returned by a transaction.



hostbridge

The <hostbridge> element is the root element for a BridgeML document. It contains all the XML ouput from HostBridge and CICS after a transaction completes.

Elements

This element can contain the following elements:

ElementDescription
<token>A sessionID that HostBridge uses to maintain state with the facility assigned to a completed transaction. To continue a session, the sessionID must be passed back to HostBridge in the URL using the HB_TOKEN parameter.
<timestamp> Records transaction time. Timestamp is a text string which is 14 characters long. It is formatted according to YYYYMMDDHHMMSS, where
  • YYYY is a 4 digit year
  • MM is a 2 digit month, 0 padded to fill 2 spaces
  • DD is the day of the month, 0 padded to fill 2 spaces
  • HH is the hour in 24 hour time format, 0 padded to fill 2 spaces
  • MM is the minutes, 0 padded to fill 2 spaces
  • SS is the number of seconds, 0 padded to fill 2 spaces.
<status>Contains status information from HostBridge after a transaction completes.
<sysid>Contains the name of the region in which HostBridge runs.
<transaction>Contains information returned from CICS after a transaction completes.



Attributes

This element can have the following attributes:

AttributeValueDescription
build_date[date]Indicates HBR$MAIN build date and time for versioning.


input_cursor

The <input_cursor> element identifies where HostBridge placed the cursor for the previous transaction. The value indicates the field where HostBridge placed the cursor using symbolic cursor positioning.

input_cursor_pos

The <input_cursor_pos> element indicates a non-zero numeric value that identifies the position where HostBridge placed the cursor for the previous transaction.

line[number]

The <line[number]> element contains the literal text for a single row in a 3270 screen returned by HostBridge following a completed transaction. Each line element contains a number that identifies which row of text it contains. For example, the element <line24 /> contains the text that appears on row 24 of the 3270 screen.

link3270

The <link3270> element indicates the use of the Link3270 method for invoking the transaction under CICS Transaction Server 2.2. If this method is used, the element contains the numeral “1”.

map

The <map> element identifies which map a transaction used.

mapset

The <mapset> element identifies the mapset resource that contains the BMS map.

name

The <name> element contains the name assigned to the field in the BMS map.

Attributes

This element can have the following attributes:

AttributeValueDescription
len[number]Character length of the field name.



parameters

The <parameters> element contains input and output data that control the interaction with a CICS application.

Elements

This element can contain the following elements:

ElementDescription
<aid>Returns the AID key used to execute a CICS transaction.
<camap_in>Name of the CAMAP used to create the input COMMAREA.
<camap_out>Name of the CAMAP used to create the output COMMAREA.
<commarea_len>Size of the COMMAREA created by HostBridge to pass data to and from the CICS program.
<data_len_in>Length of the string sent to HostBridge to invoke the CICS program.
<data_len_out>Length of data returned by the CICS program.
<debug>Decimal, numeric value indicating whether debug is enabled. Non-zero means enabled. This element only appears if debug is enabled. It is hidden if debug is disabled, which is the default.
<entry>Transaction and user data passed in with the completed transaction. The first four characters represent the transaction ID that appears in the <tranid> element and the remaining characters represent the user data that appears in the <user_data> element.
<erase>Returns field names erased using the hb_erase command. Multiple field names appear with spaces between each name (e.g., “field_r1_c1 field_1 USER1).
<facility_like>Specifies the defined terminal to be used as a model for the bridge facility. The default is CBRF if no facility like is specified.
<facility_timeout>Decimal, numeric value that indicates the timeout for the bridge facility in seconds. If there is no activity on the facility for the specified number of seconds, the facility goes away.
<field_erase>Indicates whether HostBridge erased the contents of fields with empty name value pairs on the previous transaction.
<input_cursor>Returns the field name where HostBridge placed the cursor in the previous transaction.
<input_cursor_pos>Returns the zero-based decimal number indicating where HostBridge placed the cursor in the previous transaction.
<program>Name of the COMMAREA-based program HostBridge invoked.
<user_data>Data passed in with the transaction. This is data that is normally typed after the transaction name when entered at a terminal. It is specified using the HB_DATA parameter.
<userid>Userid under which a transaction operates. Identifies the userid passed to CICS to begin the completed transaction.
<xml_min>Indicates output is the result of HB_XML_MIN command.



passticket

The <passticket> element returns the passticket value for initial FEPI transactions in regions with security turned on and passtickets enabled to automate the signon transaction. This element only appears with output from FEPI-based transactions. If security is off in the region, then this element will not appear in the XML output.

program

The <program> element returns the name of the COMMAREA-based program HostBridge invoked. This element only appears with output from COMMAREA-based programs.

response

The <response> element shows HostBridge error codes. If HostBridge encounters problems during a transaction, it will return a numeric decimal error code. If the target application abends, this element contains the following message: “error: Application abend has occurred. See <abend_code> for the value.”

screen

The <screen> element contains the literal text in a 3270 screen following a completed transaction.

Elements

This element can contain the following elements:

ElementDescription
<line[number]>Contains the literal text for a single row in a 3270 screen. Each line element contains a number that identifies which row of text it contains.


send

The <send> element indicates that the CICS applications executed the previous transaction using the SEND command. The resulting XML document contains both field data and literal screen text.

Attributes

This element can have the following attributes:

AttributeValueDescription
erasenClears the facility buffer. For terminals, this would clear the screen



Elements

This element can contain the following elements:

ElementDescription
<cursor>Indicates where CICS placed the cursor in the returned data following a transaction.
<fields>Contains field data returned from a CICS application following a completed transaction.
<screen>Contains the literal text from a 3270 screen.
<size>Indicates the number of rows and columns in the screen data.
<wcc>Indicates the write control character used.



send_control

The <send_control> element indicates that the CICS application sent control indicators to the facility using the SEND CONTROL command. There is no data associated with send control.

Elements

This element can contain the following elements:

ElementDescription
<wcc>Indicates the write control character used.


send_map

The <send_map> element indicates that the CICS applications executed the previous transaction using the SEND MAP command. The resulting XML document contains data with mapping information and fields.

Attributes

This element can have the following attributes:

AttributeValueDescription
alarmnSounds an audible alarm for applications that support it.
erasenClears the facility buffer. For terminals, this would clear the screen
erase_unpnResets unprotected fields in an application to nulls before returning output to the facility.
reset_mdtnTurns off the modified data tag off for all fields in the facility buffer.
unlock_kbnIndicates whether the facility can receive input data from an application after a transaction executes.



Elements

This element can contain the following elements:

ElementDescription
<cursor>Indicates where CICS placed the cursor in the returned data following a transaction.
<mapset>Identifies the program that contains the BMS map.
<map>Identifies the map a transaction used.
<data_descriptor>Indicates whether the CICS application used the MAPONLY, DATAONLY or neither options with the SEND MAP command.
<fields>Contains data returned from a CICS application following a completed transaction.



send_text

The <send_text> element indicates that the CICS applications executed the previous transaction using the SEND TEXT command. The resulting XML document contains data without mapping information. Any non-printable characters are converted to spaces.

Attributes

This element can have the following attributes:

AttributeValueDescription
alarmnSounds an audible alarm for applications that support it.
erasenClears the facility buffer. For terminals, this would clear the screen
erase_unpnResets unprotected fields in an application to nulls before returning output to the facility.
reset_mdtnTurns off the modified data tag off for all fields in the facility buffer.
unlock_kbnIndicates whether the facility can receive input data from an application after a transaction executes.



Elements

This element can contain the following elements:

ElementDescription
<cursor>Indicates where CICS placed the cursor in the returned data following a transaction.
<data>Contains data returned from a CICS application following a completed transaction.
<wcc>Indicates the write control character used.



size

The <size> element indicates the size of the 3270 screen following a transaction. The value contained by this element equals the number of columns multiplied by the number of rows.

Attributes

This element can have the following attributes:

AttributeValueDescription
cols[number]Indicates the number of columns in a 3270 screen.
rows[number]Indicates the number of rows in a 3270 screen.


status (<hostbridge> parent)

The <status> element within the <hostbridge> element contains HostBridge status information that indicates whether HostBridge encountered any errors during a transaction.

Elements

This element can contain the following elements:

ElementDescription
<response>Shows HostBridge decimal, numeric error codes.
<desc>Describes HostBridge numeric error codes returned in the <response> element. This is a human-readable text string.



status (<transaction> parent)

The <status> element within the <transaction> element contains status information that indicates whether CICS encountered any errors starting the transaction. HostBridge passes any errors that occurred during the transaction in the <abend_code> element.

Elements

This element can contain the following elements:

ElementDescription
<cics_resp>Error codes related to Host Bridge interactions with the 3270 bridge.
<cics_resp2>Displays a description that further qualifies the description returned in the <cics_desc> element. CICS applications sometimes use this when an error can have more than one cause.
<cics_desc>Provides a description of the error codes identified in the <cics_resp> element.
<task_end>Contains the value returned on output messages showing the status of the user transaction.
<abend_code>Contains alphanumeric codes if the CICS transaction abends.



task_end

The <task_end> element contains the value returned on output messages showing the status of the user transaction.

Values

This element can have the following values.

ValueDescription
nosyncUser transaction has not yet completed, and has not syncpointed.
commitUser transaction has not yet completed, but has syncpointed the first unit of work.
backoutUser transaction has not yet completed. The current unit of work will be backed out.
endtaskUser transaction has ended (or abended).



timestamp

The <timestamp> element contains a 14-character numeric value that represents the time when HostBridge returned the transaction data to the requesting application. Timestamp is a text string which is 14 characters long and uses the YYYYMMDDHHMMSS data format, where

  • YYYY is a 4 digit year
  • MM is a 2 digit month, 0 padded to fill 2 spaces
  • DD is the day of the month, 0 padded to fill 2 spaces
  • HH is the hour in 24 hour time format, 0 padded to fill 2 spaces
  • MM is the minutes, 0 padded to fill 2 spaces
  • SS is the number of seconds, 0 padded to fill 2 spaces.

token

The <token> element contains a token that HostBridge uses to maintain state with the facility assigned to a completed transaction. To continue a session, the requesting application must pass the token back to HostBridge in the URL using the HB_TOKEN parameter.

tranid

The <tranid> element contains a four-character ID used to execute the completed CICS transaction. Requesting applications send this value to HostBridge in the URL using the HB_TRANID parameter.

transaction

The <transaction> element contains data about a completed CICS transaction.

Attributes

This element can have the following attributes:

AttributeValueDescription
facility[string]Indicates the name of the facility the 3270 bridge used to complete the transaction.
next_tranid[string]Specifies the transaction ID to be used with the next transaction in a pseudo-conversational transaction chain. If the completed transaction was not pseudo-conversational, this value will be blank. If the token from the current transaction (identified in the <token> element) is passed back in, next_tranid is the default id for the next transaction unless it is overridden through the use of the HB_TRANID parameter.
next_tranid_srcnormal | return_immediate | start

Specifies the source of the next_tranid attribute.

normal: "normal" The next tranid was generated by a RETURN TRANSID()

return_immediate: The next tranid was generated by a RETURN IMMEDIATE statement. HostBridge automatically launches the next tranid. There should be a <transaction> following the current one.

start: The next tranid was generated by a START statement using the same FACILITY. HostBridge automatically launches the next tranid. There should be a <transaction> following the current one.



Elements

This element can contain the following elements:

ElementDescription
<command>Specifies which CICS API commands HostBridge used to execute a CICS transaction.
<parameters>Input and output data that control the interaction with a CICS application.
<status>Status information that indicates whether CICS encountered any errors during a transaction.



user_data

The <user_data> element indicates data passed in to initiate the completed transaction. This is data that is normally typed after the transaction name when entered at a terminal and specified using the HB_DATA parameter. For example, in the transaction “trad michael 25467863” the user data is “michael 25467863”.

userid

The <userid> element identifies the userid passed to CICS to begin the completed transaction. This is useful if you need to verify what rights a client application has when executing transactions.

value

The <value> element contains input field data returned from the CICS application.

Attributes

This element can have the following attributes:

AttributeValueDescription
len[number]Indicates the length of data between the <value> and </value> elements.
maxlen[number]Indicates the maximum length of data an input field will accept.



wcc

The <wcc> element contains write control character byte normally sent in the 3270 data stream. The attributes can help determine application state or where the application is in the flow.

Attributes

This element can have the following attributes:

AttributeValueDescription
alarmnSounds an audible alarm for applications that support it.
resetnSets the facility to system default values.
reset_mdtnTurns off the modified data tag off for all fields in the facility buffer.
unlock_kbnIndicates whether the facility can receive input data from an application after a transaction executes.


Sample XML Documents for BMS Transactions

This section contains samples that illustrate how the outbound elements appear in XML documents returned to requesting applications.

SEND CONTROL Command

The following XML document is the result of a single-transaction with a CICS application using the SEND CONTROL command to retrieve data.


<?xml version="1.0" encoding="ISO-8859-1" ?>
<hostbridge>
<token />
<timestamp>20010618145431</timestamp>
<status>
<response>0</response>
<desc>ok</desc>
</status>
<transaction facility="}AAD" next_tranid="">
<status>
<cics_resp>0</cics_resp>
<cics_resp2>0</cics_resp2>
<cics_desc>ok</cics_desc>
<task_end>endtask</task_end>
<abend_code />
</status>
<parameters>
<tranid>T010</tranid>
</parameters>
<command>
<send_control erase="y" erase_unp="n" unlock_kb="n" alarm="'''n'''" reset_mdt="'''n'''" />
</command>
<command>
<send_text erase="'''y'''" erase_unp="'''n'''" unlock_kb="'''n'''" alarm="'''n'''" reset_mdt="'''n'''">
<data len="'''37'''">TEST0010: SEND CONTROL and SEND TEXT</data>
</send_text>
</command>
</transaction>
<copyright info="'''HostBridge Copyright 2000-2003 HostBridge Technology, U.S. Patent Pending'''" />
</hostbridge>


SEND MAP Command

The following XML document is the result of a transaction with a CICS application using the SEND MAP command to retrieve data. It is a pseudo conversational transaction. Since it has a token value, it has at least one transaction executed before it to get the application to this state.


<?xml version="1.0" encoding="ISO-8859-1" ?>
<hostbridge>
<token>95c6b871</token>
<timestamp>20010618142951</timestamp>
<status>
<response>0</response>
<desc>ok</desc>
</status>
<transaction facility="}AAG" next_tranid="TRAD">
<status>
<cics_resp>0</cics_resp>
<cics_resp2>0</cics_resp2>
<cics_desc>ok</cics_desc>
<task_end>endtask</task_end>
<abend_code />
</status>
<parameters>
<tranid>TRAD</tranid>
</parameters>
<command>
<send_map erase="y" erase_unp="n" unlock_kb="y" alarm="n" reset_mdt="n">
<mapset>TRADBMS</mapset>
<map>T002</map>
<data_indicator>map_and_data</data_indicator>
<fields count="6">
<field name="COMP1" index="0">
<name len="5">COMP1</name>
<value maxlen="20" len="19">Casey_Import_Export</value>
<attr byte="00" justify="l" disp="n" prot="n" num="n" int="n" mdt="n" />
</field>
<field name="COMP2" index="0">
<name len="5">COMP2</name>
<value maxlen="20" len="19">Glass_and_Luget_Plc</value>
<attr byte="00" justify="l" disp="n" prot="n" num="n" int="n" mdt="n" />
</field>
<field name="COMP3" index="0">
<name len="5">COMP3</name>
<value maxlen="20" len="20">Headworth_Electrical</value>
<attr byte="00" justify="l" disp="n" prot="n" num="n" int="n" mdt="n" />
</field>
<field name="COMP4" index="0">
<name len="5">COMP4</name>
<value maxlen="20" len="3">IBM</value>
<attr byte="00" justify="l" disp="n" prot="n" num="n" int="n" mdt="n" />
</field>
<field name="OPTION" index="0">
<name len="6">OPTION</name>
<value maxlen="1" len="0" />
<attr byte="00" justify="l" disp="n" prot="n" num="n" int="n" mdt="n" />
</field>
<field name="MESS2" index="0">
<name len="5">MESS2</name>
<value maxlen="79" len="0" />
<attr byte="00" justify="l" disp="n" prot="n" num="n" int="n" mdt="n" />
</field>
</fields>
</send_map>
</command>
</transaction>
<copyright info="HostBridge Copyright 2000-2003 HostBridge Technology, U.S. Patent Pending" />
</hostbridge>


SEND TEXT Command

The following XML document is the result of a single transaction with a CICS application using the SEND TEXT command to retrieve data. HostBridge retrieves the data from the SEND TEXT and returns the data to the requesting application without change.


<?xml version="1.0" encoding="ISO-8859-1" ?>
<hostbridge>
<token />
<timestamp>20010618144154</timestamp>
<status>
<response>0</response>
<desc>ok</desc>
</status>
<transaction facility="}AAH" next_tranid="">
<status>
<cics_resp>0</cics_resp>
<cics_resp2>0</cics_resp2>
<cics_desc>ok</cics_desc>
<task_end>endtask</task_end>
<abend_code />
</status>
<parameters>
<tranid>T001</tranid>
</parameters>
<command>
<send_text erase="y" erase_unp="n" unlock_kb="n" alarm="n" reset_mdt="n">
<data len="47">TEST0001: SEND TEXT This is a SEND TEXT test.</data>
</send_text>
</command>
</transaction>
<copyright info="HostBridge Copyright 2000-2003 HostBridge Technology, U.S. Patent Pending" />
</hostbridge>


SEND TEXT using RETURN IMMEDIATE

The following XML document is the result of a transaction with a CICS application using the SEND TEXT command that then issues a RETURN IMMEDIATE command to another application.


<?xml version="1.0" encoding="ISO-8859-1" ?>
<hostbridge>
<token />
<timestamp>20011217214349</timestamp>
<status>
<response>0</response>
<desc>ok</desc>
</status>
<transaction tranid="T011" facility="}AAB" next_tranid="T012" next_tranid_src="return_immediate">
<status>
<cics_resp>0</cics_resp>
<cics_resp2>0</cics_resp2>
<cics_desc>NORMAL</cics_desc>
<task_end>endtask</task_end>
<abend_code />
</status>
<parameters>
<tranid>T011</tranid>
<entry>T011</entry>
<userid>DSI2</userid>
</parameters>
</transaction>
<transaction tranid="T012" facility="}AAB" next_tranid="" next_tranid_src="">
<status>
<cics_resp>0</cics_resp>
<cics_resp2>0</cics_resp2>
<cics_desc>NORMAL</cics_desc>
<task_end>endtask</task_end>
<abend_code />
</status>
<parameters>
<tranid>T011</tranid>
<entry>T011</entry>
<userid>DSI2</userid>
</parameters>
<command src="TEST0012">
<send_text erase="y" erase_unp="n" unlock_kb="y" alarm="n" reset_mdt="n">
<data len="59">Facility : AAB Termid : AAB StartCode : TD Tellerid : 00</data>
</send_text>
</command>
</transaction>
<copyright info="HostBridge Copyright 2000-2003 HostBridge Technology, U.S. Patent Pending" />
</hostbridge>


SEND TEXT using START

The following XML document is the result of a transaction with a CICS application using the SEND TEXT command that then issues a START command to another application.


<?xml version="1.0" encoding="ISO-8859-1" ?>
<hostbridge>
<token />
<timestamp>20011217214257</timestamp>
<status>
<response>0</response>
<desc>ok</desc>
</status>
<transaction tranid="T023" facility="}AAA" next_tranid="T012" next_tranid_src="start">
<status>
<cics_resp>0</cics_resp>
<cics_resp2>0</cics_resp2>
<cics_desc>NORMAL</cics_desc>
<task_end>endtask</task_end>
<abend_code />
</status>
<parameters>
<tranid>T023</tranid>
<entry>T023</entry>
<userid>DSI2</userid>
</parameters>
</transaction>
<transaction tranid="T012" facility="}AAA" next_tranid="" next_tranid_src="">
<status>
<cics_resp>0</cics_resp>
<cics_resp2>0</cics_resp2>
<cics_desc>NORMAL</cics_desc>
<task_end>endtask</task_end>
<abend_code />
</status>
<parameters>
<tranid>T023</tranid>
<entry>T023</entry>
<userid>DSI2</userid>
</parameters>
<command src="TEST0012">
<send_text erase="y" erase_unp="n" unlock_kb="y" alarm="n" reset_mdt="n">
<data len="59">Facility : AAA Termid : AAA StartCode : S Tellerid : 00</data>
</send_text>
</command>
</transaction>
<copyright info="HostBridge Copyright 2000-2003 HostBridge Technology, U.S. Patent Pending" />
</hostbridge>


Sample XML Documents for 3270 Transactions

This section contains samples that illustrate how 3270 transactions appear in XML documents returned to requesting applications.

CONVERSE and SEND Commands

The following XML document is the result of a single-transaction with a CICS application using the CONVERSE command to retrieve data. CONVERSE and SEND transmit a 3270 datastream. HostBridge displays both field data and literal screen text in the resulting document. The example shows the output of a CONVERSE command, though the output from SEND is identical.


<?xml version="1.0" encoding="ISO-8859-1" standalone="yes" ?>
<hostbridge>
<token>f84c2b42</token>
<timestamp>20020531185505</timestamp>
<status>
<response>0</response>
<desc>ok</desc>
</status>
<transaction tranid="CEMT" facility="}AAA" next_tranid="" next_tranid_src="">
<status>
<cics_resp>0</cics_resp>
<cics_resp2>0</cics_resp2>
<cics_desc>NORMAL</cics_desc>
<task_end>nosync</task_end>
<abend_code />
</status>
<parameters>
<tranid>CEMT</tranid>
<entry>CEMT</entry>
<userid>DSI2</userid>
</parameters>
<command src="DFHEMTD">
<converse erase="y">
<size rows="24" cols="80">1920</size>
<wcc />
<fields count="27">
<field name="field_r1_c1" row="1" col="1" pos="0">
<name len="11">field_r1_c1</name>
<value maxlen="78" len="0" />
<attr byte="c8" justify="n" disp="y" prot="n" num="n" int="y" mdt="n" />
</field>
<field name="field_r1_c80" row="1" col="80" pos="79">
<name len="12">field_r1_c80</name>
<value maxlen="1" len="0" />
<attr byte="e8" justify="n" disp="y" prot="y" num="n" int="y" mdt="n" />
</field>
<field name="field_r2_c2" row="2" col="2" pos="81">
<name len="11">field_r2_c2</name>
<value maxlen="8" len="7">STATUS:</value>
<attr byte="60" justify="n" disp="y" prot="y" num="n" int="n" mdt="n" />
</field>
<field name="field_r2_c11" row="2" col="11" pos="90">
<name len="12">field_r2_c11</name>
<value maxlen="149" len="26">ENTER ONE OF THE FOLLOWING</value>
<attr byte="e8" justify="n" disp="y" prot="y" num="n" int="y" mdt="n" />
</field>
<field name="field_r4_c1" row="4" col="1" pos="240">
<name len="11">field_r4_c1</name>
<value maxlen="79" len="7">Discard</value>
<attr byte="60" justify="n" disp="y" prot="y" num="n" int="n" mdt="n" />
</field>
<field name="field_r5_c1" row="5" col="1" pos="320">
<name len="11">field_r5_c1</name>
<value maxlen="79" len="7">Inquire</value>
<attr byte="60" justify="n" disp="y" prot="y" num="n" int="n" mdt="n" />
</field>
<field name="field_r6_c1" row="6" col="1" pos="400">
<name len="11">field_r6_c1</name>
<value maxlen="79" len="7">Perform</value>
<attr byte="60" justify="n" disp="y" prot="y" num="n" int="n" mdt="n" />
</field>
<field name="field_r7_c1" row="7" col="1" pos="480">
<name len="11">field_r7_c1</name>
<value maxlen="1252" len="3">Set</value>
<attr byte="60" justify="n" disp="y" prot="y" num="n" int="n" mdt="n" />
</field>
<field name="field_r22_c54" row="22" col="54" pos="1733">
<name len="13">field_r22_c54</name>
<value maxlen="10" len="10">SYSID=HBR1</value>
<attr byte="60" justify="n" disp="y" prot="y" num="n" int="n" mdt="n" />
</field>
<field name="field_r22_c65" row="22" col="65" pos="1744">
<name len="13">field_r22_c65</name>
<value maxlen="95" len="15">APPLID=CICSHBR1</value>
<attr byte="60" justify="n" disp="y" prot="y" num="n" int="n" mdt="n" />
</field>
<field name="field_r24_c1" row="24" col="1" pos="1840">
<name len="12">field_r24_c1</name>
<value maxlen="2" len="2">PF</value>
<attr byte="c8" justify="n" disp="y" prot="n" num="n" int="y" mdt="n" />
</field>
<field name="field_r24_c4" row="24" col="4" pos="1843">
<name len="12">field_r24_c4</name>
<value maxlen="1" len="1">1</value>
<attr byte="60" justify="n" disp="y" prot="y" num="n" int="n" mdt="n" />
</field>
<field name="field_r24_c6" row="24" col="6" pos="1845">
<name len="12">field_r24_c6</name>
<value maxlen="4" len="4">HELP</value>
<attr byte="c8" justify="n" disp="y" prot="n" num="n" int="y" mdt="n" />
</field>
<field name="field_r24_c11" row="24" col="11" pos="1850">
<name len="13">field_r24_c11</name>
<value maxlen="5" len="0" />
<attr byte="60" justify="n" disp="y" prot="y" num="n" int="n" mdt="n" />
</field>
<field name="field_r24_c17" row="24" col="17" pos="1856">
<name len="13">field_r24_c17</name>
<value maxlen="1" len="1">3</value>
<attr byte="60" justify="n" disp="y" prot="y" num="n" int="n" mdt="n" />
</field>
<field name="field_r24_c19" row="24" col="19" pos="1858">
<name len="13">field_r24_c19</name>
<value maxlen="3" len="3">END</value>
<attr byte="c8" justify="n" disp="y" prot="n" num="n" int="y" mdt="n" />
</field>
<field name="field_r24_c23" row="24" col="23" pos="1862">
<name len="13">field_r24_c23</name>
<value maxlen="5" len="0" />
<attr byte="60" justify="n" disp="y" prot="y" num="n" int="n" mdt="n" />
</field>
<field name="field_r24_c29" row="24" col="29" pos="1868">
<name len="13">field_r24_c29</name>
<value maxlen="1" len="1">5</value>
<attr byte="60" justify="n" disp="y" prot="y" num="n" int="n" mdt="n" />
</field>
<field name="field_r24_c31" row="24" col="31" pos="1870">
<name len="13">field_r24_c31</name>
<value maxlen="3" len="3">VAR</value>
<attr byte="c8" justify="n" disp="y" prot="n" num="n" int="y" mdt="n" />
</field>
<field name="field_r24_c35" row="24" col="35" pos="1874">
<name len="13">field_r24_c35</name>
<value maxlen="6" len="0" />
<attr byte="60" justify="n" disp="y" prot="y" num="n" int="n" mdt="n" />
</field>
<field name="field_r24_c42" row="24" col="42" pos="1881">
<name len="13">field_r24_c42</name>
<value maxlen="5" len="0" />
<attr byte="60" justify="n" disp="y" prot="y" num="n" int="n" mdt="n" />
</field>
<field name="field_r24_c48" row="24" col="48" pos="1887">
<name len="13">field_r24_c48</name>
<value maxlen="5" len="0" />
<attr byte="60" justify="n" disp="y" prot="y" num="n" int="n" mdt="n" />
</field>
<field name="field_r24_c54" row="24" col="54" pos="1893">
<name len="13">field_r24_c54</name>
<value maxlen="1" len="1">9</value>
<attr byte="60" justify="n" disp="y" prot="y" num="n" int="n" mdt="n" />
</field>
<field name="field_r24_c56" row="24" col="56" pos="1895">
<name len="13">field_r24_c56</name>
<value maxlen="3" len="3">MSG</value>
<attr byte="c8" justify="n" disp="y" prot="n" num="n" int="y" mdt="n" />
</field>
<field name="field_r24_c60" row="24" col="60" pos="1899">
<name len="13">field_r24_c60</name>
<value maxlen="5" len="0" />
<attr byte="60" justify="n" disp="y" prot="y" num="n" int="n" mdt="n" />
</field>
<field name="field_r24_c66" row="24" col="66" pos="1905">
<name len="13">field_r24_c66</name>
<value maxlen="5" len="0" />
<attr byte="60" justify="n" disp="y" prot="y" num="n" int="n" mdt="n" />
</field>
<field name="field_r24_c72" row="24" col="72" pos="1911">
<name len="13">field_r24_c72</name>
<value maxlen="8" len="0" />
<attr byte="60" justify="n" disp="y" prot="y" num="n" int="n" mdt="n" />
</field>
</fields>
<cursor type="pos" row="1" col="3">2</cursor>
</converse>
</command>
</transaction>
<copyright info="HostBridge Copyright 2000-2003 HostBridge Technology, U.S. Patent Pending" />
</hostbridge>


Sample XML Documents for COMMAREA Programs

This section contains samples that illustrate how data from COMMAREA-based programs appears in XML documents returned to requesting applications.


<?xml version="1.0" encoding="ISO-8859-1" standalone="yes" ?>
<hostbridge>
<timestamp>20021022143640</timestamp>
<status>
<response>0</response>
<desc>ok</desc>
</status>
<commarea program="TRADERBL">
<status>
<cics_resp>0</cics_resp>
<cics_resp2>0</cics_resp2>
<cics_desc>NORMAL</cics_desc>
</status>
<parameters>
<program>TRADERBL</program>
<userid>DSI2</userid>
<camap_in>TRADER</camap_in>
<camap_out>TRADER</camap_out>
<commarea_len>372</commarea_len>
</parameters>
<fields>
<field name="ALARM-CHANGE" />
<field name="BUY-SELL-PRICE1" />
<field name="BUY-SELL-PRICE2" />
<field name="BUY-SELL-PRICE3" />
<field name="BUY-SELL-PRICE4" />
<field name="BUY-SELL1" />
<field name="BUY-SELL2" />
<field name="BUY-SELL3" />
<field name="BUY-SELL4" />
<field name="COMMISSION-COST-BUY" />
<field name="COMMISSION-COST-SELL" />
<field name="COMPANY-NAME" />
<field name="COMPANY-NAME-TAB_1" />
<field name="COMPANY-NAME-TAB_2" />
<field name="COMPANY-NAME-TAB_3" />
<field name="COMPANY-NAME-TAB_4" />
<field name="CORRELID" />
<field name="NO-OF-SHARES" />
<field name="NO-OF-SHARES-DEC">0</field>
<field name="REQUEST-TYPE" />
<field name="RETURN-VALUE">01</field>
<field name="TOTAL-SHARE-VALUE" />
<field name="UNIT-SHARE-PRICE" />
<field name="UNIT-VALUE-1-DAYS" />
<field name="UNIT-VALUE-2-DAYS" />
<field name="UNIT-VALUE-3-DAYS" />
<field name="UNIT-VALUE-4-DAYS" />
<field name="UNIT-VALUE-5-DAYS" />
<field name="UNIT-VALUE-6-DAYS" />
<field name="UNIT-VALUE-7-DAYS" />
<field name="UPDATE-BUY-SELL" />
<field name="USER-PASSWORD" />
<field name="USERID" />
</fields>
</commarea>
<copyright info="HostBridge Copyright 2000-2003 HostBridge Technology, U.S. Patent Pending" />
</hostbridge>



© 2022 HostBridge Technology, LLC
Unless otherwise noted, all rights reserved.