CMD (JANUS DEFINE parameter): Difference between revisions

From m204wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 1: Line 1:
{{DISPLAYTITLE:CMD}}
{{DISPLAYTITLE:CMD}}
<span class="pageSubtitle"><section begin="desc" />CMD 'xxx' -- Model 204 command to process upon connection<section end="desc" /></span>
<span class="pageSubtitle"><section begin="desc" />CMD 'xxx' &mdash; Model 204 command to process upon connection<section end="desc" /></span>


CMD is a parameter on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]].
<var>CMD</var> is a [[JANUS DEFINE#parmlist|parameter]] of the <var>[[JANUS DEFINE|JANUS DEFINE]]</var> command, which defines and sets characteristics of a Janus port.  
<var>CMD</var> specifies the <var class="product">Model 204</var> commands to be executed after the files and groups specified in the <var>[[OPEN]]</var> parameter are opened. Multiple commands must be separated by the word <code>AND</code>, and any command that contains blanks must be enclosed in quotes.  


This parameter specifies the ''Model 204'' commands to be executed after the files and groups specified in the [[OPEN]] parameter are opened. Multiple commands must be separated by the word "AND", and any command that contains blanks must be enclosed in quotes. Multiple commands in the CMD clause are supported in Version 6.0 and later of ''[[Sirius Mods]]''.  
<var>CMD</var> may span more than one line &mdash; continued with a hyphen (<tt>-</tt>) &mdash; but the total length of commands plus one overhead byte per command cannot exceed 255 bytes.  


CMD may span more than one line -- continued with a hyphen (<code>-</code>) -- but the total length of commands plus one overhead byte per command cannot exceed 255 bytes.  
For an <var>OPENSERV</var>, <var>SRVSOCK</var>, or <var>TNSERV</var> port, the commands specified by <var>CMD</var> specify the processing performed for each connection to the port.  


For an OPENSERV, SRVSOCK, or TNSERV port, the commands specified by CMD specify the processing performed for each connection to the port.  
<var>TNSERV</var> connections run on daemon threads, but they will usually run full-screen 3270-applications. As such, they might have somewhat different parameter or table size requirements from other applications that run on daemon threads. The <var>CMD</var> parameter, possibly along with the <var>OPEN</var> command, make it possible to set certain parameters or table sizes that might be specific to all 3270 threads and so are not set in the subsystems run by these threads.  


TNSERV connections run on daemon threads, but they will usually run full-screen 3270-applications. As such, they might have somewhat different parameter or table size requirements from other applications that run on daemon threads. The CMD parameter, possibly along with the OPEN command, make it possible to set certain parameters or table sizes that might be specific to all 3270 threads and so are not set in the subsystems run by these threads.  
The commands specified by <var>CMD</var> for <var>TNSERV</var> connections are not executed unless a trusted login is performed via the <var>[[NEWSESCMD]]</var> parameter of <var>JANUS DEFINE</var>.  


The commands specified by CMD for TNSERV connections are not executed unless a trusted login is performed via [[NEWSESCMD]]. the NEWSESCMD parameter of JANUS DEFINE.  
You can invoke a specific subsystem on a telnet server connection either with the <var>CMD</var> parameter or with the <var>[[AUTOSYS]]</var> parameter of <var>JANUS DEFINE</var>. If the user logs off and logs on again during the same connection, the <var>CMD</var> command(s) are not executed. Because of this, using <var>AUTOSYS</var> is probably preferable to using <var>CMD</var> parameters for most <var>TNSERV</var> applications.


You can invoke a specific subsystem on a telnet server connection either with the CMD parameter or with the [[AUTOSYS]] parameter of [[JANUS DEFINE]]. If the user logs off and logs on again during the same connection, the CMD command(s) are not executed. Because of this, using AUTOSYS is probably preferable to using CMD parameters for most TNSERV applications.
For <var>SDS</var> ports, the commands are executed before the port begins acting as a <var class="product>[http://sirius-software.com/maint/manlist/jsdsr.pdf Specialty Data Store]</var>. It is strongly recommended that this command be used mainly to set user table sizes and user parameters for <var>SDS</var> ports. This might be necessary because <var class="product>Janus Specialty Data Store</var> might have very different table size requirements than other applications running on an sdaemon.  


For SDS ports, the commands are executed before the port begins acting as a Specialty Data Store. It is strongly recommended that this command be used mainly to set user table sizes and user parameters for SDS ports. This might be necessary because ''[[Janus Specialty Data Store]]'' might have very different table size requirements than other applications running on an sdaemon.  
For <var>WEB</var> ports, the commands specified by <var>CMD</var> are executed after all rules are executed except the <var>ON</var> rules. The specified commands can be used to invoke an <var class="product">APSY</var> subsystem when using the <var class="product">Janus Web Server</var> [[$function API]] or to reset <var>UTABLE</var> and other parameters.  


For WEB ports the commands specified by CMD are executed after all rules are executed except the ON rules. The specified commands can be used to invoke an APSY subsystem when using the Janus Web UL API or to reset UTABLEs and other parameters.
Examples of some valid <var>CMD</var> clauses:
 
Examples of some valid CMD clauses:


<p class="code">  JANUS DEFINE MYWEB 80 WEBSERV 10 CMD WEBAPSY
<p class="code">  JANUS DEFINE MYWEB 80 WEBSERV 10 CMD WEBAPSY
Line 27: Line 26:
   JANUS DEFINE OPENXXX 1234 OPENSERV 15 OPEN FILE OPENPROC CMD 'R PROMPT 16' AND OPENAPSY
   JANUS DEFINE OPENXXX 1234 OPENSERV 15 OPEN FILE OPENPROC CMD 'R PROMPT 16' AND OPENAPSY
</p>
</p>
<p class="caption">The command only needs to be quoted if it contains blanks or special characters.'</p>
'''Note:''' The command only needs to be quoted if it contains blanks or special characters.
 
Valid for SRVSOCK or &P$SVSYB port types, this parameter is required for SRVSOCK and OPENSERV port types. This parameter is '''not''' valid on an FTPSERVER port definition.


This parameter is required for OPENSERV port types.
Valid for <var>SRVSOCK</var> or &P$SVSYB port types, this parameter is required for <var>SRVSOCK</var> and <var>OPENSERV</var> port types. This parameter is '''not''' valid on an <var>FTPSERVER</var> port definition.


==References==
==References==

Revision as of 16:49, 20 June 2011

<section begin="desc" />CMD 'xxx' — Model 204 command to process upon connection<section end="desc" />

CMD is a parameter of the JANUS DEFINE command, which defines and sets characteristics of a Janus port. CMD specifies the Model 204 commands to be executed after the files and groups specified in the OPEN parameter are opened. Multiple commands must be separated by the word AND, and any command that contains blanks must be enclosed in quotes.

CMD may span more than one line — continued with a hyphen (-) — but the total length of commands plus one overhead byte per command cannot exceed 255 bytes.

For an OPENSERV, SRVSOCK, or TNSERV port, the commands specified by CMD specify the processing performed for each connection to the port.

TNSERV connections run on daemon threads, but they will usually run full-screen 3270-applications. As such, they might have somewhat different parameter or table size requirements from other applications that run on daemon threads. The CMD parameter, possibly along with the OPEN command, make it possible to set certain parameters or table sizes that might be specific to all 3270 threads and so are not set in the subsystems run by these threads.

The commands specified by CMD for TNSERV connections are not executed unless a trusted login is performed via the NEWSESCMD parameter of JANUS DEFINE.

You can invoke a specific subsystem on a telnet server connection either with the CMD parameter or with the AUTOSYS parameter of JANUS DEFINE. If the user logs off and logs on again during the same connection, the CMD command(s) are not executed. Because of this, using AUTOSYS is probably preferable to using CMD parameters for most TNSERV applications.

For SDS ports, the commands are executed before the port begins acting as a Specialty Data Store. It is strongly recommended that this command be used mainly to set user table sizes and user parameters for SDS ports. This might be necessary because Janus Specialty Data Store might have very different table size requirements than other applications running on an sdaemon.

For WEB ports, the commands specified by CMD are executed after all rules are executed except the ON rules. The specified commands can be used to invoke an APSY subsystem when using the Janus Web Server $function API or to reset UTABLE and other parameters.

Examples of some valid CMD clauses:

JANUS DEFINE MYWEB 80 WEBSERV 10 CMD WEBAPSY JANUS DEFINE SDS204 1777 SDS 20 CMD 'R MCPU 5000' AND 'UTABLE LQTBL 1000' - AND 'R PROMPT 16' JANUS DEFINE OPENXXX 1234 OPENSERV 15 OPEN FILE OPENPROC CMD 'R PROMPT 16' AND OPENAPSY

Note: The command only needs to be quoted if it contains blanks or special characters.

Valid for SRVSOCK or &P$SVSYB port types, this parameter is required for SRVSOCK and OPENSERV port types. This parameter is not valid on an FTPSERVER port definition.

References

See: List of Janus commands | List of JANUS DEFINE parameters.