JANUS START: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (1 revision)
mNo edit summary
Line 1: Line 1:
{{DISPLAYTITLE:JANUS START}}
{{DISPLAYTITLE:JANUS START}}
<span class="pageSubtitle"><section begin="desc" />START<section end="desc" /></span>
<span class="pageSubtitle"><section begin="desc" />Start a Janus port<section end="desc" /></span>


This makes a port available for connections; it is put into the START state.


==Syntax==


This makes a port available for connections; it is put into the START state.
==Syntax==
<p class="syntax"><section begin="syntax" /> JANUS START portname
<p class="syntax"><section begin="syntax" /> JANUS START portname
<section end="syntax" /></p>
<section end="syntax" /></p>
Line 11: Line 11:
</p>
</p>


Where 'portname' is the name of the port(s) to start.


Where 'portname' is the name of the port(s) to start.<blockquote> The JANUS DEFINE command must be used to define the port before it is started with JANUS START. Also, if the port is defined to use Secure Sockets Layer (SSL) or Transport Layer Security (TLS) for secured communications, you are prompted for the password that decrypts the private key for the certificate specified on the SSL parameter of this port's DEFINE command.</blockquote>
The [[JANUS DEFINE]] command must be used to define the port before it is started with JANUS START. Also, if the port is defined to use Secure Sockets Layer (SSL) or Transport Layer Security (TLS) for secured communications, you are prompted for the password that decrypts the private key for the certificate specified on the SSL parameter of this port's DEFINE command.


In the following example, all ports whose names begin with ACCTS are made available for incoming connections, and any remote servers associated with those ports are made available for outgoing connections. For any of these ports whose DEFINE commands did not include an ALLOCC, the control blocks are built in SPCORE.
In the following example, all ports whose names begin with ACCTS are made available for incoming connections, and any remote servers associated with those ports are made available for outgoing connections. For any of these ports whose DEFINE commands did not include an ALLOCC, the control blocks are built in SPCORE.
<p class="code"> JANUS START ACCTS*
<p class="code"> JANUS START ACCTS*
</p>
</p>


 
[[List of Janus commands]]
[[Category:Janus commands|JANUS START]]
[[Category:Janus commands|JANUS START]]
[[Category:Sirius commands]]
[[Category:Sirius commands]]

Revision as of 16:05, 2 March 2011

<section begin="desc" />Start a Janus port<section end="desc" />

This makes a port available for connections; it is put into the START state.

Syntax

<section begin="syntax" /> JANUS START portname <section end="syntax" />

JANUS START command syntax

Where 'portname' is the name of the port(s) to start.

The JANUS DEFINE command must be used to define the port before it is started with JANUS START. Also, if the port is defined to use Secure Sockets Layer (SSL) or Transport Layer Security (TLS) for secured communications, you are prompted for the password that decrypts the private key for the certificate specified on the SSL parameter of this port's DEFINE command.

In the following example, all ports whose names begin with ACCTS are made available for incoming connections, and any remote servers associated with those ports are made available for outgoing connections. For any of these ports whose DEFINE commands did not include an ALLOCC, the control blocks are built in SPCORE.

JANUS START ACCTS*

List of Janus commands