m204wiki - User contributions [en]

Charting using Janus Web Server and FusionCharts Free

2010-10-13T15:48:30Z

Dessick: added disclaimer

[[Category:Tutorial]]
==Background==
You've created a beautiful web site, but the only thing missing is a way to easily add bar graphs, pie charts or other business graphics. Fortunately, there is an easy way to do this at little or no cost using FusionCharts Free from [http://www.fusioncharts.com/free InfoSoft Global Ltd.] '''FusionCharts Free''' supports a generous number of business charts. Of course for more sophisticated options there is a more full featured version, for which you must pay a license fee.

==Disclaimer==
This tutorial should not be construed as an endorsement of [http://www.fusioncharts.com/free FusionCharts Free] or [http://www.fusioncharts.com/free InfoSoft Global Ltd.]. It is presented only as an example of how one can easily add business charts to Janus Web applications.
==Chart Types Supported==
'''FusionCharts Free''' supports the following chart types:
*Bar Charts (2D and 3D)
*Pie Charts (2D and 3D)
*Doughnut Charts
*Line Charts
*Area Charts
*Stacked Charts
*Combination (Line & Bar) Charts
*Candlestick Charts
*Funnel Charts
*Gantt Charts

There are 22 different charts, which are rendered as Adobe Flash (.swf) files in the browser using JavaScript.

==Getting Started==
The first step in using Fusion Charts is of course downloading the source. This can be found on the [http://www.fusioncharts.com/free FusionCharts Free] web site. Once you have downloaded the JavaScript files, you will need to upload them to a Model 204 file. The easiest way to do this is to use the Sirius FTP capability. (See the Sirius Janus Sockets Manual, Chapter 12). If you do not have Janus Sockets, you can use HTTP PUT or a Mainframe FTP package to get the files to your machine and subsequently to a Model 204 Procedure file. '''Hint''': when you upload the files to your Janus Web Procedure file, upload them as ''binary'' files to avoid the dreaded "Code Page" issue. You must then add a Janus Web Rule to send them to the browser as "binary". The data that will populate your chart will come from an XML file that is either created by another program specified by a URL, or coded directly in the charting program.

==Using FusionCharts Free with Janus Web==
Once you have uploaded your FusionCharts Free JavaScript files to your server and added appropriate Janus Web Rules to send them to the browser, you are ready to code a Janus Web application to chart your data. You might also need to add a web rule to use Adobe Flash for .swf files. I find the "Data URL" method (see FusionCharts Free documentation) the easiest. In your Janus Web Program, you would add a container for your chart and the JavaScript code to call the chart-type JavaScrip and also your data URL. '''Note:''' If your data URL program is being passed parameters, the URL must be URL Encoded using the Sirius URLENCODE function or the JavaScript "escape()" method.

In the <head> of your HTML file you will need to include the following:

<SCRIPT LANGUAGE="Javascript" SRC="/FusionCharts/FusionCharts.js"></SCRIPT>

You may need to modify the path name depending on your Janus Web Rules.

You will then add the following code in the <body> of the HTML:
<nowiki>...
HTML
<div id="chart1div">This text is replaced by the chart
</div>
<script type="text/javascript">
var chart1 = new FusionCharts("Pie2D.swf", "ChId1", "600", "400", "0", "0");
//To pass parameters, URLEncode the dataURL. Use escape() in JavaScript
chart1.setDataURL(escape("Data.URL?id=1&subId=2"));
chart1.render("chart1div");
</script>
END HTML
...</nowiki>

Assuming you have coded up everything properly, the FusionCharts Column2D.swf JavaScript will call the Data.URL User Language program which will return an XML file properly formatted for creating a FusionCharts 2D Column Chart. Here is an example of a Column2D XML File:

<graph caption='Pie Chart' decimalPrecision='0' showPercentageValues='0' showNames='1' numberPrefix='$' showValues='1' showPercentageInLabel='0' pieYScale='45' pieBorderAlpha='100' pieRadius='100' animation='0' shadowXShift='4' shadowYShift='4' shadowAlpha='40' pieFillAlpha='95' pieBorderColor='FFFFFF'>
<set value='25' name='Item A' color='AFD8F8'/>
<set value='17' name='Item B' color='F6BD0F'/>
<set value='23' name='Item C' color='8BBA00' isSliced='1'/>
<set value='65' name='Item D' color='A66EDD'/>
<set value='22' name='Item E' color='F984A1'/>
</graph>

[[File:XML_2DPie1.gif|frame|alt=Sample 2D Pie Chart|Sample 2D Pie Chart]]

==Debugging==
If you see the dreaded JavaScript Error at the bottom of the page, it could be caused by one of the following:
*You actually made an error typing your JavaScript. ''Remember JavaScript is case sensitive.''
*There is a problem with your Janus Web Rules. Check '''SIRSCAN''' and look for Janus Web Rule problems
*There is a problem with the DataURL program or Janus Web Rules
*Your XML data is not in the proper format or is not well-formed

==Additional Capabilities==
You can add even more punch to your FusionCharts data, you can add a ''drill-down'' capability by adding a URL to the XML data for a particular Bar or Slice of a chart. You would need to add the ''link'' property to the ''set'' value for a bar or slice.

<set name='Jan' value='17400' link='n-DemoLinkPages/DemoLink1.html' color='AFD8F8' />

'''Note:''' The n- prefix to the link indicates that it is to open in a new window. Leave this off if you want to replace the active page.

Category:Tutorial

2010-10-13T15:34:40Z

Dessick: delete

Charting using Janus Web Server and FusionCharts Free

2010-10-13T15:32:23Z

Dessick: Add to category tutorial

[[Category:Tutorial]]
==Background==
You've created a beautiful web site, but the only thing missing is a way to easily add bar graphs, pie charts or other business graphics. Fortunately, there is an easy way to do this at little or no cost using FusionCharts Free from [http://www.fusioncharts.com/free InfoSoft Global Ltd.] '''FusionCharts Free''' supports a generous number of business charts. Of course for more sophisticated options there is a more full featured version, for which you must pay a license fee.

==Chart Types Supported==
'''FusionCharts Free''' supports the following chart types:
*Bar Charts (2D and 3D)
*Pie Charts (2D and 3D)
*Doughnut Charts
*Line Charts
*Area Charts
*Stacked Charts
*Combination (Line & Bar) Charts
*Candlestick Charts
*Funnel Charts
*Gantt Charts

There are 22 different charts, which are rendered as Adobe Flash (.swf) files in the browser using JavaScript.

==Getting Started==
The first step in using Fusion Charts is of course downloading the source. This can be found on the [http://www.fusioncharts.com/free FusionCharts Free] web site. Once you have downloaded the JavaScript files, you will need to upload them to a Model 204 file. The easiest way to do this is to use the Sirius FTP capability. (See the Sirius Janus Sockets Manual, Chapter 12). If you do not have Janus Sockets, you can use HTTP PUT or a Mainframe FTP package to get the files to your machine and subsequently to a Model 204 Procedure file. '''Hint''': when you upload the files to your Janus Web Procedure file, upload them as ''binary'' files to avoid the dreaded "Code Page" issue. You must then add a Janus Web Rule to send them to the browser as "binary". The data that will populate your chart will come from an XML file that is either created by another program specified by a URL, or coded directly in the charting program.

==Using FusionCharts Free with Janus Web==
Once you have uploaded your FusionCharts Free JavaScript files to your server and added appropriate Janus Web Rules to send them to the browser, you are ready to code a Janus Web application to chart your data. You might also need to add a web rule to use Adobe Flash for .swf files. I find the "Data URL" method (see FusionCharts Free documentation) the easiest. In your Janus Web Program, you would add a container for your chart and the JavaScript code to call the chart-type JavaScrip and also your data URL. '''Note:''' If your data URL program is being passed parameters, the URL must be URL Encoded using the Sirius URLENCODE function or the JavaScript "escape()" method.

In the <head> of your HTML file you will need to include the following:

<SCRIPT LANGUAGE="Javascript" SRC="/FusionCharts/FusionCharts.js"></SCRIPT>

You may need to modify the path name depending on your Janus Web Rules.

You will then add the following code in the <body> of the HTML:
<nowiki>...
HTML
<div id="chart1div">This text is replaced by the chart
</div>
<script type="text/javascript">
var chart1 = new FusionCharts("Pie2D.swf", "ChId1", "600", "400", "0", "0");
//To pass parameters, URLEncode the dataURL. Use escape() in JavaScript
chart1.setDataURL(escape("Data.URL?id=1&subId=2"));
chart1.render("chart1div");
</script>
END HTML
...</nowiki>

Assuming you have coded up everything properly, the FusionCharts Column2D.swf JavaScript will call the Data.URL User Language program which will return an XML file properly formatted for creating a FusionCharts 2D Column Chart. Here is an example of a Column2D XML File:

<graph caption='Pie Chart' decimalPrecision='0' showPercentageValues='0' showNames='1' numberPrefix='$' showValues='1' showPercentageInLabel='0' pieYScale='45' pieBorderAlpha='100' pieRadius='100' animation='0' shadowXShift='4' shadowYShift='4' shadowAlpha='40' pieFillAlpha='95' pieBorderColor='FFFFFF'>
<set value='25' name='Item A' color='AFD8F8'/>
<set value='17' name='Item B' color='F6BD0F'/>
<set value='23' name='Item C' color='8BBA00' isSliced='1'/>
<set value='65' name='Item D' color='A66EDD'/>
<set value='22' name='Item E' color='F984A1'/>
</graph>

[[File:XML_2DPie1.gif|frame|alt=Sample 2D Pie Chart|Sample 2D Pie Chart]]

==Debugging==
If you see the dreaded JavaScript Error at the bottom of the page, it could be caused by one of the following:
*You actually made an error typing your JavaScript. ''Remember JavaScript is case sensitive.''
*There is a problem with your Janus Web Rules. Check '''SIRSCAN''' and look for Janus Web Rule problems
*There is a problem with the DataURL program or Janus Web Rules
*Your XML data is not in the proper format or is not well-formed

==Additional Capabilities==
You can add even more punch to your FusionCharts data, you can add a ''drill-down'' capability by adding a URL to the XML data for a particular Bar or Slice of a chart. You would need to add the ''link'' property to the ''set'' value for a bar or slice.

<set name='Jan' value='17400' link='n-DemoLinkPages/DemoLink1.html' color='AFD8F8' />

'''Note:''' The n- prefix to the link indicates that it is to open in a new window. Leave this off if you want to replace the active page.

Charting using Janus Web Server and FusionCharts Free

2010-10-13T15:31:10Z

Dessick: Initial Edit

==Background==
You've created a beautiful web site, but the only thing missing is a way to easily add bar graphs, pie charts or other business graphics. Fortunately, there is an easy way to do this at little or no cost using FusionCharts Free from [http://www.fusioncharts.com/free InfoSoft Global Ltd.] '''FusionCharts Free''' supports a generous number of business charts. Of course for more sophisticated options there is a more full featured version, for which you must pay a license fee.

==Chart Types Supported==
'''FusionCharts Free''' supports the following chart types:
*Bar Charts (2D and 3D)
*Pie Charts (2D and 3D)
*Doughnut Charts
*Line Charts
*Area Charts
*Stacked Charts
*Combination (Line & Bar) Charts
*Candlestick Charts
*Funnel Charts
*Gantt Charts

There are 22 different charts, which are rendered as Adobe Flash (.swf) files in the browser using JavaScript.

==Getting Started==
The first step in using Fusion Charts is of course downloading the source. This can be found on the [http://www.fusioncharts.com/free FusionCharts Free] web site. Once you have downloaded the JavaScript files, you will need to upload them to a Model 204 file. The easiest way to do this is to use the Sirius FTP capability. (See the Sirius Janus Sockets Manual, Chapter 12). If you do not have Janus Sockets, you can use HTTP PUT or a Mainframe FTP package to get the files to your machine and subsequently to a Model 204 Procedure file. '''Hint''': when you upload the files to your Janus Web Procedure file, upload them as ''binary'' files to avoid the dreaded "Code Page" issue. You must then add a Janus Web Rule to send them to the browser as "binary". The data that will populate your chart will come from an XML file that is either created by another program specified by a URL, or coded directly in the charting program.

==Using FusionCharts Free with Janus Web==
Once you have uploaded your FusionCharts Free JavaScript files to your server and added appropriate Janus Web Rules to send them to the browser, you are ready to code a Janus Web application to chart your data. You might also need to add a web rule to use Adobe Flash for .swf files. I find the "Data URL" method (see FusionCharts Free documentation) the easiest. In your Janus Web Program, you would add a container for your chart and the JavaScript code to call the chart-type JavaScrip and also your data URL. '''Note:''' If your data URL program is being passed parameters, the URL must be URL Encoded using the Sirius URLENCODE function or the JavaScript "escape()" method.

In the <head> of your HTML file you will need to include the following:

<SCRIPT LANGUAGE="Javascript" SRC="/FusionCharts/FusionCharts.js"></SCRIPT>

You may need to modify the path name depending on your Janus Web Rules.

You will then add the following code in the <body> of the HTML:
<nowiki>...
HTML
<div id="chart1div">This text is replaced by the chart
</div>
<script type="text/javascript">
var chart1 = new FusionCharts("Pie2D.swf", "ChId1", "600", "400", "0", "0");
//To pass parameters, URLEncode the dataURL. Use escape() in JavaScript
chart1.setDataURL(escape("Data.URL?id=1&subId=2"));
chart1.render("chart1div");
</script>
END HTML
...</nowiki>

Assuming you have coded up everything properly, the FusionCharts Column2D.swf JavaScript will call the Data.URL User Language program which will return an XML file properly formatted for creating a FusionCharts 2D Column Chart. Here is an example of a Column2D XML File:

<graph caption='Pie Chart' decimalPrecision='0' showPercentageValues='0' showNames='1' numberPrefix='$' showValues='1' showPercentageInLabel='0' pieYScale='45' pieBorderAlpha='100' pieRadius='100' animation='0' shadowXShift='4' shadowYShift='4' shadowAlpha='40' pieFillAlpha='95' pieBorderColor='FFFFFF'>
<set value='25' name='Item A' color='AFD8F8'/>
<set value='17' name='Item B' color='F6BD0F'/>
<set value='23' name='Item C' color='8BBA00' isSliced='1'/>
<set value='65' name='Item D' color='A66EDD'/>
<set value='22' name='Item E' color='F984A1'/>
</graph>

[[File:XML_2DPie1.gif|frame|alt=Sample 2D Pie Chart|Sample 2D Pie Chart]]

==Debugging==
If you see the dreaded JavaScript Error at the bottom of the page, it could be caused by one of the following:
*You actually made an error typing your JavaScript. ''Remember JavaScript is case sensitive.''
*There is a problem with your Janus Web Rules. Check '''SIRSCAN''' and look for Janus Web Rule problems
*There is a problem with the DataURL program or Janus Web Rules
*Your XML data is not in the proper format or is not well-formed

==Additional Capabilities==
You can add even more punch to your FusionCharts data, you can add a ''drill-down'' capability by adding a URL to the XML data for a particular Bar or Slice of a chart. You would need to add the ''link'' property to the ''set'' value for a bar or slice.

<set name='Jan' value='17400' link='n-DemoLinkPages/DemoLink1.html' color='AFD8F8' />

'''Note:''' The n- prefix to the link indicates that it is to open in a new window. Leave this off if you want to replace the active page.

SRSMAXUS parameter

2010-10-05T20:06:04Z

Dessick:

<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>System manager resettable
<dt>Related products
<dd>[[Janus Web Server]]
<dt>Introduced
<dd>Before [[Sirius Mods]] 6.7
</dl>
This parameter sets the maximum number of saved record sets per user. This limit is a
per-userid limit, and it applies even if the userid is being used from multiple web
browsers. The default for SRSMAXUS of 0 means that there is no per-user limit for
saved record sets.

SRSMAXUS can be used to ensure that a single user, either as the result of a
programming error or simply through running frequent queries, does not monopolize the
saved record set facility.

The SRSMAXUS parameter has no effect unless [[SRSMAX parameter|SRSMAX]] is
set to a non-zero value.

[[Category:System Parameters]]
[[Category:Parameters]]

SRSMAXUS parameter

2010-10-05T20:05:22Z

Dessick:

<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>System manager resettable
<dt>Related products
<dd>[[Janus Web Server]]
<dt>Introduced
<dd>Before [[Sirius Mods]] 6.7
</dl>
This parameter sets the maximum number of saved record sets per user. This limit is a
per-userid limit, and it applies even if the userid is being used from multiple web
browsers. The default for SRSMAXUS of 0 means that there is no per-user limit for
saved record sets.

SRSMAXUS can be used to ensure that a single user, either as the result of a
programming error or simply through running frequent queries, does not monopolize the
saved record set facility.

The SRSMAXUS parameter has no effect unless [[SRSMAX Parameter|SRSMAX]] is
set to a non-zero value.

[[Category:System Parameters]]
[[Category:Parameters]]

SIRTUNE parameter

2010-10-05T19:59:47Z

Dessick:

<dl>
<dt>Default value
<dd>X'01'
<dt>Parameter type
<dd>System
<dt>Where set
<dd>EXEC card PARM value under MVS, M204 CMS command parameters under CMS
<dt>Related products
<dd>[[SirTune]]
<dt>Introduced
<dd> [[Sirius Mods]] 6.9
</dl>
This is a bitmask parameter that controls SirTune. SirTune is integrated with the Sirius
Mods as of Sirius Mods version 6.9. The meaning of the bits are:

<dl>
<dt>X'01' <dd>Enables the SirTune data collector. When this is set, the SirTune data collector
will look for the SIRTUNED dataset. If present, the SirTune data collector will
be enabled, and compilation and sample data will be collected to SIRTUNED.
In addition, the MODIFY/SMSG commands will also be available.
</dl>
The default value of X'01' for SIRTUNE causes the SirTune data collector to be enabled
'''if possible'''. Things that prevent it from being enabled are the absence of the
SIRTUNED dataset and the fact that Model 204 is running under an older SirTune load
module. In the first case, the SirTune data collector silently disables itself. In the
second case, it issues an informational message and then disables itself. In no case
should the default value for SIRTUNE prevent an Online from coming up, so there is
probably little reason to set this parameter.

Setting this parameter in an Online not authorized for SirTune will have no effect.
For more information about the SirTune data collector, see the [[SirTune Reference Manual]].

[[Category:System Parameters]]
[[Category:Parameters]]

SIRTUNE parameter

2010-10-05T17:19:23Z

Dessick:

<dl>
<dt>Default value
<dd>X'01'
<dt>Parameter type
<dd>System
<dt>Where set
<dd>EXEC card PARM value under MVS, M204CMS command parameters under CMS
<dt>Related products
<dd>[[SirTune]]
<dt>Introduced
<dd> [[Sirius Mods]] 6.9
</dl>
This is a bitmask parameter that controls SirTune. SirTune is integrated with the Sirius
Mods as of Sirius Mods version 6.9. The meaning of the bits are:

<dl>
<dt>X'01' <dd>Enables the SirTune data collector. When this is set, the SirTune data collector
will look for the SIRTUNED dataset. If present, the SirTune data collector will
be enabled, and compilation and sample data will be collected to SIRTUNED.
In addition, the MODIFY/SMSG commands will also be available.
</dl>
The default value of X'01' for SIRTUNE causes the SirTune data collector to be enabled
'''if possible'''. Things that prevent it from being enabled are the absence of the
SIRTUNED dataset and the fact that Model 204 is running under an older SirTune load
module. In the first case, the SirTune data collector silently disables itself. In the
second case, it issues an informational message and then disables itself. In no case
should the default value for SIRTUNE prevent an Online from coming up, so there is
probably little reason to set this parameter.

Setting this parameter in an Online not authorized for SirTune will have no effect.
For more information about the SirTune data collector, see the [[SirTune Reference Manual]].

[[Category:System Parameters]]
[[Category:Parameters]]

SOCKMAX parameter

2010-10-05T17:14:42Z

Dessick: initial edit

<dl>
<dt>Default value
<dd>10
<dt>Parameter type
<dd>System
<dt>Where set
<dd>User 0 CCAIN parameters
<dt>Related products
<dd>[[Janus Sockets]]
<dt>Introduced
<dd>Before [[Sirius Mods]] 6.7
</dl>
This parameter specifies the maximum total number of sockets a user may use at any
time (one of these is reserved for the server socket number 1, whether the user is a
server socket program or not). The default for SOCKMAX is 10, which allows 9 client
socket numbers to be in use.
The minimum value for SOCKMAX is 2, and the maximum value is 88.
SOCKMAX affects storage allocation for each user who is using any sockets — each
such user has allocated 6 + (6 * SOCKMAX) bytes (rounded up to a multiple of 4). In
addition, each open socket over a Janus Sockets port increases the storage requirement
by 960 bytes plus the value of the [[IBSIZE]] and [[OBSIZE]] parameters.
Note the distinction between this Model 204 system parameter and [[SOCKPMAX]].

[[Category:System Parameters]]
[[Category:Parameters]]

SPANSIZE parameter

2010-10-05T17:12:31Z

Dessick: initial edit

<dl>
<dt>Default value
<dd>90
<dt>Parameter type
<dd>System
<dt>Where set
<dd>User 0 CCAIN parameters
<dt>Related products
<dd>All
<dt>Introduced
<dd>Before [[Sirius Mods]] 6.7
</dl>
This is a numeric parameter that must have a value between 10 and 100. It sets the
default value for the range in number of years that two-digit years are allowed to
encompass. By limiting the valid range of two digit years, protection is provided against
misinterpretation of ambiguous two-digit dates such as, for example, ‘10’ being
misinterpreted as 1910, when in fact, it means 2010.

This setting affects many $functions, and it can be overridden by many of these same
$functions. For more information about how SCANSIZE is used, see the [[Sir2000 User Language Tools Reference Manual]] or the [[Sir2000 Field Migration Facility Reference Manual]].

[[Category:System Parameters]]
[[Category:Parameters]]

SRSDEFTO parameter

2010-10-05T16:52:57Z

Dessick: initial edit from parameter reference

<dl>
<dt>Default value
<dd>900
<dt>Parameter type
<dd>System
<dt>Where set
<dd>System manager resettable
<dt>Related products
<dd>[[Janus Web Server]]
<dt>Introduced
<dd>Before [[Sirius Mods]] 6.7
</dl>
This parameter sets the default timeout value (in seconds) to be used for saved record
sets if none is specified on the $web_save_recset function. If SRSDEFTO exceeds
[[SRSMAXTO]], [[SRSMAXTO]] will effectively act as the default
timeout value.

The default for SRSDEFTO is 900, which means 15 minutes. Setting SRSDEFTO to 0
means no record sets will be saved unless an explicit timeout is specified in the
$web_save_recset function.

The SRSDEFTO parameter has no effect unless [[SRSMAX]] is
set to a non-zero value.

Valid values for SRSDEFTO are between 0 and 2592000 (720 hours).

[[Category:System Parameters]]
[[Category:Parameters]]

SRSMAX parameter

2010-10-05T16:50:34Z

Dessick: Initial edit from parameter reference

<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>User 0 CCAIN parameters
<dt>Related products
<dd>[[Janus Web Server]]
<dt>Introduced
<dd>Before [[Sirius Mods]] 6.7
</dl>
This parameter sets the maximum number of total saved record sets in the system.
SRSMAX defaults to 0, and it must be set to a positive value less than or equal to
16777215 to allow use of the saved record set feature of Janus Web Server. If
SRSMAX is 0, $web_save_recset will never save a record set.

The number of record sets that can actually be saved at a given time might be
somewhat less than the SRSMAX value if many of the saved record sets are associated
with groups with large numbers of members.

The saved record set feature will use approximately 64*SRSMAX bytes of virtual
storage.

[[Category:System Parameters]]
[[Category:Parameters]]

SRSMAXTO parameter

2010-10-05T16:48:02Z

Dessick: Initial edit from system parameters reference

<dl>
<dt>Default value
<dd>3600
<dt>Parameter type
<dd>System
<dt>Where set
<dd>System manager resettable
<dt>Related products
<dd>[[Janus Web Server]]
<dt>Introduced
<dd>Before [[Sirius Mods]] 6.7
</dl>
This parameter sets the maximum length of time (in seconds) that a saved record set
can be saved without being referenced. The actual maximum length of time a record set
will be saved can be set in the $web_save_recset function, but it will be set to
SRSMAXTO if the $web_save_recset value exceeds SRSMAXTO. Similarly, if a
timeout is not specified on the $web_save_recset, the timeout value is derived from
[[SRSDEFTO]] but if [[SRSDEFTO]] is greater than
SRSMAXTO, SRSMAXTO will be used as the timeout.

The default for SRSMAXTO of 3600 means a maximum timeout of one hour.

Resetting SRSMAXTO to 0 temporarily disables the saved record set facility, and all
enqueues associated with saved record sets are freed. This can be useful in clearing up
an enqueuing problem caused by a saved record set.

Resetting SRSMAXTO will dynamically adjust the timeout for any record sets saved with
a higher timeout value. So if there is a saved record set with a timeout of 1800 seconds
when SRSMAXTO is reset to 300, that record set's timeout is updated to 300. If that
record set had been saved more than 300 seconds before the reset, it would be
immediately freed.

The SRSMAXTO parameter has no effect unless [[SRSMAX]] is
set to a non-zero value.

Valid values for SRSMAXTO are between 0 and 2592000 (720 hours).
[[Category:System Parameters]]
[[Category:Parameters]]

SRSMAXUS parameter

2010-10-05T16:43:05Z

Dessick: initial edit from system parameters reference

<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>System manager resettable
<dt>Related products
<dd>[[Janus Web Server]]
<dt>Introduced
<dd>Before [[Sirius Mods]] 6.7
</dl>
This parameter sets the maximum number of saved record sets per user. This limit is a
per-userid limit, and it applies even if the userid is being used from multiple web
browsers. The default for SRSMAXUS of 0 means that there is no per-user limit for
saved record sets.

SRSMAXUS can be used to ensure that a single user, either as the result of a
programming error or simply through running frequent queries, does not monopolize the
saved record set facility.

The SRSMAXUS parameter has no effect unless [[SRSMAX]] is
set to a non-zero value.

[[Category:System Parameters]]
[[Category:Parameters]]

TCPSERV parameter

2010-10-05T16:40:03Z

Dessick: initial edit from system parameters reference

<dl>
<dt>Default value
<dd>'TCPIP'
<dt>Parameter type
<dd>System
<dt>Where set
<dd>User 0 CCAIN parameters
<dt>Related products
<dd>All
<dt>Introduced
<dd>Before [[Sirius Mods]] 6.7
</dl>
This parameter indicates the name of the TCP/IP server address space (MVS) or virtual
machine (CMS).

[[Category:System Parameters]]
[[Category:Parameters]]

TCPSUBSY parameter

2010-10-05T16:37:10Z

Dessick:

<dl>
<dt>Default value
<dd>'    ' (four blanks)
<dt>Parameter type
<dd>System
<dt>Where set
<dd>User 0 CCAIN parameters
<dt>Related products
<dd>All
<dt>Introduced
<dd>Before [[Sirius Mods]] 6.7
</dl>
This parameter indicates the subsystem name to be used by Janus. It only has meaning
when using the MVS IUCV interface (a deprecated API), and the Interlink interface. The
default of blank causes the default value of ‘VMCF’ to be used in the unlikely event that
MVS IUCV is being used and ‘ACSS’ for Interlink.

[[Category:System Parameters]]
[[Category:Parameters]]

TCPSUBSY parameter

2010-10-05T16:36:15Z

Dessick: initial edit

<dl>
<dt>Default value
<dd>' ' (four blanks)
<dt>Parameter type
<dd>System
<dt>Where set
<dd>User 0 CCAIN parameters
<dt>Related products
<dd>All
<dt>Introduced
<dd>Before [[Sirius Mods]] 6.7
</dl>
This parameter indicates the subsystem name to be used by Janus. It only has meaning
when using the MVS IUCV interface (a deprecated API), and the Interlink interface. The
default of blank causes the default value of ‘VMCF’ to be used in the unlikely event that
MVS IUCV is being used and ‘ACSS’ for Interlink.

[[Category:System Parameters]]
[[Category:Parameters]]

TCPTYPE parameter

2010-10-05T16:34:00Z

Dessick: Initial edit from system parameters reference

<dl>
<dt>Default value
<dd>UNKNOWN
<dt>Parameter type
<dd>System
<dt>Where set
<dd>User 0 CCAIN parameters
<dt>Related products
<dd>All
<dt>Introduced
<dd>Before [[Sirius Mods]] 6.7
</dl>
This parameter specifies the type of TCP/IP network to which Model 204 is connected.
Generally, you can leave this parameter at its default value and let Janus automatically
detect the type of TCP/IP you have on your machine.

If you specify type IBM, Janus detects and sets the type of IBM interface it will use:

* Under CMS, this is always IUCV.
* Under MVS, Janus will select the IBM interface in the following order: BPX (Unix System Services), HPNS, then IUCV.
* If multiple types are installed, Janus will select the interface in the following order for MVS: BPX, HPNS, IUCV, Interlink, then KNET. For CMS the order is IUCV, then KNET.

You can always override auto-detection by explicitly supplying a TCPTYPE parameter.
The only reason to do this would be if you have multiple TCP/IP stacks installed and you
want to force use of the non-preferred stack.

The valid TCPTYPE values are:
<dl>
<dt>IBM <dd>Specifies IBM TCP/IP. This means to auto-detect the “best” IBM TCP/IP interface. For CMS, this is always IUCV. For MVS, Janus will look for BPX, HPNS, then IUCV.
<dt>BPX <dd>Specifies IBM BPX (Unix System Services) (MVS only).
<dt>HPNS <dd>Specifies IBM HPNS (High Performance Native Sockets) (MVS only). Note that despite its name, HPNS's performance is not nearly as good as BPX's.
<dt>INTERLNK <dd>Specifies InterLink TCP/IP (MVS only).
<dt>CSI <dd>Specifies Connectivity Systems TCP/IP (VSE only).
</dl>
Most of the communication with the TCP/IP address space is accomplished via a PST.
Because of this, you may need to increase NSUBTKS by 1 before using Janus.

[[Category:System Parameters]]
[[Category:Parameters]]

TNDEV parameter

2010-10-05T16:27:04Z

Dessick: Inital edit from system parameters manual

<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>User 0 CCAIN parameters
<dt>Related products
<dd>Janus Sockets
<dt>Introduced
<dd>[[Sirius Mods]] 6.9
</dl>
This parameter specifies the IODEV number to be used for Janus Telnet Server
connections. When a connection is made to a Janus Telnet Server, the IODEV number
of the SDAEMON thread is dynamically switched to the TNDEV value. If TNDEV is not
set to a non-zero value, no Janus Telnet Server (TNSERV) ports can be defined, and no
telnet connections can be made directly to Model 204.

The value of the TNDEV parameter must be an odd number between 1 and 53, and it
must be different from the SDAEMDEV system parameter.

'''Note:''' No IODEV cards are allowed for the TNDEV IODEV number — the IODEV
number can only be used dynamically by Janus Telnet Server.

The recommended setting for TNDEV is 21, an IODEV number no longer in use by
Model 204.

For more information about the Janus Telnet Server, see the'' Janus Sockets Reference
Manual''.

[[Category:System Parameters]]
[[Category:Parameters]]

WEBAUDIT parameter

2010-10-05T16:22:16Z

Dessick:

<dl>
<dt>Default value
<dd>X'00000000'
<dt>Parameter type
<dd>System
<dt>Where set
<dd>User 0 CCAIN parameters
<dt>Related products
<dd>All
<dt>Introduced
<dd> [[Sirius Mods]] 6.9
</dl>
This parameter makes it possible to reduce the quantity of useless audit trail data
associated with Janus Web Server applications. The WEBAUDIT parameter is a
collection of bits that, when set, reduce the quantity of data sent to the Model 204 journal
or make it possible to reduce this quantity. The bits in WEBAUDIT are:

<dl>
<dt>X'00000001'
<dd>Allow NOAUDIT and NOAUDITW keywords on MSGCTL command.
Specifying '''MSGCTL msg_no NOAUDIT''' prevents msg_no from ever
going to the audit trail, while '''MSGCTL msg_no NOAUDITW''' prevents
msg_no from going to the audit trail, if issued on a J''anus Web Server''
thread.

<dt>X'00000001'
<dd>Suppress APSY load since-last statistics for Janus Web Server threads.
The resource usage associated with the APSY load such as CPU,
DKPRs, disk I/Os, etc. will be included in the EVAL since-last statistics
for the request. Since APSY load resource utilization is typically
extremely minor relative to request evaluation, APSY load since-last
statistics tend to be fairly useless.

<dt>X'00000004'
<dd>Suppress APSY load since-last statistics for all threads. The resource
usage associated with the APSY load such as CPU, DKPRs, disk I/Os,
etc. will be included in the EVAL since-last statistics for the request.
Since APSY load resource utilization is typically extremely minor relative
to request evaluation, APSY load since-last statistics tend to be fairly
useless.

<dt>X'00000008'
<dd>Suppress “NO USERID” logout messages (M204.0353) for Janus Web
Server threads. These messages are sometimes issued before a user
logon, even though there is no userid logged on the thread, so they are
singularly useless.

<dt>X'00000010'
<dd>Suppress “NO USERID” logout messages (M204.0353) for all threads.
These messages are sometimes issued before a user logon, even
though there is no userid logged on the thread, so they are singularly
useless.

The MSGCTL NOAUDIT enhancement should be used with caution. Preventing certain
messages from going to the journal could make diagnosing certain problems more
difficult. It is not, however, a new capability or one that is only available to Janus Web
Server customers. Even without Janus Web Server, it is possible to issue a MSGCTL
command for any message with the AUDITRK parameter. It is then possible to
suppress RK messages from going to the audit trail by making sure the X'20' bit is not
set in SYSOPT. The one unfortunate side-effect of this technique is that it also
suppresses RK messages that one might actually want to go to the audit trail, but this
can be overcome by MSGCTL'ing these messages to NOAUDITRK. Thanks to Warren
Kring for this technique.

In any case, the MSGCTL NOAUDIT and NOAUDITW provide a neater and more finegrained
way of reducing audit trail messages for Janus Web Server or other threads.
Some good candidates for MSGCTL NOAUDIT or NOAUDITW are:
<dl>
<dt>M204.0099<dd> MINIMUM SERVSIZE FOR THESE TABLES = ...
<dt>M204.0131<dd> (Checkpoint completed or timed out messages)
<dt>M204.0353<dd> (login/logout message that is essentially a shortened version of '''M204.0352''' that also gets logged to the journal)
<dt>M204.0608 <dd>FILE CLOSED: ...
<dt>M204.0619 <dd>GROUP FILE OPENED: ...
<dt>M204.0620 <dd>FILE file OPENED (-- NO UPDATES ALLOWED)
<dt>M204.0621 <dd>(Informational message indicating recovery status of file being opened)
<dt>M204.0622 <dd>(Informational message indicating the last update applied by the last rollforward for a file being opened)
<dt>M204.0821 <dd>GROUP FILE CLOSED: ...
<dt>M204.0858 <dd>GROUP group OPENED (-- NO UPDATES ALLOWED)
<dt>M204.1203 <dd>FILE file WAS LAST UPDATED ON ...
<dt>M204.1238 <dd>(Informational message indicating the time the file was last recovered.)

Under Sirius Mods version 6.9 and later, there is also a NOAUD parameter on Janus
port definitions that allow even more information to be suppressed from the audit trail on
a port basis.
</dl>
[[Category:User Parameters]]
[[Category:Parameters]]

[[Category:System Parameters]]
[[Category:Parameters]]

WEBAUDIT parameter

2010-10-05T16:20:36Z

Dessick:

<dl>
<dt>Default value
<dd>X'00000000'
<dt>Parameter type
<dd>System
<dt>Where set
<dd>User 0 CCAIN parameters
<dt>Related products
<dd>All
<dt>Introduced
<dd> [[Sirius Mods]] 6.9
</dl>
This parameter makes it possible to reduce the quantity of useless audit trail data
associated with Janus Web Server applications. The WEBAUDIT parameter is a
collection of bits that, when set, reduce the quantity of data sent to the Model 204 journal
or make it possible to reduce this quantity. The bits in WEBAUDIT are:

<dl>
<dt>X'00000001'
<dd>Allow NOAUDIT and NOAUDITW keywords on MSGCTL command.
Specifying '''MSGCTL msg_no NOAUDIT''' prevents msg_no from ever
going to the audit trail, while '''MSGCTL msg_no NOAUDITW''' prevents
msg_no from going to the audit trail, if issued on a J''anus Web Server''
thread.

<dt>X'00000001'
<dd>Suppress APSY load since-last statistics for Janus Web Server threads.
The resource usage associated with the APSY load such as CPU,
DKPRs, disk I/Os, etc. will be included in the EVAL since-last statistics
for the request. Since APSY load resource utilization is typically
extremely minor relative to request evaluation, APSY load since-last
statistics tend to be fairly useless.

<dt>X'00000004'
<dd>Suppress APSY load since-last statistics for all threads. The resource
usage associated with the APSY load such as CPU, DKPRs, disk I/Os,
etc. will be included in the EVAL since-last statistics for the request.
Since APSY load resource utilization is typically extremely minor relative
to request evaluation, APSY load since-last statistics tend to be fairly
useless.

<dt>X'00000008'
<dd>Suppress “NO USERID” logout messages (M204.0353) for Janus Web
Server threads. These messages are sometimes issued before a user
logon, even though there is no userid logged on the thread, so they are
singularly useless.

<dt>X'00000010'
<dd>Suppress “NO USERID” logout messages (M204.0353) for all threads.
These messages are sometimes issued before a user logon, even
though there is no userid logged on the thread, so they are singularly
useless.

The MSGCTL NOAUDIT enhancement should be used with caution. Preventing certain
messages from going to the journal could make diagnosing certain problems more
difficult. It is not, however, a new capability or one that is only available to Janus Web
Server customers. Even without Janus Web Server, it is possible to issue a MSGCTL
command for any message with the AUDITRK parameter. It is then possible to
suppress RK messages from going to the audit trail by making sure the X'20' bit is not
set in SYSOPT. The one unfortunate side-effect of this technique is that it also
suppresses RK messages that one might actually want to go to the audit trail, but this
can be overcome by MSGCTL'ing these messages to NOAUDITRK. Thanks to Warren
Kring for this technique.

In any case, the MSGCTL NOAUDIT and NOAUDITW provide a neater and more finegrained
way of reducing audit trail messages for Janus Web Server or other threads.
Some good candidates for MSGCTL NOAUDIT or NOAUDITW are:
<dl>
<dt>M204.0099<dd> MINIMUM SERVSIZE FOR THESE TABLES = ...
<dt>M204.0131<dd> (Checkpoint completed or timed out messages)
<dt>M204.0353<dd> (login/logout message that is essentially a shortened version of
<dt>M204.0352<dd> that also gets logged to the journal)
<dt>M204.0608 <dd>FILE CLOSED: ...
<dt>M204.0619 <dd>GROUP FILE OPENED: ...
<dt>M204.0620 <dd>FILE file OPENED (-- NO UPDATES ALLOWED)
<dt>M204.0621 <dd>(Informational message indicating recovery status of file being opened)
<dt>M204.0622 <dd>(Informational message indicating the last update applied by the last rollforward for a file being opened)
<dt>M204.0821 <dd>GROUP FILE CLOSED: ...
<dt>M204.0858 <dd>GROUP group OPENED (-- NO UPDATES ALLOWED)
<dt>M204.1203 <dd>FILE file WAS LAST UPDATED ON ...
<dt>M204.1238 <dd>(Informational message indicating the time the file was last recovered.)

Under Sirius Mods version 6.9 and later, there is also a NOAUD parameter on Janus
port definitions that allow even more information to be suppressed from the audit trail on
a port basis.
</dl>
[[Category:User Parameters]]
[[Category:Parameters]]

[[Category:System Parameters]]
[[Category:Parameters]]

WEBAUDIT parameter

2010-10-05T16:19:35Z

Dessick: Inital Edit from parameters reference

<dl>
<dt>Default value
<dd>X'00000000'
<dt>Parameter type
<dd>System
<dt>Where set
<dd>User 0 CCAIN parameters
<dt>Related products
<dd>All
<dt>Introduced
<dd>Before [[Sirius Mods]] 6.9
</dl>
This parameter makes it possible to reduce the quantity of useless audit trail data
associated with Janus Web Server applications. The WEBAUDIT parameter is a
collection of bits that, when set, reduce the quantity of data sent to the Model 204 journal
or make it possible to reduce this quantity. The bits in WEBAUDIT are:

<dl>
<dt>X'00000001'
<dd>Allow NOAUDIT and NOAUDITW keywords on MSGCTL command.
Specifying '''MSGCTL msg_no NOAUDIT''' prevents msg_no from ever
going to the audit trail, while '''MSGCTL msg_no NOAUDITW''' prevents
msg_no from going to the audit trail, if issued on a J''anus Web Server''
thread.

<dt>X'00000001'
<dd>Suppress APSY load since-last statistics for Janus Web Server threads.
The resource usage associated with the APSY load such as CPU,
DKPRs, disk I/Os, etc. will be included in the EVAL since-last statistics
for the request. Since APSY load resource utilization is typically
extremely minor relative to request evaluation, APSY load since-last
statistics tend to be fairly useless.

<dt>X'00000004'
<dd>Suppress APSY load since-last statistics for all threads. The resource
usage associated with the APSY load such as CPU, DKPRs, disk I/Os,
etc. will be included in the EVAL since-last statistics for the request.
Since APSY load resource utilization is typically extremely minor relative
to request evaluation, APSY load since-last statistics tend to be fairly
useless.

<dt>X'00000008'
<dd>Suppress “NO USERID” logout messages (M204.0353) for Janus Web
Server threads. These messages are sometimes issued before a user
logon, even though there is no userid logged on the thread, so they are
singularly useless.

<dt>X'00000010'
<dd>Suppress “NO USERID” logout messages (M204.0353) for all threads.
These messages are sometimes issued before a user logon, even
though there is no userid logged on the thread, so they are singularly
useless.

The MSGCTL NOAUDIT enhancement should be used with caution. Preventing certain
messages from going to the journal could make diagnosing certain problems more
difficult. It is not, however, a new capability or one that is only available to Janus Web
Server customers. Even without Janus Web Server, it is possible to issue a MSGCTL
command for any message with the AUDITRK parameter. It is then possible to
suppress RK messages from going to the audit trail by making sure the X'20' bit is not
set in SYSOPT. The one unfortunate side-effect of this technique is that it also
suppresses RK messages that one might actually want to go to the audit trail, but this
can be overcome by MSGCTL'ing these messages to NOAUDITRK. Thanks to Warren
Kring for this technique.

In any case, the MSGCTL NOAUDIT and NOAUDITW provide a neater and more finegrained
way of reducing audit trail messages for Janus Web Server or other threads.
Some good candidates for MSGCTL NOAUDIT or NOAUDITW are:
<dl>
<dt>M204.0099<dd> MINIMUM SERVSIZE FOR THESE TABLES = ...
<dt>M204.0131<dd> (Checkpoint completed or timed out messages)
<dt>M204.0353<dd> (login/logout message that is essentially a shortened version of
<dt>M204.0352<dd> that also gets logged to the journal)
<dt>M204.0608 <dd>FILE CLOSED: ...
<dt>M204.0619 <dd>GROUP FILE OPENED: ...
<dt>M204.0620 <dd>FILE file OPENED (-- NO UPDATES ALLOWED)
<dt>M204.0621 <dd>(Informational message indicating recovery status of file being opened)
<dt>M204.0622 <dd>(Informational message indicating the last update applied by the last rollforward for a file being opened)
<dt>M204.0821 <dd>GROUP FILE CLOSED: ...
<dt>M204.0858 <dd>GROUP group OPENED (-- NO UPDATES ALLOWED)
<dt>M204.1203 <dd>FILE file WAS LAST UPDATED ON ...
<dt>M204.1238 <dd>(Informational message indicating the time the file was last recovered.)

Under Sirius Mods version 6.9 and later, there is also a NOAUD parameter on Janus
port definitions that allow even more information to be suppressed from the audit trail on
a port basis.
</dl>
[[Category:User Parameters]]
[[Category:Parameters]]

[[Category:System Parameters]]
[[Category:Parameters]]

WEBOPT parameter

2010-10-05T16:10:43Z

Dessick: Intial edit from Janus Web Server Manual

<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>User 0 resettable
<dt>Related products
<dd>Janus Web Server
<dt>Introduced
<dd>Before [[Sirius Mods]] 6.5
</dl>
The WEBOPT parameter is a standard Model 204 bitmask-type parameter introduced in
Sirius Mods version 6.5. The X'01' setting causes RACF calls to be performed in a
special RACF subtask.

In cases where Janus Web Server is deployed and RACF handles login validation, the
RACF call load for login-protected web pages can get very high. Since these calls often
involve synchronous I/Os that stop the Model 204 main task, they are generally not very
good for Model 204 performance. However, if you set the WEBOPT system parameter
to X'01', these calls are done in a subtask, reducing their impact on Online performance
dramatically.
<dl>
<dt>X'01'
<dd>RACF Calls are performed in a special RACF subtask.
</dl>

[[Category:System Parameters]]
[[Category:Parameters]]

SIREDIT parameter

2010-10-05T15:55:09Z

Dessick: Added complete text from command reference

<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>User
<dt>Where set
<dd>User resettable
<dt>Related products
<dd>All
<dt>Introduced
<dd>Before [[Sirius Mods]] 6.7
</dl>
This is a bitmask parameter that controls various enhancements to the Model 204 fullscreen
editor. The meaning of the bits are:
<dl>
<dt>X'01'
<dd>Switch to *LOWER mode upon entry to the editor, and revert to prior setting
upon exit. This allows command mode to work in *UPPER mode so that
commands are automatically uppercased, while allowing the editor to work in
mixed-case mode.

Since most Model 204 commands take entirely uppercase input, *UPPER mode
is almost always preferable in command mode. On the other hand, most
modern User Language programs use mixed case, so *LOWER mode is
preferable inside the editor. The SIREDIT X'01' bit allows one to get the best of
both worlds with no effort.

This bit has no effect if the user is already in *LOWER mode on entry to the
editor.
<dt>X'02'
<dd> Change the LINEND character for the current procedure to carriage return
(X'0D'). This allows procedures to include semicolons as data, and it also
makes it easier to edit a procedure that has been uploaded from an HTML
generator.
<dt>X'04'
<dd>Always force the current 3270 Mod 2 behavior (24 lines by eighty characters),
even if the editor is invoked by a thread using a Mod 5 session. This bit takes
precedence over the following bit.
<dt>X'08'
<dd>Allow Mod 5 sessions in DBCS environments. Ordinarily the widescreen (Mod
5) support is disabled under DBCS environments. When this bit is set, even
DBCS sessions are eligible for widescreen support.
<dt>X'10'
<dd>Provide case-insensitive locate in non-DBCS environments. Thus, the editor
command will locate both of the following lines, regardless of the setting of *LOWER/*UPPER or the SIREDIT X'01' bit:

This is sometimes hard to find due to mixed
case, while “this is” is all lower case.

<dt>X'20'
<dd>Provide case-insensitive search strings for the replace command, while still retaining the case as entered on the replacement string, assuming that either *LOWER is in effect or the X'01' bit of SIREDIT is set. Under these conditions, and using the text from the previous example, the command:

r/this is/This Is/* all

will change occurrences on both lines, resulting in:

This Is sometimes hard to find due to mixed
case, while “This Is” is all lower case.

In addition to the SIREDIT parameter, the Sirius Mods provide some additional fullscreen
editor commands.
</dl>
[[Category:User Parameters]]
[[Category:Parameters]]

SIREDIT parameter

2010-10-05T15:46:50Z

Dessick:

SIREDIT parameter

2010-10-05T15:44:50Z

Dessick: Create Stub

<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>User
<dt>Where set
<dd>User resettable
<dt>Related products
<dd>All
<dt>Introduced
<dd>Before [[Sirius Mods]] 6.7
</dl>

SIREDIT parameter

2010-10-05T15:43:52Z

Dessick: Created page with "<dl> <dt>Default value <dd>0 <dt>Parameter type <dd>System <dt>Where set <dd>System manager resettable <dt>Related products <dd>A;; <dt>Introduced <dd>Before Sirius Mods 6.7 ..."

<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>System manager resettable
<dt>Related products
<dd>A;;
<dt>Introduced
<dd>Before [[Sirius Mods]] 6.7
</dl>

Text and Html statements

2010-10-05T15:26:54Z

Dessick: Copy of the chapter in Janus Soap Manual with formatting changes for Wiki

==The '''HTML''' or '''TEXT''' statement==
The '''Html''' (or '''Text''') statement in User Language is a general purpose alternative to a
series of Print statements for producing a fair amount of literal data. Primarily for use
with Janus Web Server (hence the name Html), it is available with many Sirius
products. It is most useful when PRINT output is captured or directed by some means.
It is also quite useful for populating a StringList with a large amount of mostly constant
text. This latter capability is provided by the To option of the '''Html/Text''' statement.

In this section, “HTML block” refers to either the '''Html''' or '''Text''' block.

The Html block can be used to produce print output of largely literal or static data. For
example, sending output to a browser with Janus Web Server often requires a significant
quantity of static text for HTML directives. Rather than placing this static data inside
quotes in a Print statement, the Html block will automatically assign text as print output.
Any Model 204 expression, including simple %variable values or $function invocations,
can be placed inside an Html block, as long as it is enclosed inside the expression start
and end characters. The default start and end characters are the curly brackets ( { )
and ( } ).

The following is an example of an '''Html''' statement specification:

HTML
<form method="POST" action="processform">
<br>
Last name: <input type="text"
name="lname" value="{%LNAME}">
</form>
END HTML

The syntax of the '''Html''' and '''Text''' blocks is shown below:

HTML [options]
body
block_end_line

or

TEXT [options]
body
block_end_line

''options'', ''body'', and ''block_end_line'' are discussed below.

The components of the Html or Text block are discussed in the following sections. The Html (or Text) block can be used in contexts other than the production of a web page. For example, it can be used:
* To store lines in a temporary procedure or sequential dataset, using the USE command
* To populate a StringList, using the To option on the Html/Text statement
* To populate a $list, using the $LIST_CAPTURE function
* To send lines over a Janus Sockets connection, using the $SOCK_CAPTURE function
* To prepare output processed by some other program, when the output is created by something like a BATCH2 or RCL connection to Model 204 Here are some advantages of the Html/Text block:
* User Language is visually close to the output.
* Literal text does not need to be enclosed in apostrophes.
* The Print keyword is not necessary.
* Any valid Model 204 expression can be included inside an Html block, not just literals, %variables, fieldnames, $functions, and a few other constructs.
* The With and And keywords are not needed between expressions.
* Apostrophes do not need to be doubled, as in:

PRINT <nowiki>'Just say ''No'''</nowiki>

The following is an example of an Html block using JavaScript to illustrate applications of the '''Html/Text''' options:

HTML NOCONT EXPRS '!{' EXPRE '}!'
<nowiki><html>
<head>
<title>My Javascript Page</title>
</head>
!{$SIR_DATE('Wkd Mon DD YYYY HH:MI:SS')}!
<br>
<body>
<script>

</script>
</body>
</html>
END HTML</nowiki>

'''Html''' statement options used in this example:
* Nocont is used to turn off continuations signified by trailing dashes. In the JavaScript, dashes are used in an input line that prevents browsers without JavaScript from displaying script as literal output.
* Exprs and Expre let you use characters other than the curly brackets ( { } ) to demarcate expressions. The curly bracket characters are necessary in JavaScript.

New in Sirius Mods version 6.0, the Html block is available to any customer who owns any of the following products:
* ''Fast/Unload User Language Interface''
*'' Janus SOAP''
* ''Janus Sockets''
* ''Janus Web Server''
* ''Sirius Functions''

The '''Html''' block is also available if the Limited Janus Web Server capability is available.
==Options: Html or Text block options==
The various options for an Html or Text block are introduced after the Html or Text
keyword. They are described in the following subsections.
===Data, Print, Audit, or Trace===
These keywords indicate that the Html block consists of only the text that follows the
keyword on the logical line: that is, there is no End Html statement to end the block.

Prior to Sirius Mods version 7.2, only the Data keyword had this effect, and the Print,
Audit, and Trace keywords did not exist.

Any Html statement keywords that appear after a Data, Print, Audit, or Trace keyword
are processed not as keywords but simply as text. If you want to specify keywords in
addition to a Data, Print, Audit, or Trace keyword, they must appear before Data, Print,
Audit, or Trace to be treated as a keyword.

All other Html block processing, including expression processing, is performed on the
line as if it were inside an Html block. The exception is Nodummy processing, because
dummy string replacement is performed before the Html statement is parsed.

====Data or Print====
Either of these keywords can be thought of as providing a single-line
Html/Text statement which can still be much easier to type and read
than a User Language PRINT statement, as in:

HTML DATA Don't need to worry about apostrophes
TEXT PRINT {%I} + {%J} = {%I + %J}

The following is an equivalent alternative to the second statement in the
preceding example.

PrintText {%I} + {%J} = {%I + %J}

The '''PrintText''' statement has the same effect as a Text Print statement.
The '''PrintText''' keyword is simply a merging and reordering of ''Text
Print'' to emphasize the principle action. The lone difference between
PrintText and Text Print is that PrintText cannot be used if you want to
include other Html/Text options, as in:

text noexpr print The set is {2, 3, 5, 8, 13, ...}

The Data keyword is available in ''Sirius Mods 6.2'' and later. The Print
and PrintText keywords are available in ''Sirius Mods 7.2'' and later.

====Audit====
This keyword provides a single-line Html/Text statement that functions
like a User Language AUDIT statement, that is, routing subsequent text
to the audit trail.

For example, this statement directs the text content to the audit trail:

text audit It ({$time}) was the best of times

The following is an equivalent alternative to the preceding example.

AuditText It ({$time}) was the best of times

As with the PrintText keyword above, the AuditText statement has the
same effect as a Text Audit statement, except it cannot be used if you
want to include additional Html/Text options.

The Audit keyword is available in ''Sirius Mods 7.2'' and later. The
AuditText keyword is available as of ''Sirius Mods 7.2''.
====Trace====
This keyword provides a single-line Html/Text statement that is the
same as a User Language TRACE statement, that is, routing
subsequent text to the trace destination (which may be the audit trail,
print device, or CCATEMP trace table, or a combination of them).
For example, this statement directs the text content by default to the
audit trail:

text trace This day ({$date}) is unlike any other

The following is an equivalent alternative to the preceding example.

TraceText This day ({$date}) is unlike any other

As with the PrintText and AudiText keywords above, the TraceText
statement has the same effect as a Text Trace statement, except it
cannot be used if you want to include additional Html/Text options.
The Trace and TraceText keywords are available as of ''Sirius Mods 7.2.''
The Trace statement is described in detail in the SirFact Reference
Manual.

====Ent_print====
The Ent_print keyword overrides the current $ENT_PRINT setting for character entity
translation over the Html block. Ent_print must be followed by one of these keywords:
<table>
<tr><td>'''Off'''</td><td>No character entity translation will occur over the Html block.</td></tr>
<tr><td>'''On'''</td><td>All data printed by the Html statement will undergo character entity translation.</td></tr>
<tr><td>'''Var'''</td><td>Only the results of expressions will undergo character entity translation.</td></tr></table>

Character entity translation is the process of converting a single character that might be
problematic in certain contexts to a more verbose but non-problematic equivalent. For
example, if a “less than” sign ('''<''') appears in HTML text, it should typically be represented
as <nowiki>“<”</nowiki> to prevent an HTML processor from mistakenly interpreting it as the start of an
HTML tag.

When entity translation is performed, the default translations are “&” to <nowiki>“&”</nowiki>, “<” to
<nowiki>“<”</nowiki> and the double quotation mark character (") to <nowiki>“"”</nowiki>. These defaults should
be sufficient for most HTML and XML applications (though XML might also require
translation of the single quotation mark character (') to <nowiki>“'”</nowiki> if attributes are
enclosed in single quotation marks), but they can be modified with the $ENT_TAB
function.

The Ent_print keyword is a compile-time option that affects only what is inside the Html
block and that is not affected by evaluation time setting of $ENT_PRINT, even within the
Html block. If no Ent_print keyword is present on the Html statement, character entity
translation is controlled by the evaluation-time $ENT_PRINT setting.
Automatic character entity translation and the Ent_print keyword on the Html/Text
statement are only available in ''Sirius Mods 6.2'' and later.
====LiteralsToTemp====
The LiteralsToTempt option indicates that the literal data in the statement is stored in
CCATEMP rather than STBL, avoiding excessive demands on STBL space. Designed
for a Text statement with an unusually large amount of literal data, this is an alternative
to setting the X'01' bit of the SIRCOMP user parameter (which performs the same
function).
====Nocom or Nocomments====
The Nocomments (abbreviated Nocom) option indicates that lines beginning with an
asterisk (*) are not comment lines. For example:

<nowiki> HTML NOCOM
* This line will go to the output
END HTML</nowiki>
====Nocont or Nocontinuations====
The Nocontinuations (abbreviated Nocont) option causes trailing dashes to cease
being treated as line continuations. For example, the following statement will cause the
output to appear on two separate lines:

<nowiki> HTML NOCONT
English: B-
Social Studies: C
END HTML</nowiki>

====Nodum or Nodummy====
The Nodummy (abbreviated Nodum) option stops dummy string substitution. For
example, the following statement will cause the literal string ?&W to be output without
global variable substitution:

HTML NODUM
Hello, ?&W
END HTML
====Noell or Noellipses====
With the Noellipses (abbreviated Noell) option, a trailing ellipsis (...) is not treated as
a concatenation operator. For example:

HTML NOELL
These lines are not joined...
They will appear on different lines.
END HTML
====Noexpr or Noexpressions====
If you do not want expression substitution, specify Noexpr or Noexpressions. For
example:
HTML NOEXPR
{This will be sent directly to output}
END HTML
====Raw====
The Raw option acts as Nocom, Nocont, Nodum, Noell, and Noexpr all at once.
====Noend====
The Noend option eliminates the block end line. Thus, the block will terminate at the
end of the procedure. For example:
PROC FOO
HTML NOEND
Now we are in HTML.
END HTML
Still in HTML.
END PROC

====Exprs or Exprstart====
The Exprstart (abbreviated Exprs) option specifies a string, up to three characters
long, that begins an expression within the block body. The default is a left curly brace
( { ). For example:

HTML EXPRS go EXPRE stp
The answer is go8*9stp
HTML END

It is probably best to use start and end sequences that are not likely to occur in the literal
text in the Html/Text block and that clearly demarcate expressions from literal text. The
go and stp in the example above are actually not very good choices.

If the expression start string occurs in the input text, you can “double” the expression
start and end strings, instead of using the Exprs and Expre options. For example:

<nowiki>HTML
<script>
{{alert("User error")}}
<script>
END HTML</nowiki>

An alternative way to handle the curly braces in the script above is shown in the Html block example at the beginning of this chapter: that is, specifying '''HTML EXPRS '!{'EXPRE '}!'''' and''' !{alert("User error")!'''}.

'''Note:''' If you use multiple special characters to demarcate expressions, you are advised
to enclose those characters in single quotation marks (as above) in your Exprs and
Expre specifications. Otherwise, multiple-character combinations involving certain
special characters (including these six, for example: = ¬ ( ) < > ) cause M204.0580
errors.
====Expre or Exprend====
The Exprend (abbreviated Expre) option specifies a string that ends an expression
within the block body. The default is a right curly brace ( } ).
====End====
To set your own block_end_line, you can use the End option. If the text of the line you
are specifying contains spaces, enclose it in single quotation marks, as in:
END 'END TEXT BLOCK'
The default block_end_line value is '''End Html''' (for the Html block) or '''End Text''' (for the
Text block).
====To %stringList | Audit | Print | Trace====
The To option lets you direct the contents of the Html or Text block to a StringList or to
the destinations associated with the User Language statements Audit, Print, or Trace.
To %stringlist
Here is how Text To populates a StringList with some names:
%jumps is object stringList
...
%jumps = new
text to %jumps
Axel
Flip
Lutz
Salchow
Toe Loop
Wally
end text

There are many advantages to using Html To or Text To over a plain Html statement
wih $LIST_CAPTURE:
* $LIST_CAPTURE or an equivalent is not available for StringLists.
* Because Html To does not go through generic Print processing, it has a somewhat more efficient processing path, that is, it uses less CPU.
* Because Html To does not go through generic Print processing, the generated quads take somewhat less space.
* An Html To block does not affect the current $LIST_CAPTURE setting, so it eliminates the need to worry about saving and restoring the $LIST_CAPTURE setting.
* A To option on an Html statement is simply less and cleaner code than an Html statement inside a $LIST_CAPTURE bracket.
* If an expression inside an Html To block invokes a User Language method, and that method does a Print statement, the output of that Print statement does not end up on the StringList target of the Html statement. Inside a $LIST_CAPTURE bracket, the output of such a Print statement ends up on the $LIST_CAPTURE's target $list.

The To option of the Html/Text statement appends to the target StringList, so it does not
instantiate the stringList if it is null. In fact, a null StringList target for an Html To results
in a null-pointer request-cancelling error.

Even if the ultimate target of an Html/Text statement is a plain $list, the Html To can still
be used to gain some of the benefits of this structure without much extra code by using
the Stringlist object MoveFromId and MoveToId methods:

%htmlList is object stringList
%list is float
...
%list = $listNew
...
%htmlList = new
%htmlList:modeFromId(%list)
text to %htmlList
This gets added to the $list.
end text
%htmlList:modeToId(%list)

'''To Audit, To Print, To Trace'''

These options direct the contents of an Html or Text block or line to the destinations
associated with the User Language statements Audit, Print, or Trace. Respectively
these destinations are the journal/audit trail, the current print output device, or the trace
destination (which may be the audit trail, print device, or CCATEMP trace table, or a
combination of them).

For example, the following statement directs the Text block content to the audit trail:

text to audit
Now ({$time}) is the time for all good men
to come to the aid of their company.
end text

To direct a single line of output, you can use the Data keyword (''Data, Print, Audit, or
Trace'') as in the following:

text to audit Data It ({$time}) was the best of times

Or, simpler, you can use the Audit keyword like this:

text Audit It ({$time}) was the best of times
====Body: Html or Text block body====
Each line of an Html or Text block, up to the block_end_line, creates a line of literal
output, with the following substitutions:
<table border="1">
<tr><td>Expressions</td><td> An expression is begun by a left brace ( { ) or a user-defined string specified with the Exprs option, and it is ended by a right brace ( } ) or a user-defined string specified with the Expre option. Text within the expression is evaluated as if it were the right-hand side of a User Language assignment; that value is produced, rather than literal output.</td></tr>
<tr><td>Dummy strings</td><td> Normally, as in other Model 204 input, dummy strings are substituted under the control of the SUB parameter. This can be suppressed with the Nodummy option, which may be useful if your block contains strings like “what the heck??!!”.</td></tr>
<tr><td>Continuation</td><td> Continuation allows text from multiple lines to be printed on one line by adding a hyphen (-) to all preceding lines in the block. All spacing and indentation following the hyphen is ignored. This option works
inside an expression.</td></tr>
<tr><td>Ellipses</td><td> Ellipses allow text from multiple command lines to be printed on one line by adding three dots (...) to all preceding command lines. Leading spaces will be included. This option will not work inside an expression.</td></tr>
<tr><td>Indentation</td><td> Except for continuation lines, the output of a line is indented by as many spaces as the input is indented relative to the Html or Text statement that begins the block.</td></tr></table>
====block_end_line: Html or Text block end====
By default, the line that ends an Html or Text block is End Html for an Html block, or it
is End Text for a Text block. You can specify your own end line with the End option,
as described above in “End”.
====Printing of expression results====
Model 204 expressions enclosed in the expression start and end characters are printed
as if the result of the expression were placed literally in the place of the expression in the
HTML block. For example, Text Print {$date} produces a result like 08-02-29.
====Character entity substitution====
Under ''Sirius Mods 6.2'' and later, the result of the expression might undergo character
entity substitution under control of the $ENT_PRINT setting or the Ent_print parameter
on the Html/Text statement. An expression can explicitly override the default
$ENT_PRINT and Ent_print processing by immediately following the expression start
character(s) with one of the following special characters:
<table border="1">
<tr><td>'''&'''</td><td> Perform character entity substitution regardless of the current $ENT_PRINT
setting and the Ent_print setting on the Html statement.</td></tr>
<tr><td>'''!''' </td><td>Do not perform character entity substitution, regardless of the current
$ENT_PRINT setting and the Ent_print setting on the Html statement.</td></tr>
<tr><td>'''*'''</td><td>Do not print the results of the expression. This can be useful if embedding a $function that itself prints output, such as $LIST_PRINT or $WEB_SEL, or a $function that simply sets some environmental parameter (such as $WEB_SET or $RESETN) whose return value should not be displayed.</td></tr></table>

'''Note:''' The asterisk (*) suppresses the printing of the return code but not the
output from a $LIST_PRINT or $WEB_SEL function.

In the following example, character entity substitution is explicitly suppressed for the
contents of %FONT and explicitly forced for %COMMENT, and the return code from
$LIST_PRINT is suppressed:
<nowiki>HTML
{!%FONT}This is in a fancy font</font>
<input type="text" name="comment" value="{&%COMMENT}">
<br>And here's some stuff<br>
{*$LIST_PRINT(%LIST)}
END HTML
</nowiki>
====The {~} directive====
The special expression {~} directs the compiler to replace this expression with the literal
chartacter content of the next expression appearing on the same line. So PrintText
{~} {$date} produces '''$date 08-02-29'''. The evaluation of the expression following
{~} is carried out as usual.
===Table Usage===
While the '''Html/Text''' statement can provide a convenient typing shorthand relative to a
host of Print statements, and it can make code considerably more readable, it does not
necessarily use any less table space than the comparable Print statements.

Under ''Sirius Mods version 6.6'' and later, however, table space can be saved with the
Html/Text statement, as follows:

* By using the To clause and sending the Html/Text statement output directly to a StringList, the amount of QTBL space used is reduced.
* If the X'01' bit is set in the SIRCOMP user parameter when a program is compiled, string literals are saved in CCATEMP rather than STBL. Since Html/Text statements often have a large quantity of literal text, they can use a lot of STBL space, so the STBL space savings of the SIRCOMP X'01' bit can be great.

The drawback to having string literals in CCATEMP rather than STBL is that the access path to the data is somewhat longer, that is, slightly more CPU is required to
access it. When the Html/Text statement uses a To clause, the extra overhead of
CCATEMP data access is reduced, because Html/Text To processing keeps the
CCATEMP pages holding literal data open over as many literals as possible.

Furthermore, for pre-compiled APSY procedures, the literals in CCATEMP do not
need to be APSY loaded, and they are shared among all users of a procedure.
Finally, if a user with a large number of Html/Text statement literals is serverswapped,
there is less data to server-swap if literals are kept in CCATEMP
(although, the data in CCATEMP does take buffer pool space and might require
CCATEMP I/O).

So there is probably no good general rule of thumb regarding whether the SIRCOMP
X'01' bit should be set. Probably, unless a site is struggling with server size problems, it
is best and simplest to just keep the literals in STBL.

Text and Html statements

2010-10-05T15:20:53Z

Dessick:

'''Bold text'''==The '''HTML''' or '''TEXT''' statement==
The '''Html''' (or '''Text''') statement in User Language is a general purpose alternative to a
series of Print statements for producing a fair amount of literal data. Primarily for use
with Janus Web Server (hence the name Html), it is available with many Sirius
products. It is most useful when PRINT output is captured or directed by some means.
It is also quite useful for populating a StringList with a large amount of mostly constant
text. This latter capability is provided by the To option of the Html/Text statement.

In this section, “HTML block” refers to either the Html or Text block.

The Html block can be used to produce print output of largely literal or static data. For
example, sending output to a browser with Janus Web Server often requires a significant
quantity of static text for HTML directives. Rather than placing this static data inside
quotes in a Print statement, the Html block will automatically assign text as print output.
Any Model 204 expression, including simple %variable values or $function invocations,
can be placed inside an Html block, as long as it is enclosed inside the expression start
and end characters. The default start and end characters are the curly brackets ( { )
and ( } ).

The following is an example of an '''Html''' statement specification:

HTML
<form method="POST" action="processform">
<br>
Last name: <input type="text"
name="lname" value="{%LNAME}">
</form>
END HTML

The syntax of the '''Html''' and '''Text''' blocks is shown below:

HTML [options]
body
block_end_line

or

TEXT [options]
body
block_end_line

''options'', ''body'', and ''block_end_line'' are discussed below.

The components of the Html or Text block are discussed in the following sections. The Html (or Text) block can be used in contexts other than the production of a web page. For example, it can be used:
* To store lines in a temporary procedure or sequential dataset, using the USE command
* To populate a StringList, using the To option on the Html/Text statement
* To populate a $list, using the $LIST_CAPTURE function
* To send lines over a Janus Sockets connection, using the $SOCK_CAPTURE function
* To prepare output processed by some other program, when the output is created by something like a BATCH2 or RCL connection to Model 204 Here are some advantages of the Html/Text block:
* User Language is visually close to the output.
* Literal text does not need to be enclosed in apostrophes.
* The Print keyword is not necessary.
* Any valid Model 204 expression can be included inside an Html block, not just literals, %variables, fieldnames, $functions, and a few other constructs.
* The With and And keywords are not needed between expressions.
* Apostrophes do not need to be doubled, as in:

PRINT <nowiki>'Just say ''No'''</nowiki>

The following is an example of an Html block using JavaScript to illustrate applications of the '''Html/Text''' options:

HTML NOCONT EXPRS '!{' EXPRE '}!'
<nowiki><html>
<head>
<title>My Javascript Page</title>
</head>
!{$SIR_DATE('Wkd Mon DD YYYY HH:MI:SS')}!
<br>
<body>
<script>

</script>
</body>
</html>
END HTML</nowiki>

'''Html''' statement options used in this example:
* Nocont is used to turn off continuations signified by trailing dashes. In the JavaScript, dashes are used in an input line that prevents browsers without JavaScript from displaying script as literal output.
* Exprs and Expre let you use characters other than the curly brackets ( { } ) to demarcate expressions. The curly bracket characters are necessary in JavaScript.

New in Sirius Mods version 6.0, the Html block is available to any customer who owns any of the following products:
* ''Fast/Unload User Language Interface''
*'' Janus SOAP''
* ''Janus Sockets''
* ''Janus Web Server''
* ''Sirius Functions''

The '''Html''' block is also available if the Limited Janus Web Server capability is available.
==Options: Html or Text block options==
The various options for an Html or Text block are introduced after the Html or Text
keyword. They are described in the following subsections.
===Data, Print, Audit, or Trace===
These keywords indicate that the Html block consists of only the text that follows the
keyword on the logical line: that is, there is no End Html statement to end the block.

Prior to Sirius Mods version 7.2, only the Data keyword had this effect, and the Print,
Audit, and Trace keywords did not exist.

Any Html statement keywords that appear after a Data, Print, Audit, or Trace keyword
are processed not as keywords but simply as text. If you want to specify keywords in
addition to a Data, Print, Audit, or Trace keyword, they must appear before Data, Print,
Audit, or Trace to be treated as a keyword.

All other Html block processing, including expression processing, is performed on the
line as if it were inside an Html block. The exception is Nodummy processing, because
dummy string replacement is performed before the Html statement is parsed.

====Data or Print====
Either of these keywords can be thought of as providing a single-line
Html/Text statement which can still be much easier to type and read
than a User Language PRINT statement, as in:

HTML DATA Don't need to worry about apostrophes
TEXT PRINT {%I} + {%J} = {%I + %J}

The following is an equivalent alternative to the second statement in the
preceding example.

PrintText {%I} + {%J} = {%I + %J}

The '''PrintText''' statement has the same effect as a Text Print statement.
The '''PrintText''' keyword is simply a merging and reordering of ''Text
Print'' to emphasize the principle action. The lone difference between
PrintText and Text Print is that PrintText cannot be used if you want to
include other Html/Text options, as in:

text noexpr print The set is {2, 3, 5, 8, 13, ...}

The Data keyword is available in ''Sirius Mods 6.2'' and later. The Print
and PrintText keywords are available in ''Sirius Mods 7.2'' and later.

====Audit====
This keyword provides a single-line Html/Text statement that functions
like a User Language AUDIT statement, that is, routing subsequent text
to the audit trail.

For example, this statement directs the text content to the audit trail:

text audit It ({$time}) was the best of times

The following is an equivalent alternative to the preceding example.

AuditText It ({$time}) was the best of times

As with the PrintText keyword above, the AuditText statement has the
same effect as a Text Audit statement, except it cannot be used if you
want to include additional Html/Text options.

The Audit keyword is available in ''Sirius Mods 7.2'' and later. The
AuditText keyword is available as of ''Sirius Mods 7.2''.
====Trace====
This keyword provides a single-line Html/Text statement that is the
same as a User Language TRACE statement, that is, routing
subsequent text to the trace destination (which may be the audit trail,
print device, or CCATEMP trace table, or a combination of them).
For example, this statement directs the text content by default to the
audit trail:

text trace This day ({$date}) is unlike any other

The following is an equivalent alternative to the preceding example.

TraceText This day ({$date}) is unlike any other

As with the PrintText and AudiText keywords above, the TraceText
statement has the same effect as a Text Trace statement, except it
cannot be used if you want to include additional Html/Text options.
The Trace and TraceText keywords are available as of ''Sirius Mods 7.2.''
The Trace statement is described in detail in the SirFact Reference
Manual.

====Ent_print====
The Ent_print keyword overrides the current $ENT_PRINT setting for character entity
translation over the Html block. Ent_print must be followed by one of these keywords:
<table>
<tr><td>'''Off'''</td><td>No character entity translation will occur over the Html block.</td></tr>
<tr><td>'''On'''</td><td>All data printed by the Html statement will undergo character entity translation.</td></tr>
<tr><td>'''Var'''</td><td>Only the results of expressions will undergo character entity translation.</td></tr></table>

Character entity translation is the process of converting a single character that might be
problematic in certain contexts to a more verbose but non-problematic equivalent. For
example, if a “less than” sign ('''<''') appears in HTML text, it should typically be represented
as <nowiki>“<”</nowiki> to prevent an HTML processor from mistakenly interpreting it as the start of an
HTML tag.

When entity translation is performed, the default translations are “&” to <nowiki>“&”</nowiki>, “<” to
<nowiki>“<”</nowiki> and the double quotation mark character (") to <nowiki>“"”</nowiki>. These defaults should
be sufficient for most HTML and XML applications (though XML might also require
translation of the single quotation mark character (') to <nowiki>“'”</nowiki> if attributes are
enclosed in single quotation marks), but they can be modified with the $ENT_TAB
function.

The Ent_print keyword is a compile-time option that affects only what is inside the Html
block and that is not affected by evaluation time setting of $ENT_PRINT, even within the
Html block. If no Ent_print keyword is present on the Html statement, character entity
translation is controlled by the evaluation-time $ENT_PRINT setting.
Automatic character entity translation and the Ent_print keyword on the Html/Text
statement are only available in ''Sirius Mods 6.2'' and later.
====LiteralsToTemp====
The LiteralsToTempt option indicates that the literal data in the statement is stored in
CCATEMP rather than STBL, avoiding excessive demands on STBL space. Designed
for a Text statement with an unusually large amount of literal data, this is an alternative
to setting the X'01' bit of the SIRCOMP user parameter (which performs the same
function).
====Nocom or Nocomments====
The Nocomments (abbreviated Nocom) option indicates that lines beginning with an
asterisk (*) are not comment lines. For example:

<nowiki> HTML NOCOM
* This line will go to the output
END HTML</nowiki>
====Nocont or Nocontinuations====
The Nocontinuations (abbreviated Nocont) option causes trailing dashes to cease
being treated as line continuations. For example, the following statement will cause the
output to appear on two separate lines:

<nowiki> HTML NOCONT
English: B-
Social Studies: C
END HTML</nowiki>

====Nodum or Nodummy====
The Nodummy (abbreviated Nodum) option stops dummy string substitution. For
example, the following statement will cause the literal string ?&W to be output without
global variable substitution:

HTML NODUM
Hello, ?&W
END HTML
====Noell or Noellipses====
With the Noellipses (abbreviated Noell) option, a trailing ellipsis (...) is not treated as
a concatenation operator. For example:

HTML NOELL
These lines are not joined...
They will appear on different lines.
END HTML
====Noexpr or Noexpressions====
If you do not want expression substitution, specify Noexpr or Noexpressions. For
example:
HTML NOEXPR
{This will be sent directly to output}
END HTML
====Raw====
The Raw option acts as Nocom, Nocont, Nodum, Noell, and Noexpr all at once.
====Noend====
The Noend option eliminates the block end line. Thus, the block will terminate at the
end of the procedure. For example:
PROC FOO
HTML NOEND
Now we are in HTML.
END HTML
Still in HTML.
END PROC

====Exprs or Exprstart====
The Exprstart (abbreviated Exprs) option specifies a string, up to three characters
long, that begins an expression within the block body. The default is a left curly brace
( { ). For example:

HTML EXPRS go EXPRE stp
The answer is go8*9stp
HTML END

It is probably best to use start and end sequences that are not likely to occur in the literal
text in the Html/Text block and that clearly demarcate expressions from literal text. The
go and stp in the example above are actually not very good choices.

If the expression start string occurs in the input text, you can “double” the expression
start and end strings, instead of using the Exprs and Expre options. For example:

<nowiki>HTML
<script>
{{alert("User error")}}
<script>
END HTML</nowiki>

An alternative way to handle the curly braces in the script above is shown in the Html block example at the beginning of this chapter: that is, specifying '''HTML EXPRS '!{'EXPRE '}!'''' and''' !{alert("User error")!'''}.

'''Note:''' If you use multiple special characters to demarcate expressions, you are advised
to enclose those characters in single quotation marks (as above) in your Exprs and
Expre specifications. Otherwise, multiple-character combinations involving certain
special characters (including these six, for example: = ¬ ( ) < > ) cause M204.0580
errors.
====Expre or Exprend====
The Exprend (abbreviated Expre) option specifies a string that ends an expression
within the block body. The default is a right curly brace ( } ).
====End====
To set your own block_end_line, you can use the End option. If the text of the line you
are specifying contains spaces, enclose it in single quotation marks, as in:
END 'END TEXT BLOCK'
The default block_end_line value is '''End Html''' (for the Html block) or '''End Text''' (for the
Text block).
====To %stringList | Audit | Print | Trace====
The To option lets you direct the contents of the Html or Text block to a StringList or to
the destinations associated with the User Language statements Audit, Print, or Trace.
To %stringlist
Here is how Text To populates a StringList with some names:
%jumps is object stringList
...
%jumps = new
text to %jumps
Axel
Flip
Lutz
Salchow
Toe Loop
Wally
end text

There are many advantages to using Html To or Text To over a plain Html statement
wih $LIST_CAPTURE:
* $LIST_CAPTURE or an equivalent is not available for StringLists.
* Because Html To does not go through generic Print processing, it has a somewhat more efficient processing path, that is, it uses less CPU.
* Because Html To does not go through generic Print processing, the generated quads take somewhat less space.
* An Html To block does not affect the current $LIST_CAPTURE setting, so it eliminates the need to worry about saving and restoring the $LIST_CAPTURE setting.
* A To option on an Html statement is simply less and cleaner code than an Html statement inside a $LIST_CAPTURE bracket.
* If an expression inside an Html To block invokes a User Language method, and that method does a Print statement, the output of that Print statement does not end up on the StringList target of the Html statement. Inside a $LIST_CAPTURE bracket, the output of such a Print statement ends up on the $LIST_CAPTURE's target $list.

The To option of the Html/Text statement appends to the target StringList, so it does not
instantiate the stringList if it is null. In fact, a null StringList target for an Html To results
in a null-pointer request-cancelling error.

Even if the ultimate target of an Html/Text statement is a plain $list, the Html To can still
be used to gain some of the benefits of this structure without much extra code by using
the Stringlist object MoveFromId and MoveToId methods:

%htmlList is object stringList
%list is float
...
%list = $listNew
...
%htmlList = new
%htmlList:modeFromId(%list)
text to %htmlList
This gets added to the $list.
end text
%htmlList:modeToId(%list)

'''To Audit, To Print, To Trace'''

These options direct the contents of an Html or Text block or line to the destinations
associated with the User Language statements Audit, Print, or Trace. Respectively
these destinations are the journal/audit trail, the current print output device, or the trace
destination (which may be the audit trail, print device, or CCATEMP trace table, or a
combination of them).

For example, the following statement directs the Text block content to the audit trail:

text to audit
Now ({$time}) is the time for all good men
to come to the aid of their company.
end text

To direct a single line of output, you can use the Data keyword (''Data, Print, Audit, or
Trace'') as in the following:

text to audit Data It ({$time}) was the best of times

Or, simpler, you can use the Audit keyword like this:

text Audit It ({$time}) was the best of times
====Body: Html or Text block body====
Each line of an Html or Text block, up to the block_end_line, creates a line of literal
output, with the following substitutions:
<table border="1">
<tr><td>Expressions</td><td> An expression is begun by a left brace ( { ) or a user-defined string specified with the Exprs option, and it is ended by a right brace ( } ) or a user-defined string specified with the Expre option. Text within the expression is evaluated as if it were the right-hand side of a User Language assignment; that value is produced, rather than literal output.</td></tr>
<tr><td>Dummy strings</td><td> Normally, as in other Model 204 input, dummy strings are substituted under the control of the SUB parameter. This can be suppressed with the Nodummy option, which may be useful if your block contains strings like “what the heck??!!”.</td></tr>
<tr><td>Continuation</td><td> Continuation allows text from multiple lines to be printed on one line by adding a hyphen (-) to all preceding lines in the block. All spacing and indentation following the hyphen is ignored. This option works
inside an expression.</td></tr>
<tr><td>Ellipses</td><td> Ellipses allow text from multiple command lines to be printed on one line by adding three dots (...) to all preceding command lines. Leading spaces will be included. This option will not work inside an expression.</td></tr>
<tr><td>Indentation</td><td> Except for continuation lines, the output of a line is indented by as many spaces as the input is indented relative to the Html or Text statement that begins the block.</td></tr></table>
====block_end_line: Html or Text block end====
By default, the line that ends an Html or Text block is End Html for an Html block, or it
is End Text for a Text block. You can specify your own end line with the End option,
as described above in “End”.
====Printing of expression results====
Model 204 expressions enclosed in the expression start and end characters are printed
as if the result of the expression were placed literally in the place of the expression in the
HTML block. For example, Text Print {$date} produces a result like 08-02-29.
====Character entity substitution====
Under ''Sirius Mods 6.2'' and later, the result of the expression might undergo character
entity substitution under control of the $ENT_PRINT setting or the Ent_print parameter
on the Html/Text statement. An expression can explicitly override the default
$ENT_PRINT and Ent_print processing by immediately following the expression start
character(s) with one of the following special characters:
<table border="1">
<tr><td>'''&'''</td><td> Perform character entity substitution regardless of the current $ENT_PRINT
setting and the Ent_print setting on the Html statement.</td></tr>
<tr><td>'''!''' </td><td>Do not perform character entity substitution, regardless of the current
$ENT_PRINT setting and the Ent_print setting on the Html statement.</td></tr>
<tr><td>'''*'''</td><td>Do not print the results of the expression. This can be useful if embedding a $function that itself prints output, such as $LIST_PRINT or $WEB_SEL, or a $function that simply sets some environmental parameter (such as $WEB_SET or $RESETN) whose return value should not be displayed.</td></tr></table>

'''Note:''' The asterisk (*) suppresses the printing of the return code but not the
output from a $LIST_PRINT or $WEB_SEL function.

In the following example, character entity substitution is explicitly suppressed for the
contents of %FONT and explicitly forced for %COMMENT, and the return code from
$LIST_PRINT is suppressed:
<nowiki>HTML
{!%FONT}This is in a fancy font</font>
<input type="text" name="comment" value="{&%COMMENT}">
<br>And here's some stuff<br>
{*$LIST_PRINT(%LIST)}
END HTML
</nowiki>
====The {~} directive====
The special expression {~} directs the compiler to replace this expression with the literal
chartacter content of the next expression appearing on the same line. So PrintText
{~} {$date} produces '''$date 08-02-29'''. The evaluation of the expression following
{~} is carried out as usual.

Text and Html statements

2010-10-05T14:58:20Z

Dessick: Created page with "==The '''HTML''' or '''TEXT''' statement== The '''Html''' (or '''Text''') statement in User Language is a general purpose alternative to a series of Print statements for producin..."

Category:Tutorial

2010-10-04T19:07:08Z

Dessick:

[[Category:Charting using Janus Web Server and FusionCharts Free]]
==Background==
You've created a beautiful web site, but the only thing missing is a way to easily add bar graphs, pie charts or other business graphics. Fortunately, there is an easy way to do this at little or no cost using FusionCharts Free from [http://www.fusioncharts.com/free InfoSoft Global Ltd.] '''FusionCharts Free''' supports a generous number of business charts. Of course for more sophisticated options there is a more full featured version, for which you must pay a license fee.

==Chart Types Supported==
'''FusionCharts Free''' supports the following chart types:
*Bar Charts (2D and 3D)
*Pie Charts (2D and 3D)
*Doughnut Charts
*Line Charts
*Area Charts
*Stacked Charts
*Combination (Line & Bar) Charts
*Candlestick Charts
*Funnel Charts
*Gantt Charts

There are 22 different charts, which are rendered as Adobe Flash (.swf) files in the browser using JavaScript.

==Getting Started==
The first step in using Fusion Charts is of course downloading the source. This can be found on the [http://www.fusioncharts.com/free FusionCharts Free] web site. Once you have downloaded the JavaScript files, you will need to upload them to a Model 204 file. The easiest way to do this is to use the Sirius FTP capability. (See the Sirius Janus Sockets Manual, Chapter 12). If you do not have Janus Sockets, you can use HTTP PUT or a Mainframe FTP package to get the files to your machine and subsequently to a Model 204 Procedure file. '''Hint''': when you upload the files to your Janus Web Procedure file, upload them as ''binary'' files to avoid the dreaded "Code Page" issue. You must then add a Janus Web Rule to send them to the browser as "binary". The data that will populate your chart will come from an XML file that is either created by another program specified by a URL, or coded directly in the charting program.

==Using FusionCharts Free with Janus Web==
Once you have uploaded your FusionCharts Free JavaScript files to your server and added appropriate Janus Web Rules to send them to the browser, you are ready to code a Janus Web application to chart your data. You might also need to add a web rule to use Adobe Flash for .swf files. I find the "Data URL" method (see FusionCharts Free documentation) the easiest. In your Janus Web Program, you would add a container for your chart and the JavaScript code to call the chart-type JavaScrip and also your data URL. '''Note:''' If your data URL program is being passed parameters, the URL must be URL Encoded using the Sirius URLENCODE function or the JavaScript "escape()" method.

In the <head> of your HTML file you will need to include the following:

<SCRIPT LANGUAGE="Javascript" SRC="/FusionCharts/FusionCharts.js"></SCRIPT>

You may need to modify the path name depending on your Janus Web Rules.

You will then add the following code in the <body> of the HTML:
<nowiki>...
HTML
<div id="chart1div">This text is replaced by the chart
</div>
<script type="text/javascript">
var chart1 = new FusionCharts("Pie2D.swf", "ChId1", "600", "400", "0", "0");
//To pass parameters, URLEncode the dataURL. Use escape() in JavaScript
chart1.setDataURL(escape("Data.URL?id=1&subId=2"));
chart1.render("chart1div");
</script>
END HTML
...</nowiki>

Assuming you have coded up everything properly, the FusionCharts Column2D.swf JavaScript will call the Data.URL User Language program which will return an XML file properly formatted for creating a FusionCharts 2D Column Chart. Here is an example of a Column2D XML File:

<graph caption='Pie Chart' decimalPrecision='0' showPercentageValues='0' showNames='1' numberPrefix='$' showValues='1' showPercentageInLabel='0' pieYScale='45' pieBorderAlpha='100' pieRadius='100' animation='0' shadowXShift='4' shadowYShift='4' shadowAlpha='40' pieFillAlpha='95' pieBorderColor='FFFFFF'>
<set value='25' name='Item A' color='AFD8F8'/>
<set value='17' name='Item B' color='F6BD0F'/>
<set value='23' name='Item C' color='8BBA00' isSliced='1'/>
<set value='65' name='Item D' color='A66EDD'/>
<set value='22' name='Item E' color='F984A1'/>
</graph>

[[File:XML_2DPie1.gif|frame|alt=Sample 2D Pie Chart|Sample 2D Pie Chart]]

==Debugging==
If you see the dreaded JavaScript Error at the bottom of the page, it could be caused by one of the following:
*You actually made an error typing your JavaScript. ''Remember JavaScript is case sensitive.''
*There is a problem with your Janus Web Rules. Check '''SIRSCAN''' and look for Janus Web Rule problems
*There is a problem with the DataURL program or Janus Web Rules
*Your XML data is not in the proper format or is not well-formed

==Additional Capabilities==
You can add even more punch to your FusionCharts data, you can add a ''drill-down'' capability by adding a URL to the XML data for a particular Bar or Slice of a chart. You would need to add the ''link'' property to the ''set'' value for a bar or slice.

<set name='Jan' value='17400' link='n-DemoLinkPages/DemoLink1.html' color='AFD8F8' />

'''Note:''' The n- prefix to the link indicates that it is to open in a new window. Leave this off if you want to replace the active page.

Category:Tutorial

2010-10-04T17:08:50Z

Dessick: Added sample chart image

[[Category:Charting using Janus Web Server and FusionCharts Free]]
==Background==
You've created a beautiful web site, but the only thing missing is a way to easily add bar graphs, pie charts or other business graphics. Fortunately, there is an easy way to do this at little or no cost using FusionCharts Free from [http://www.fusioncharts.com/free InfoSoft Global Ltd.] '''FusionCharts Free''' supports a generous number of business charts. Of course for more sophisticated options there is a more full featured version, for which you must pay a license fee.

==Chart Types Supported==
'''FusionCharts Free''' supports the following chart types:
*Bar Charts (2D and 3D)
*Pie Charts (2D and 3D)
*Doughnut Charts
*Line Charts
*Area Charts
*Stacked Charts
*Combination (Line & Bar) Charts
*Candlestick Charts
*Funnel Charts
*Gantt Charts

There are 22 different charts, which are rendered as Adobe Flash (.swf) files in the browser using JavaScript.

==Getting Started==
The first step in using Fusion Charts is of course downloading the source. This can be found on the [http://www.fusioncharts.com/free FusionCharts Free] web site. '''Hint''': when you upload the files to your Janus Web Procedure file, upload them as ''binary'' files to avoid the dreaded "Code Page" issue. You must then ad a Janus Web Rule to send them to the browser as "binary". The data that will populate your chart will come from an XML file that is either created by another program specified by a URL, or coded directly in the charting program.

==Using FusionCharts Free with Janus Web==
Once you have uploaded your FusionCharts Free JavaScript files to your server and added appropriate Janus Web Rules to send them to the browser, you are ready to code a Janus Web application to chart your data. You might also need to add a web rule to use Adobe Flash for .swf files. I find the "Data URL" method (see FusionCharts Free documentation) the easiest. In your Janus Web Program, you would add a container for your chart and the JavaScript code to call the chart-type JavaScrip and also your data URL. '''Note:''' If your data URL program is being passed parameters, the URL must be URL Encoded using the Sirius URLENCODE function or the JavaScript "escape()" method.

In the <head> of your HTML file you will need to include the following:

<SCRIPT LANGUAGE="Javascript" SRC="/FusionCharts/FusionCharts.js"></SCRIPT>

You may need to modify the path name depending on your Janus Web Rules.

You will then add the following code in the <body> of the HTML:
<nowiki>...
HTML
<div id="chart1div">This text is replaced by the chart
</div>
<script type="text/javascript">
var chart1 = new FusionCharts("Pie2D.swf", "ChId1", "600", "400", "0", "0");
//To pass parameters, URLEncode the dataURL. Use escape() in JavaScript
chart1.setDataURL(escape("Data.URL?id=1&subId=2"));
chart1.render("chart1div");
</script>
END HTML
...</nowiki>

Assuming you have coded up everything properly, the FusionCharts Column2D.swf JavaScript will call the Data.URL User Language program which will return an XML file properly formatted for creating a FusionCharts 2D Column Chart. Here is an example of a Column2D XML File:

<graph caption='Pie Chart' decimalPrecision='0' showPercentageValues='0' showNames='1' numberPrefix='$' showValues='1' showPercentageInLabel='0' pieYScale='45' pieBorderAlpha='100' pieRadius='100' animation='0' shadowXShift='4' shadowYShift='4' shadowAlpha='40' pieFillAlpha='95' pieBorderColor='FFFFFF'>
<set value='25' name='Item A' color='AFD8F8'/>
<set value='17' name='Item B' color='F6BD0F'/>
<set value='23' name='Item C' color='8BBA00' isSliced='1'/>
<set value='65' name='Item D' color='A66EDD'/>
<set value='22' name='Item E' color='F984A1'/>
</graph>

[[File:XML_2DPie1.gif|frame|alt=Sample 2D Pie Chart|Sample 2D Pie Chart]]

==Debugging==
If you see the dreaded JavaScript Error at the bottom of the page, it could be caused by one of the following:
*You actually made an error typing your JavaScript. ''Remember JavaScript is case sensitive.''
*There is a problem with your Janus Web Rules. Check '''SIRSCAN''' and look for Janus Web Rule problems
*There is a problem with the DataURL program or Janus Web Rules
*Your XML data is not in the proper format or is not well-formed

==Additional Capabilities==
You can add even more punch to your FusionCharts data, you can add a ''drill-down'' capability by adding a URL to the XML data for a particular Bar or Slice of a chart. You would need to add the ''link'' property to the ''set'' value for a bar or slice.

<set name='Jan' value='17400' link='n-DemoLinkPages/DemoLink1.html' color='AFD8F8' /

'''Note:''' The n- prefix to the link indicates that it is to open in a new window. Leave this off if you want to replace the active page.

File:XML 2DPie1.gif

2010-10-04T16:58:31Z

Dessick: Sample 2D Pie Chart from FusionChartsFree

Sample 2D Pie Chart from FusionChartsFree

Category:Tutorial

2010-10-04T16:52:58Z

Dessick: Using FusionCharts Free with Janus Web Server to display business charts

[[Category:Charting using Janus Web Server and FusionCharts Free]]
==Background==
You've created a beautiful web site, but the only thing missing is a way to easily add bar graphs, pie charts or other business graphics. Fortunately, there is an easy way to do this at little or no cost using FusionCharts Free from [http://www.fusioncharts.com/free InfoSoft Global Ltd.] '''FusionCharts Free''' supports a generous number of business charts. Of course for more sophisticated options there is a more full featured version, for which you must pay a license fee.

==Chart Types Supported==
'''FusionCharts Free''' supports the following chart types:
*Bar Charts (2D and 3D)
*Pie Charts (2D and 3D)
*Doughnut Charts
*Line Charts
*Area Charts
*Stacked Charts
*Combination (Line & Bar) Charts
*Candlestick Charts
*Funnel Charts
*Gantt Charts

There are 22 different charts, which are rendered as Adobe Flash (.swf) files in the browser using JavaScript.

==Getting Started==
The first step in using Fusion Charts is of course downloading the source. This can be found on the [http://www.fusioncharts.com/free FusionCharts Free] web site. '''Hint''': when you upload the files to your Janus Web Procedure file, upload them as ''binary'' files to avoid the dreaded "Code Page" issue. You must then ad a Janus Web Rule to send them to the browser as "binary". The data that will populate your chart will come from an XML file that is either created by another program specified by a URL, or coded directly in the charting program.

==Using FusionCharts Free with Janus Web==
Once you have uploaded your FusionCharts Free JavaScript files to your server and added appropriate Janus Web Rules to send them to the browser, you are ready to code a Janus Web application to chart your data. You might also need to add a web rule to use Adobe Flash for .swf files. I find the "Data URL" method (see FusionCharts Free documentation) the easiest. In your Janus Web Program, you would add a container for your chart and the JavaScript code to call the chart-type JavaScrip and also your data URL. '''Note:''' If your data URL program is being passed parameters, the URL must be URL Encoded using the Sirius URLENCODE function or the JavaScript "escape()" method.

In the <head> of your HTML file you will need to include the following:

<SCRIPT LANGUAGE="Javascript" SRC="/FusionCharts/FusionCharts.js"></SCRIPT>

You may need to modify the path name depending on your Janus Web Rules.

You will then add the following code in the <body> of the HTML:
<nowiki>...
HTML
<div id="chart1div">This text is replaced by the chart
</div>
<script type="text/javascript">
var chart1 = new FusionCharts("Pie2D.swf", "ChId1", "600", "400", "0", "0");
//To pass parameters, URLEncode the dataURL. Use escape() in JavaScript
chart1.setDataURL(escape("Data.URL?id=1&subId=2"));
chart1.render("chart1div");
</script>
END HTML
...</nowiki>

Assuming you have coded up everything properly, the FusionCharts Column2D.swf JavaScript will call the Data.URL User Language program which will return an XML file properly formatted for creating a FusionCharts 2D Column Chart. Here is an example of a Column2D XML File:

<graph caption='Pie Chart' decimalPrecision='0' showPercentageValues='0' showNames='1' numberPrefix='$' showValues='1' showPercentageInLabel='0' pieYScale='45' pieBorderAlpha='100' pieRadius='100' animation='0' shadowXShift='4' shadowYShift='4' shadowAlpha='40' pieFillAlpha='95' pieBorderColor='FFFFFF'>
<set value='25' name='Item A' color='AFD8F8'/>
<set value='17' name='Item B' color='F6BD0F'/>
<set value='23' name='Item C' color='8BBA00' isSliced='1'/>
<set value='65' name='Item D' color='A66EDD'/>
<set value='22' name='Item E' color='F984A1'/>
</graph>

==Debugging==
If you see the dreaded JavaScript Error at the bottom of the page, it could be caused by one of the following:
*You actually made an error typing your JavaScript. ''Remember JavaScript is case sensitive.''
*There is a problem with your Janus Web Rules. Check '''SIRSCAN''' and look for Janus Web Rule problems
*There is a problem with the DataURL program or Janus Web Rules
*Your XML data is not in the proper format or is not well-formed

==Additional Capabilities==
You can add even more punch to your FusionCharts data, you can add a ''drill-down'' capability by adding a URL to the XML data for a particular Bar or Slice of a chart. You would need to add the ''link'' property to the ''set'' value for a bar or slice.

<set name='Jan' value='17400' link='n-DemoLinkPages/DemoLink1.html' color='AFD8F8' /

'''Note:''' The n- prefix to the link indicates that it is to open in a new window. Leave this off if you want to replace the active page.