CHAR (JANUS DEFINE parameter): Difference between revisions
m (1 revision) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:CHAR}} | {{DISPLAYTITLE:CHAR}} | ||
<span class="pageSubtitle"><section begin="desc" /><section end="desc" /></span> | <span class="pageSubtitle"><section begin="desc" />Turns on character translation on a socket port<section end="desc" /></span> | ||
CHAR 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]]. | CHAR 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]]. | ||
This parameter requests ''[[Janus Sockets]]'' to translate strings (sent and received with ''[[Janus Sockets]]'' functions or methods) between the internal representation within ''Model 204'' (EBCDIC) and the character representation used by the remote end of the connection. | This parameter requests ''[[Janus Sockets]]'' to translate strings (sent and received with ''[[Janus Sockets]]'' functions or methods) between the internal representation within ''Model 204'' (EBCDIC) and the character representation used by the remote end of the connection. | ||
This translation can be disabled by one of the following: | This translation can be disabled by one of the following: | ||
<ul> | <ul> | ||
<li>Setting a socket to BINARY using [[$Sock_Set]] or the Set function of the Socket class | |||
<li>Setting a socket to BINARY using $ | |||
<li>Using the BINARY option on an individual receive or send $function or Socket class method | <li>Using the BINARY option on an individual receive or send $function or Socket class method | ||
<li>Using an option of the AddField method | <li>Using an option of the AddField method or the Content method of the HTTP Helper | ||
</ul> | </ul> | ||
Individual strings can always be translated using $SOCK_TRAN_IN or $SOCK_TRAN_OUT, or their Socket method counterparts, TranIn or TranOut. | Individual strings can always be translated using $SOCK_TRAN_IN or $SOCK_TRAN_OUT, or their Socket method counterparts, TranIn or TranOut. | ||
If the CHAR setting is in effect, translation is determined by the tables defined by the socket's XTAB | If the CHAR setting is in effect, translation is determined by the tables defined by the socket's [[XTAB]] setting. | ||
The BINARY parameter | The [[BINARY]] parameter is the opposite of CHAR. CHAR is the default. | ||
Valid only for CLSOCK and SRVSOCK ports. | Valid only for CLSOCK and SRVSOCK ports. | ||
Revision as of 22:29, 10 March 2011
<section begin="desc" />Turns on character translation on a socket port<section end="desc" />
CHAR is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port. See the List of JANUS DEFINE parameters.
This parameter requests Janus Sockets to translate strings (sent and received with Janus Sockets functions or methods) between the internal representation within Model 204 (EBCDIC) and the character representation used by the remote end of the connection.
This translation can be disabled by one of the following:
- Setting a socket to BINARY using $Sock_Set or the Set function of the Socket class
- Using the BINARY option on an individual receive or send $function or Socket class method
- Using an option of the AddField method or the Content method of the HTTP Helper
Individual strings can always be translated using $SOCK_TRAN_IN or $SOCK_TRAN_OUT, or their Socket method counterparts, TranIn or TranOut.
If the CHAR setting is in effect, translation is determined by the tables defined by the socket's XTAB setting.
The BINARY parameter is the opposite of CHAR. CHAR is the default.
Valid only for CLSOCK and SRVSOCK ports.
References
See: List of Janus commands | List of JANUS DEFINE parameters.