Janus port processing and examples - Revision history

JAL2: /* Port name and number */

2012-03-16T21:06:09Z

Port name and number

← Older revision		Revision as of 21:06, 16 March 2012
Line 18:		Line 18:
	Each <var class="term">portname</var> must be unique, but any number of different		Each <var class="term">portname</var> must be unique, but any number of different
	port names may be associated with the same <var class="term">portnum</var> value.		port names may be associated with the same <var class="term">portnum</var> value.
	However, at any point in time only one portname defined to a port may be started by [[JANUS START]].		However, at any point in time only one portname defined to a port may be started by <var>[[JANUS START]]</var>.
	Similarly, a specific port number can only be started on a single <var class="product">Model 204</var>		Similarly, a specific port number can only be started on a single <var class="product">Model 204</var>
	Online on any host.		Online on any host.

JAL2: /* Open Client, SDS, and IFDIAL= */

2012-03-16T21:05:07Z

Open Client, SDS, and IFDIAL=

← Older revision		Revision as of 21:05, 16 March 2012
Line 61:		Line 61:
	</p>		</p>

	==Open Client, SDS, and IFDIAL===		==Open Client, SDS, and IFDIAL==
	The <var>[[MASTER (JANUS DEFINE parameter)\|MASTER]]</var> parameter is specified on the previous port definition,		The <var>[[MASTER (JANUS DEFINE parameter)\|MASTER]]</var> parameter is specified on the previous port definition,
	making it the one that will be used for all <var class="product">Open Client</var> connections		making it the one that will be used for all <var class="product">Open Client</var> connections
Line 100:		Line 100:
	definitions are automatically reloaded at the first user connection		definitions are automatically reloaded at the first user connection
	subsequent to any changes to the <var class="product">Janus Specialty Data Store</var> catalog.		subsequent to any changes to the <var class="product">Janus Specialty Data Store</var> catalog.

	==Janus Web Server==		==Janus Web Server==
	The following <var>DEFINE</var> command specifies a web server at port 666 called <code>WWW</code>:		The following <var>DEFINE</var> command specifies a web server at port 666 called <code>WWW</code>:

JAL2 at 21:04, 16 March 2012

2012-03-16T21:04:42Z

← Older revision		Revision as of 21:04, 16 March 2012
Line 1:		Line 1:
	The port number <var class="term">portnum</var>) specified in [[JANUS DEFINE#Syntax\|JANUS DEFINE syntax]] is the number to		__TOC__

			==Port name and number==
			The port number (<var class="term">portnum</var>) specified in [[JANUS DEFINE#Syntax\|JANUS DEFINE syntax]] is the number to
	which TPC/IP applications refer.		which TPC/IP applications refer.
	The port name (<var class="term">portname</var>) specified in		The port name (<var class="term">portname</var>) specified in
Line 7:		Line 10:
	<p class="code">JANUS DEFINE TRENDS 517 OPENSERV 10 ALLOCC CMD 'TRENDS 3.4'		<p class="code">JANUS DEFINE TRENDS 517 OPENSERV 10 ALLOCC CMD 'TRENDS 3.4'
	</p>		</p>
	In this example, a port named <~~var~~>TRENDS</~~var~~> is associated with TCP/IP port number 517.		In this example, a port named <code>TRENDS</code> is associated with TCP/IP port number 517.
	A maximum of 10 simultaneous connections are allowed.		A maximum of 10 simultaneous connections are allowed.
	Because <code>ALLOCC</code> is specified, buffers are allocated for a thread only		Because <code>ALLOCC</code> is specified, buffers are allocated for a thread only
	when a client connects to it.		when a client connects to it.
	The subsystem "TRENDS" is automatically invoked with its command line variable set to 3.4.		The subsystem <code>TRENDS</code> is automatically invoked with its command line variable set to 3.4.

	Each <var class="term">portname</var> must be unique, but any number of different		Each <var class="term">portname</var> must be unique, but any number of different
Line 30:		Line 33:
	</p>		</p>
	The number of <var>DEFINE</var>'d and <var>START</var>'ed ports may exceed the number of		The number of <var>DEFINE</var>'d and <var>START</var>'ed ports may exceed the number of
	available sdaemons.		available sdaemons. For example, a site may have 100 users and a license to run 100 Janus connections.

	For example, a site may have 100 users and a license to run 100 Janus connections.
	If each user was allowed to		If each user was allowed to
	connect to any of four different systems, a System Administrator might run the		connect to any of four different systems, a System Administrator might run the
Line 59:		Line 60:
	CMD 'INCLUDE STORES.1' MASTER TIMEOUT 300		CMD 'INCLUDE STORES.1' MASTER TIMEOUT 300
	</p>		</p>

	The <var>MASTER</var> parameter is specified on the previous port definition,		==Open Client, SDS, and IFDIAL===
			The <var>[[MASTER (JANUS DEFINE parameter)\|MASTER]]</var> parameter is specified on the previous port definition,
	making it the one that will be used for all <var class="product">Open Client</var> connections		making it the one that will be used for all <var class="product">Open Client</var> connections
	that originate from within the <var class="product">Model 204</var> address space.		that originate from within the <var class="product">Model 204</var> address space.
Line 99:		Line 101:
	subsequent to any changes to the <var class="product">Janus Specialty Data Store</var> catalog.		subsequent to any changes to the <var class="product">Janus Specialty Data Store</var> catalog.

			==Janus Web Server==
	The following <var>DEFINE</var> command specifies a web server at port 666 called <code>WWW</code>:		The following <var>DEFINE</var> command specifies a web server at port 666 called <code>WWW</code>:
	<p class="code">JANUS DEFINE WWW 666 WEBSERV 300 WEBUSER WWWUSER CMD 'UTABLE LSTBL 12000'		<p class="code">JANUS DEFINE WWW 666 WEBSERV 300 WEBUSER WWWUSER CMD 'UTABLE LSTBL 12000'

JAL2: Created page with "The port number `portnum`) specified in JANUS DEFINE syntax is the number to which TPC/IP applications refer. The port name (2012-03-16T20:52:12Z Created page with "The port number <var class="term">portnum</var>) specified in JANUS DEFINE syntax is the number to which TPC/IP applications refer. The port name (<var cl..." New page The port number <var class="term">portnum</var>) specified in [[JANUS DEFINE#Syntax|JANUS DEFINE syntax]] is the number to which TPC/IP applications refer. The port name (<var class="term">portname</var>) specified in the command is the handle used by other <var>JANUS</var> commands to <var>START</var>, <var>DRAIN</var> and perform all other internal services against TCP/IP threads. For example, consider the following port definition: JANUS DEFINE TRENDS 517 OPENSERV 10 ALLOCC CMD 'TRENDS 3.4' In this example, a port named <var>TRENDS</var> is associated with TCP/IP port number 517. A maximum of 10 simultaneous connections are allowed. Because <code>ALLOCC</code> is specified, buffers are allocated for a thread only when a client connects to it. The subsystem "TRENDS" is automatically invoked with its command line variable set to 3.4. Each <var class="term">portname</var> must be unique, but any number of different port names may be associated with the same <var class="term">portnum</var> value. However, at any point in time only one portname defined to a port may be started by [[JANUS START]]. Similarly, a specific port number can only be started on a single <var class="product">Model 204</var> Online on any host. The ability to have multiple <var class="term">portname</var> values associated with a <var class="term">portnum</var> is useful if you want to be able to invoke different versions of a program (say a "test" and a "production" version) on the same port at different times of the day. For example: JANUS DEFINE ACCTPROD 1001 OPENSERV 20 - OPEN FILE PRODPROC CMD 'I AA1' JANUS DEFINE ACCTTEST 1001 OPENSERV 20 - OPEN FILE TESTPROC CMD 'I AA1' The number of <var>DEFINE</var>'d and <var>START</var>'ed ports may exceed the number of available sdaemons. For example, a site may have 100 users and a license to run 100 Janus connections. If each user was allowed to connect to any of four different systems, a System Administrator might run the following set of port definitions: JANUS DEFINE RECVBL 517 OPENSERV 100 CMD RECEIVBL JANUS DEFINE PAYABL 518 OPENSERV 100 CMD PAYABLES JANUS DEFINE CHCKBK 519 OPENSERV 100 CMD CHCKBOOK JANUS DEFINE GENLDG 520 OPENSERV 100 CMD GENRLDGR 400 connections are defined, but as long as no more than 100 simultaneous connections occur, no client will be refused a connection. In shops where users access more than one application, this will be a common situation. Shops with windowed front-end software should remember that a single user may be able to initiate a number of simultaneous connections to Janus ports. System Administrators should plan for the number of Janus connections required, not the number of users on the network. In the following example, a port called <var>STORES</var> is defined to TCP/IP port number 3000. A maximum of 3 simultaneous connections is allowed. File <var>STOREDAT</var> is automatically opened when a client connection is established, and procedure <code>STORES.1</code> is <var>INCLUDE</var>'d. Users are timed out from this port after 5 minutes of inactivity. JANUS DEFINE STORES 3000 OPENSERV 3 OPEN FILE STOREDAT - CMD 'INCLUDE STORES.1' MASTER TIMEOUT 300 The <var>MASTER</var> parameter is specified on the previous port definition, making it the one that will be used for all <var class="product">Open Client</var> connections that originate from within the <var class="product">Model 204</var> address space. The following DEFINE command defines a port called <code>CONNECT_EXTERNAL</code> that allows 50 simultaneous connections: JANUS DEFINE CONNECT_EXTERNAL 3001 OPENSERV 50 - MASTER CMD 'DISCONNECT' <code>MASTER</code> specifies that it is the port which will be used for <var class="product">Janus Open Client</var> calls. <code>CMD</code> is set to <code>DISCONNECT</code> so that any client that attempts to connect to this port from another client will automatically be disconnected. A TCP/IP port definition created by <var>JANUS DEFINE</var> persists until the Online is brought down or a <var>[[JANUS DELETE]]</var> is executed against it. To automate port definitions, the <var>JANUS DEFINE</var> and <var>JANUS START</var> commands may be stored in a <var class="product">Model 204</var> procedure file as a procedure, which may be executed by User 0. They can also be stored in the <var>JANMAN</var> database and executed via <var>JANMAN</var> commands. Alternatively, the commands may be inserted directly in the User 0 CCAIN stream, similar to dynamic allocation commands for files or printers. This example defines IFDIAL service on port 810: JANUS DEFINE DIRECT 810 IFDIAL 20 TIMEOUT 600 The service is called <code>DIRECT</code>, and 20 simultaneous connections are allowed, with an inactivity timeout of 10 minutes. The following example defines <var class="product">[http://www.sirius-software.com/maint/download/sdsr.pdf SDS]</var> service at port 90210: JANUS DEFINE SQLIN 90210 SDS 150 AUTOLOAD The service is called <code>SQLINT</code>, 150 simultaneous connections are allowed, and the table definitions are automatically reloaded at the first user connection subsequent to any changes to the <var class="product">Janus Specialty Data Store</var> catalog. The following <var>DEFINE</var> command specifies a web server at port 666 called <code>WWW</code>: JANUS DEFINE WWW 666 WEBSERV 300 WEBUSER WWWUSER CMD 'UTABLE LSTBL 12000' The command allows up to 300 simultaneous connections, and connections requesting URLs that do not require logons will appear in <var class="product">Model 204</var> with user ID <code>WWWUSER</code>. The <code>CMD</code> phrase sets <code>LSTBL</code> to 12000 for <code>WWW</code> users. URL processing is handled by rules specified on <var>[[JANUS WEB]]</var> subcommands — this is the default processing when <var>CMD</var> does not reroute processing to either an <var>APSY</var> or to a <var class="product">User Language</var> procedure. The <var>DEFINE</var> command below specifies a web server at port 3278 called <code>INTRANET</code>: JANUS DEFINE INTRANET 3278 WEBSERV 50 TRACE 9 As many as 50 simultaneous connections are allowed, and the <var>[[JANUS TRACE]]</var> 1 and 8 bits are turned on, sending the header parameters and a TCP/IP packet trace to the audit trail. The following example defines a web server port called <code>BENEFITS</code> at port 3279 allowing up to 250 simultaneous connections: JANUS DEFINE BENEFITS 3279 WEBSERV 250 - WEBUSER WWW OPEN FILE BENPROC - CMD 'INCLUDE BENEFITS_SECURITY' The default logon ID for connections that do not require logons is <code>WWW</code>. Connecting users open the <code>BENEFITS</code> file and execute the command specified by <code>CMD</code>; in this case, the <var class="product">Model 204</var> procedure <code>BENEFITS_SECURITY</code> is executed. Any command specified by <var>CMD</var> is processed before any <var>JANUS WEB</var> rules, but there must be an <var>ON</var> rule matching each incoming URL. If a URL is not matched by some active <var>[[JANUS WEB ON]]</var> rule, it will be rejected and the command specified by <var>CMD</var> in the <var>JANUS DEFINE</var> statement will not be executed. '''Note:''' You can review the contents of any of your port definitions by issuing <var>[[JANUS DISPLAY]]</var> followed by the name of the port. [[Category:Janus TCP/IP Base]]