JANUS DEFINEREMOTE - Revision history

JAL: /* CHARSET xxx */

2014-10-14T21:19:31Z

CHARSET xxx

← Older revision		Revision as of 21:19, 14 October 2014
Line 36:		Line 36:
	===CHARSET xxx===		===CHARSET xxx===

	This parameter specifies the character set to use for this remote port, allowing override of either the default character set or the character set specified on the <var>JANUS CHARSET</var> subcommand. The default character set is iso_1. <var>CHARSET</var> has no effect on the operation of any application in <var class="product">Model 204</var>. The name of the specified character set is simply forwarded to the target server for a <var class="product">[http://~~sirius-software~~.com/~~maint~~/~~download~~/~~josrvr~~.pdf Janus Open Client]</var> application. For further discussion, see <var>[[JANUS CHARSET]]</var>.		This parameter specifies the character set to use for this remote port, allowing override of either the default character set or the character set specified on the <var>JANUS CHARSET</var> subcommand. The default character set is <code>iso_1</code>. <var>CHARSET</var> has no effect on the operation of any application in <var class="product">Model 204</var>. The name of the specified character set is simply forwarded to the target server for a <var class="product">[http://m204wiki.rocketsoftware.com/images/4/4a/JoclrNew.pdf Janus Open Client]</var> application. For further discussion, see <var>[[JANUS CHARSET]]</var>.

	===INONLY===		===INONLY===

JALWiccan: Automatically generated page update

2013-03-13T16:02:27Z

Automatically generated page update

← Older revision		Revision as of 16:02, 13 March 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:JANUS DEFINEREMOTE}}		{{DISPLAYTITLE:JANUS DEFINEREMOTE}}
	<span class="pageSubtitle"~~><section begin="desc" /~~>Define remote port and characteristics for OPENSERV port.~~<section end="desc" />~~</span>		<span class="pageSubtitle">Define remote port and characteristics for OPENSERV port.</span>

	This command associates a remote server with a Janus <var>[[JANUS DEFINE#type\|OPENSERV]]</var> port and specifies characteristics of connections with that remote server.		This command associates a remote server with a Janus <var>[[JANUS DEFINE#type\|OPENSERV]]</var> port and specifies characteristics of connections with that remote server.
Line 7:		Line 7:

	==Syntax==		==Syntax==
	<p class="syntax"~~><section begin="syntax" /~~><span class="literal">JANUS DEFINEREMOTE </span><span class="term">portname remotename host portnum </span><span class="squareb">[</span><span class="term">optional parms...</span><span class="squareb">]</span>		<p class="syntax"><span class="literal">JANUS DEFINEREMOTE </span><span class="term">portname remotename host portnum </span><span class="squareb">[</span><span class="term">optional parms...</span><span class="squareb">]</span>
	~~<section end="syntax" />~~</p>		</p>

	Where each of the first four parameters is positional and required:		Where each of the first four parameters is positional and required:

JAL2 at 21:38, 7 August 2012

2012-08-07T21:38:25Z

← Older revision		Revision as of 21:38, 7 August 2012
Line 14:		Line 14:
	<table class="syntaxTable">		<table class="syntaxTable">
	<tr><th>portname</th>		<tr><th>portname</th>
	<td>The name of the Janus port(s) with which a remote server is being associated. Wildcard characters may be used in <var class="term">portname</var>, indicating that the remote server is associated with all previously defined <var ~~class="term"~~>SDS</var> or <var>OPENSERV</var> ports matching the pattern. There must be at least one previously defined <var ~~class="term"~~>SDS</var> or <var>OPENSERV</var> port matching <var class="term">portname</var>. Any ports which match <var class="term">portname</var> but have not yet been defined will not be associated with <var class="term">remotename</var>, even if they are subsequently defined.</td></tr>		<td>The name of the Janus port(s) with which a remote server is being associated. Wildcard characters may be used in <var class="term">portname</var>, indicating that the remote server is associated with all previously defined <var>SDS</var> or <var>OPENSERV</var> ports matching the pattern. There must be at least one previously defined <var>SDS</var> or <var>OPENSERV</var> port matching <var class="term">portname</var>. Any ports which match <var class="term">portname</var> but have not yet been defined will not be associated with <var class="term">remotename</var>, even if they are subsequently defined.</td></tr>
	<tr><th>remotename</th>		<tr><th>remotename</th>
	<td>A 1-30 character name for the remote server to which this Janus port will connect and/or from which connections will be accepted. The remote server may be a ''Sybase SQL Server'', a ''Sybase Open Server'' or <var class="product">[http://sirius-software.com/maint/download/josrvr.pdf Janus Open Server]</var>, or another vendor's ''Open Server''. Wildcard characters may not be used in the <var class="term">remotename</var> specification.</td></tr>		<td>A 1-30 character name for the remote server to which this Janus port will connect and/or from which connections will be accepted. The remote server may be a ''Sybase SQL Server'', a ''Sybase Open Server'' or <var class="product">[http://sirius-software.com/maint/download/josrvr.pdf Janus Open Server]</var>, or another vendor's ''Open Server''. Wildcard characters may not be used in the <var class="term">remotename</var> specification.</td></tr>

JAL2: /* See also */

2011-10-14T20:31:48Z

JAL2 at 20:30, 14 October 2011

2011-10-14T20:30:04Z

Show changes

Dme: /* Janus remote server processing and examples */

2011-10-14T20:05:41Z

Janus remote server processing and examples

New page

{{DISPLAYTITLE:JANUS DEFINEREMOTE}}
<span class="pageSubtitle"><section begin="desc" />Define remote port and characteristics for OPENSERV port.<section end="desc" /></span>

This command associates a remote server with a Janus <var>OPENSERV</var> port and specifies characteristics of connections with that remote server.

See [[JANUS DEFINE]] for a discussion of when you need to issue the <var>JANUS DEFINE</var> command.

==Syntax==
<p class="syntax"><section begin="syntax" /> JANUS DEFINEREMOTE portname remotename host portnum [optional parms...]
<section end="syntax" /></p>
<p class="caption">JANUS DEFINEREMOTE command syntax
</p>

Where each of the first four parameters is positional and required:

<table class="syntaxTable">
<tr><th>portname</th>
<td>The name of the Janus port(s) with which a remote server is being associated. Wildcard characters may be used in <var class="term">portname</var>, indicating that the remote server is associated with all previously defined <var class="term">SDS</var> or <var>OPENSERV</var> ports matching the pattern. There must be at least one previously defined <var class="term">SDS</var> or <var>OPENSERV</var> port matching <var class="term">portname</var>. Any ports which match <var class="term">portname</var> but have not yet been defined will not be associated with <var class="term">remotename</var>, even if they are subsequently defined.</td></tr>
<tr><th>remotename</th>
<td>A 1 - 30 character name for the remote server to which this Janus port will connect and/or from which connections will be accepted. The remote server may be a Sybase SQL server, a Sybase, Open Server or <var class="product">[[Janus Open Server]]</var>, or another vendor's Open Server. Wildcard characters may not be used in the <var class="term">remotename</var> specification.</td></tr>
<tr><th>host</th>
<td>The IP address or hostname for the device on which the server specified in <var class="term">remotename</var> is running.</td></tr>
<tr><th>portnum</th>
<td>The port number on which the server specified in <var class="term">remotename</var> is running.
</td></tr></table>

''[[Janus Open Server]]'', Sybase Open Server, and SQL Server names '''are''' case sensitive. If you are using server names that contain lower case characters, execute a <var>*LOWER</var> before running the <var>JANUS DEFINEREMOTE</var>.

Valid abbreviations for <var>DEFINEREMOTE</var> are <var>DEFREM</var>, <var>DEFREMOTE</var> and <var>DEFINEREM</var>.

==Optional parameters==

The optional parameters are shown in the following sections.

===CHARSET xxx===

This parameter specifies the character set to use for this remote port, allowing override of either the default character set or the character set specified on the <var>JANUS CHARSET</var> subcommand. The default character set is iso_1. <var>CHARSET</var> has no effect on the operation of any application in <var class="product">Model 204</var>. The name of the specified character set is simply forwarded to the target server for a ''[[Janus Open Client]]'' application. For further discussion, see <var>[[JANUS CHARSET]]</var>.

===INONLY===

This parameter specifies that only incoming calls are allowed from this remote server, that is, <var class="product">Janus Open Client</var> applications which are running on <var class="term">portname</var> are not allowed to use <var>$DB_xxx</var> functions to connect with <var class="term">remotename</var>. The default is to allow connections both to and from the remote server. If a site does not have <var class="product">Janus Open Client</var>, <var>INONLY</var> is the default since outgoing connections cannot be established without <var class="product">Janus Open Client</var>.

===LANGUAGE xxx===

This parameter specifies the language to use for this remote port, allowing override of either the default language or the language specified on the <var>JANUS LANGUAGE</var> subcommand. The default language is us_english. <var>LANGUAGE</var> has no effect on the operation of any application in <var class="product">Model 204</var>. For further discussion, see <var>[[JANUS LANGUAGE]]</var>.

===NOSITE===

This parameter specifies that an outgoing <var class="product">Janus Open Client</var> connection is not to use a site handler, that is, it is to appear as a client to server rather than a server to server connection to the target server. Use of <var>NOSITE</var> makes it possible to connect to a remote server without the Janus port being defined to the that server; this is required for Microsoft SQL Server. When using Sybase or Omni SQL Server or Sybase Adaptive Server, the sp_addremotelogin procedure, which normally can translate <var class="product">Model 204</var> user IDs to Sybase user IDs, cannot be used on a client to server connection.

===OPTSITE===

This parameter specifies that an outgoing (<var class="product">Janus Open Client</var>) connection can choose to not use a site handler by using the <var>NOSITE</var> parameter on the <var>[[$DB_OPEN]]</var> call. That is, it can appear as a client to server rather than a server to server connection to the target server.

===OUTONLY===

This parameter specifies that only outgoing calls to this remote server are allowed. The default is to allow connections both to and from the remote server. If a site does not have <var class="product">Janus Open Server</var>, <var>OUTONLY</var> is the default since incoming connections cannot be handled without ''[[Janus Open Server]]''.

===SITEACCT xxx===

This parameter specifies the <var class="product">Model 204</var> <var>ACCOUNT</var> for the site handler for the remote server. If no <var>SITEACCT</var> is specified the <var>ACCOUNT</var> for the user executing the <var>DEFINEREMOTE</var> command is used.

===SITEUSER xxx===

This parameter specifies the <var class="product">Model 204</var> user ID for the ''site handler'' for the remote server. If no <var>SITEUSER</var> is specified the user ID for the user executing the <var>DEFINEREMOTE</var> command is used.

===TIMEOUT xxx===

This parameter specifies the number of seconds without a logical connection after which the site handlers will log off and the connection to the remote server will be broken. The default <var>TIMEOUT</var> is 60 seconds.

===TRUST===

This parameter permits the port to initiate a user session for an incoming user ID by performing a trusted login and ignoring the password. To minimize the security hole introduced by this parameter, the <var>VERIP</var> parameter should also be specified when <var>TRUST</var> is specified.

===VERIP===

This parameter specifies validation of the IP address of the connecting remote server. This indicates that Janus should reject a connection attempt by the remote server if the IP address does not match either the IP address specified on the <var>JANUS DEFINEREMOTE</var> command or the IP address found by doing a DNS name lookup on the host name specified on the <var>JANUS DEFINEREMOTE</var> command. <var>VERIP</var> does '''not''' provide bullet-proof security because it is not a difficult task to spoof (fake) an IP address. Nevertheless, it is better than nothing and should certainly be used whenever the <var>TRUST</var> parameter is specified.

==Janus remote server processing and examples==

Note that several of the optional parameters of <var>JANUS DEFINEREMOTE</var> use the term <var class="term">site handler</var>. One reason a remote port must be defined is to allow a <var class="product">[[Janus Open Server]]</var> port to accept requests from remote server host. A '''site handler''' is used for this purpose, and for <var class="product">Janus Open Client</var> communications to remote servers without the <var>NOSITE</var> parameter.

A site handler is an [[sdaemon]] that performs the task of multiplexing logical user connections across a physical connection to a remote server. The site handler appears as a <var class="product">Model 204</var> user the first time a logical connection is established with the remote server. The site handler remains logged on for as long as any logical connection exists. Then, after <var>TIMEOUT</var> seconds have elapsed the site handler also logs off. The site handler occupies an sdaemon thread and counts as a Janus connection.

If a site handler is bumped, it is disconnected immediately irrespective of <var>TIMEOUT</var>, and all logical user connections to the remote server are lost. It is recommended that site handlers not be bumped.

The rest of this section contains several examples of <var>JANUS DEFINEREMOTE</var>.

<p class="code"> JANUS DEFINE AGENTS OPENSERV 4021 CMD 'MAILLIST'
JANUS DEFREM AGENTS AGENTS_SQL_SERVER -
RS6000 3010 INONLY SITEUSER 'GHOST'
</p>

In the previous example the remote server <code>AGENTS_SQL_SERVER</code> is associated with port <code>AGENTS</code>. <code>AGENTS_SQL_SERVER</code> is running on a host name <code>RS6000</code> at port number 3010. <var>INONLY</var> specifies that the port cannot be used by <var class="product">Janus Open Client</var> functions. The site handler will appear as user ID <code>GHOST</code>. and will timeout 60 seconds after the last user connection terminates (using the default <var>TIMEOUT</var>). Each user connecting from the remote server is thrown directly into subsystem <code>MAILLIST</code> by the <var>JANUS DEFINE</var> command.

<p class="code"> JANUS DEFINE PRODUCERS OPENSERV 4022 -
CMD 'CONTACTS'
JANUS DEFREM PRODUCERS big_shots RS6000 3030 -
SITEUSER 'CASPER'
JANUS START PRODUCERS
</p>

In this example we first set the session to mixed case with <var>*LOWER</var> to allow us to define a lower-case remote server name. Next we define the <var class="product">Janus Open Server</var> port <code>PRODUCERS</code> and associate it with port number 4022 and the subsystem <code>CONTACTS</code>. We designate the remote server (for incoming and outgoing connections) as a server named big_shots running on host <code>RS6000</code> at port 3030 with the site handler having <var class="product">Model 204</var> user ID <code>CASPER</code>. Then we start port <code>PRODUCERS</code>, making it available for connections.

<p class="code"> JANUS DEFINE DIRECTORS OPENSERV 4027 -
CMD 'WANNABE' MASTER UPCASE
JANUS DEFINEREMOTE DIR* lights_cameras_action -
RS6000 3037 SITEUSER 'ICHABOD' OUTONLY
JANUS START DIRECTORS
</p>

In this example we set the session to mixed case with <var>*LOWER</var> to allow us to define a lower-case remote server name. Next we define the <var class="product">Janus Open Server</var> port <code>DIRECTORS</code> and associate it with a port and subsystem. The port also acts as the <var>MASTER</var> port for <var class="product">Janus Open Client</var> connections and forces upper case translation of parameter names.

We designate the remote server as a server named lights_cameras_action running on host <code>RS6000</code> at port 3037 with the site handler having <var class="product">Model 204</var> user ID <code>ICHABOD</code>. The port allows only outgoing connections. Then we start port <var>DIRECTORS</var>, making it available for connections, and reset *UPPER status.

<p class="code"> JANUS DEFINE WRITERS_CONTRACT OPENSERV 4012 -
CMD 'UTILITIES' UPCASE
JANUS DEFINE WRITERS_INHOUSE OPENSERV 4013 -
CMD 'LOGOFF' UPCASE MASTER
JANUS DEFINEREMOTE WRITERS* SCRIBBLERS SPARC2 3013
JANUS START WRI*
</p>

In the above example port <code>WRITERS_CONTRACT</code> is defined at port 4012 and <code>WRITERS_INHOUSE</code> defined at port 4013, and a remote server <code>SCRIBBLERS</code> is associated with both of them. <code>SCRIBBLERS</code> runs on host <code>SPARC2</code> at port 3013. Note that we don't specify <var>OUTONLY</var> on port 4013 but if any client attempts to connect, a <var>LOGOFF</var> command will execute, making this effectively a port for the exclusive use of <var class="product">Janus Open Client</var> applications front-ended within the <var class="product">Model 204</var> online.

Port <code>WRITERS_CONTRACT</code> however will put externally front-ended clients into subsystem <code>UTILITIES</code>, and the <var>DEFINEREMOTE</var> definition will allow the <code>UTILITIES</code> application to access the same remote server as users going out on <code>WRITERS_INHOUSE</code>. A configuration such as the one above shows how a similar Open Client access is made available to two versions of an application, a 3270 version running in the <var class="product">Model 204</var> online, and a workstation version accessing <var class="product">Model 204</var> over <var class="product">Janus Open Server</var> connections.

==References and links==
See: [[List_of_Janus_commands|Janus command list]]
[[Category:Janus commands|JANUS DEFINEREMOTE]]

JALWiccan: 1 revision

2011-07-01T00:13:34Z

1 revision

← Older revision	Revision as of 00:13, 1 July 2011
(No difference)

Admin at 00:13, 1 July 2011

2011-07-01T00:13:32Z

← Older revision		Revision as of 00:13, 1 July 2011
Line 92:		Line 92:
	</p>		</p>

	In the previous example the remote server AGENTS_SQL_SERVER is associated with port AGENTS. AGENTS_SQL_SERVER is running on a host name RS6000 at port number 3010. INONLY specifies that the port cannot be used by ''[[Janus Open Client]]'' functions. The site handler will appear as user ID &OSQ.GHOST&CSQ. and will timeout 60 seconds after the last user connection terminates (using the default TIMEOUT). Each user connecting from the remote server is thrown directly into subsystem MAILLIST by the JANUS DEFINE command.		In the previous example the remote server AGENTS_SQL_SERVER is associated with port AGENTS. AGENTS_SQL_SERVER is running on a host name RS6000 at port number 3010. INONLY specifies that the port cannot be used by ''[[Janus Open Client]]'' functions. The site handler will appear as user ID &OSQ.GHOST&CSQ. and will timeout 60 seconds after the last user connection terminates (using the default TIMEOUT). Each user connecting from the remote server is thrown directly into subsystem MAILLIST by the JANUS DEFINE command.

	<p class="code"> JANUS DEFINE PRODUCERS OPENSERV 4022 -		<p class="code"> JANUS DEFINE PRODUCERS OPENSERV 4022 -
Line 129:		Line 129:
	See: [[List_of_Janus_commands\|Janus command list]]		See: [[List_of_Janus_commands\|Janus command list]]
	[[Category:Janus commands\|JANUS DEFINEREMOTE]]		[[Category:Janus commands\|JANUS DEFINEREMOTE]]
	~~[[Category:Sirius commands\|JANUS DEFINEREMOTE]]~~

Admin at 15:02, 1 March 2011

2011-03-01T15:02:30Z

← Older revision		Revision as of 15:02, 1 March 2011
Line 7:		Line 7:

	==Syntax==		==Syntax==
	<p class="syntax"><section begin="syntax" /> JANUS DEFINEREMOTE portname remotename host -		<p class="syntax"><section begin="syntax" /> JANUS DEFINEREMOTE portname remotename host portnum [optional parms...]
	portnum [optional parms...]
	<section end="syntax" /></p>		<section end="syntax" /></p>
	<p class="caption">JANUS DEFINEREMOTE command syntax		<p class="caption">JANUS DEFINEREMOTE command syntax

Admin at 20:12, 28 February 2011

2011-02-28T20:12:02Z

← Older revision		Revision as of 20:12, 28 February 2011
Line 34:		Line 34:
	The optional parameters are shown in the following sections.		The optional parameters are shown in the following sections.

	===~~Charset~~ xxx===		===CHARSET xxx===

	This parameter specifies the character set to use for this remote port, allowing override of either the default character set or the character set specified on the JANUS CHARSET subcommand. The default character set is iso_1. CHARSET has no effect on the operation of any application in ''Model 204''. The name of the specified character set is simply forwarded to the target server for a ''[[Janus Open Client]]'' application. For further discussion, see [[JANUS CHARSET]].		This parameter specifies the character set to use for this remote port, allowing override of either the default character set or the character set specified on the JANUS CHARSET subcommand. The default character set is iso_1. CHARSET has no effect on the operation of any application in ''Model 204''. The name of the specified character set is simply forwarded to the target server for a ''[[Janus Open Client]]'' application. For further discussion, see [[JANUS CHARSET]].

← Older revision		Revision as of 20:31, 14 October 2011
Line 122:		Line 122:

	==See also==		==See also==
	[[List_of_Janus_commands\|Janus command list]]		<ul>
			<li>[[List_of_Janus_commands\|Janus command list]]
			</ul>

	[[Category:Janus commands\|JANUS DEFINEREMOTE]]		[[Category:Janus commands\|JANUS DEFINEREMOTE]]