cvs: phpdoc /en/reference/sesam ini.xml reference.xml /en/reference/strings charsets.xml

derick Thu Jun 12 05:15:03 2003 EDT Modified files: /phpdoc/en/reference/sesam ini.xml reference.xml /phpdoc/en/reference/strings charsets.xml Log: - Fix XML: XML files can only have one root node. Another solution would be to make these entities instead.

Index: phpdoc/en/reference/sesam/ini.xml diff -u phpdoc/en/reference/sesam/ini.xml:1.1 phpdoc/en/reference/sesam/ini.xml:1.2 --- phpdoc/en/reference/sesam/ini.xml:1.1 Sun Sep 29 20:09:46 2002 +++ phpdoc/en/reference/sesam/ini.xml Thu Jun 12 05:15:03 2003 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1"?> -<!-- $Revision: 1.1 $ --> +<!-- $Revision: 1.2 $ --> <section id="sesam.configuration"> &reftitle.runtime; &extension.runtime; @@ -69,182 +69,6 @@ </variablelist> </section> - - <section id="sesam.config-notes"> - <title>Configuration notes</title> - <para> - There is no standalone support for the PHP SESAM interface, it - works only as an integrated Apache module. In the Apache PHP - module, this <link linkend="sesam.configuration">SESAM interface is - configured</link> using Apache directives. - <table> - <title>SESAM Configuration directives</title> - <tgroup cols="2"> - <thead> - <row> - <entry>Directive</entry> - <entry>Meaning</entry> - </row> - </thead> - <tbody> - <row> - <entry><literal>php3_sesam_oml</literal></entry> - <entry> - Name of BS2000 PLAM library containing the loadable SESAM - driver modules. Required for using SESAM functions. - <para> - Example: - <informalexample> - <programlisting role="apache"> -<![CDATA[ -php3_sesam_oml $.SYSLNK.SESAM-SQL.030 -]]> - </programlisting> - </informalexample> - </para> - </entry> - </row> - <row> - <entry><literal>php3_sesam_configfile</literal></entry> - <entry> - Name of SESAM application configuration file. Required for - using SESAM functions. - <para> - Example: - <informalexample> - <programlisting role="apache"> -<![CDATA[ -php3_sesam_configfile $SESAM.SESAM.CONF.AW -]]> - </programlisting> - </informalexample> - It will usually contain a configuration like (see SESAM - reference manual): - <informalexample> - <programlisting role="bs2000"> -<![CDATA[ -CNF=B -NAM=K -NOTYPE -]]> - </programlisting> - </informalexample> - </para> - </entry> - </row> - <row> - <entry><literal>php3_sesam_messagecatalog</literal></entry> - <entry> - Name of SESAM message catalog file. In most cases, this - directive is not neccessary. Only if the SESAM message file - is not installed in the system's BS2000 message file table, - it can be set with this directive. - <para> - Example: - <informalexample> - <programlisting role="apache"> -<![CDATA[ -php3_sesam_messagecatalog $.SYSMES.SESAM-SQL.030 -]]> - </programlisting> - </informalexample> - </para> - </entry> - </row> - </tbody> - </tgroup> - </table> - </para> - <para> - In addition to the configuration of the PHP/SESAM interface, you - have to configure the SESAM-Database server itself on your - mainframe as usual. That means: - <itemizedlist> - <listitem> - <simpara> - starting the SESAM database handler (DBH), and - </simpara> - </listitem> - <listitem> - <simpara> - connecting the databases with the SESAM database handler - </simpara> - </listitem> - </itemizedlist> - </para> - <para> - To get a connection between a PHP script and the database - handler, the <literal>CNF</literal> and <literal>NAM</literal> - parameters of the selected SESAM configuration file must match - the id of the started database handler. - </para> - <para> - In case of distributed databases you have to start a - SESAM/SQL-DCN agent with the distribution table including the - host and database names. - </para> - <para> - The communication between PHP (running in the POSIX subsystem) - and the database handler (running outside the POSIX subsystem) is - realized by a special driver module called SQLSCI and SESAM - connection modules using common memory. Because of the common - memory access, and because PHP is a static part of the web - server, database accesses are very fast, as they do not require - remote accesses via ODBC, JDBC or UTM. - </para> - <para> - Only a small stub loader (SESMOD) is linked with PHP, and the - SESAM connection modules are pulled in from SESAM's OML PLAM - library. In the <link - linkend="sesam.configuration">configuration</link>, you must tell PHP - the name of this PLAM library, and the file link to use for the - SESAM configuration file (As of SESAM V3.0, SQLSCI is available - in the SESAM Tool Library, which is part of the standard - distribution). - </para> - <para> - Because the SQL command quoting for single quotes uses duplicated - single quotes (as opposed to a single quote preceded by a - backslash, used in some other databases), it is advisable to set - the PHP configuration directives <link - linkend="ini.magic-quotes-gpc"><literal>php3_magic_quotes_gpc</literal></link> - and <link - linkend="ini.magic-quotes-sybase"><literal>php3_magic_quotes_sybase</literal></link> - to <literal>On</literal> for all PHP scripts using the SESAM - interface. - </para> - </section> - - <section id="sesam.runtime"> - <title>Runtime considerations</title> - <para> - Because of limitations of the BS2000 process model, the driver - can be loaded only after the Apache server has forked off its - server child processes. This will slightly slow down the initial - SESAM request of each child, but subsequent accesses will respond - at full speed. - </para> - <para> - When explicitly defining a Message Catalog for SESAM, that - catalog will be loaded each time the driver is loaded (i.e., at - the initial SESAM request). The BS2000 operating system prints a - message after successful load of the message catalog, which will - be sent to Apache's error_log file. BS2000 currently does not - allow suppression of this message, it will slowly fill up the - log. - </para> - <para> - Make sure that the SESAM OML PLAM library and SESAM configuration - file are readable by the user id running the web server. - Otherwise, the server will be unable to load the driver, and will - not allow to call any SESAM functions. Also, access to the - database must be granted to the user id under which the Apache - server is running. Otherwise, connections to the SESAM database - handler will fail. - </para> - -</section> - <!-- Keep this comment at the end of the file Local variables: Index: phpdoc/en/reference/sesam/reference.xml diff -u phpdoc/en/reference/sesam/reference.xml:1.4 phpdoc/en/reference/sesam/reference.xml:1.5 --- phpdoc/en/reference/sesam/reference.xml:1.4 Sun Sep 29 20:09:46 2002 +++ phpdoc/en/reference/sesam/reference.xml Thu Jun 12 05:15:03 2003 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1"?> -<!-- $Revision: 1.4 $ --> +<!-- $Revision: 1.5 $ --> <reference id="ref.sesam"> <title>SESAM database functions</title> <titleabbrev>SESAM</titleabbrev> @@ -49,6 +49,180 @@ </section> &reference.sesam.ini; + + <section id="sesam.config-notes"> + <title>Configuration notes</title> + <para> + There is no standalone support for the PHP SESAM interface, it + works only as an integrated Apache module. In the Apache PHP + module, this <link linkend="sesam.configuration">SESAM interface is + configured</link> using Apache directives. + <table> + <title>SESAM Configuration directives</title> + <tgroup cols="2"> + <thead> + <row> + <entry>Directive</entry> + <entry>Meaning</entry> + </row> + </thead> + <tbody> + <row> + <entry><literal>php3_sesam_oml</literal></entry> + <entry> + Name of BS2000 PLAM library containing the loadable SESAM + driver modules. Required for using SESAM functions. + <para> + Example: + <informalexample> + <programlisting role="apache"> +<![CDATA[ +php3_sesam_oml $.SYSLNK.SESAM-SQL.030 +]]> + </programlisting> + </informalexample> + </para> + </entry> + </row> + <row> + <entry><literal>php3_sesam_configfile</literal></entry> + <entry> + Name of SESAM application configuration file. Required for + using SESAM functions. + <para> + Example: + <informalexample> + <programlisting role="apache"> +<![CDATA[ +php3_sesam_configfile $SESAM.SESAM.CONF.AW +]]> + </programlisting> + </informalexample> + It will usually contain a configuration like (see SESAM + reference manual): + <informalexample> + <programlisting role="bs2000"> +<![CDATA[ +CNF=B +NAM=K +NOTYPE +]]> + </programlisting> + </informalexample> + </para> + </entry> + </row> + <row> + <entry><literal>php3_sesam_messagecatalog</literal></entry> + <entry> + Name of SESAM message catalog file. In most cases, this + directive is not neccessary. Only if the SESAM message file + is not installed in the system's BS2000 message file table, + it can be set with this directive. + <para> + Example: + <informalexample> + <programlisting role="apache"> +<![CDATA[ +php3_sesam_messagecatalog $.SYSMES.SESAM-SQL.030 +]]> + </programlisting> + </informalexample> + </para> + </entry> + </row> + </tbody> + </tgroup> + </table> + </para> + <para> + In addition to the configuration of the PHP/SESAM interface, you + have to configure the SESAM-Database server itself on your + mainframe as usual. That means: + <itemizedlist> + <listitem> + <simpara> + starting the SESAM database handler (DBH), and + </simpara> + </listitem> + <listitem> + <simpara> + connecting the databases with the SESAM database handler + </simpara> + </listitem> + </itemizedlist> + </para> + <para> + To get a connection between a PHP script and the database + handler, the <literal>CNF</literal> and <literal>NAM</literal> + parameters of the selected SESAM configuration file must match + the id of the started database handler. + </para> + <para> + In case of distributed databases you have to start a + SESAM/SQL-DCN agent with the distribution table including the + host and database names. + </para> + <para> + The communication between PHP (running in the POSIX subsystem) + and the database handler (running outside the POSIX subsystem) is + realized by a special driver module called SQLSCI and SESAM + connection modules using common memory. Because of the common + memory access, and because PHP is a static part of the web + server, database accesses are very fast, as they do not require + remote accesses via ODBC, JDBC or UTM. + </para> + <para> + Only a small stub loader (SESMOD) is linked with PHP, and the + SESAM connection modules are pulled in from SESAM's OML PLAM + library. In the <link + linkend="sesam.configuration">configuration</link>, you must tell PHP + the name of this PLAM library, and the file link to use for the + SESAM configuration file (As of SESAM V3.0, SQLSCI is available + in the SESAM Tool Library, which is part of the standard + distribution). + </para> + <para> + Because the SQL command quoting for single quotes uses duplicated + single quotes (as opposed to a single quote preceded by a + backslash, used in some other databases), it is advisable to set + the PHP configuration directives <link + linkend="ini.magic-quotes-gpc"><literal>php3_magic_quotes_gpc</literal></link> + and <link + linkend="ini.magic-quotes-sybase"><literal>php3_magic_quotes_sybase</literal></link> + to <literal>On</literal> for all PHP scripts using the SESAM + interface. + </para> + </section> + + <section id="sesam.runtime"> + <title>Runtime considerations</title> + <para> + Because of limitations of the BS2000 process model, the driver + can be loaded only after the Apache server has forked off its + server child processes. This will slightly slow down the initial + SESAM request of each child, but subsequent accesses will respond + at full speed. + </para> + <para> + When explicitly defining a Message Catalog for SESAM, that + catalog will be loaded each time the driver is loaded (i.e., at + the initial SESAM request). The BS2000 operating system prints a + message after successful load of the message catalog, which will + be sent to Apache's error_log file. BS2000 currently does not + allow suppression of this message, it will slowly fill up the + log. + </para> + <para> + Make sure that the SESAM OML PLAM library and SESAM configuration + file are readable by the user id running the web server. + Otherwise, the server will be unable to load the driver, and will + not allow to call any SESAM functions. Also, access to the + database must be granted to the user id under which the Apache + server is running. Otherwise, connections to the SESAM database + handler will fail. + </para> + </section> <section id="sesam.cursor-types"> <title>Cursor Types</title> Index: phpdoc/en/reference/strings/charsets.xml diff -u phpdoc/en/reference/strings/charsets.xml:1.3 phpdoc/en/reference/strings/charsets.xml:1.4 --- phpdoc/en/reference/strings/charsets.xml:1.3 Mon Jun 2 12:19:37 2003 +++ phpdoc/en/reference/strings/charsets.xml Thu Jun 12 05:15:03 2003 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1"?> -<!-- $Revision: 1.3 $ --> +<!-- $Revision: 1.4 $ --> <para> Following character sets are supported in PHP 4.3.0 and later. <table> @@ -103,13 +103,13 @@ </tbody> </tgroup> </table> + <note> + <simpara> + Any other character sets are not recognized and ISO-8859-1 will be used + instead. + </simpara> + </note> </para> -<note> - <simpara> - Any other character sets are not recognized and ISO-8859-1 will be used - instead. - </simpara> -</note> <!-- Keep this comment at the end of the file Local variables: mode: sgml