CHAR (JANUS DEFINE parameter)

From m204wiki
Revision as of 16:01, 8 March 2011 by 198.242.244.47 (talk) (Created page with "{{DISPLAYTITLE:CHAR}} <span class="pageSubtitle"><section begin="desc" /><section end="desc" /></span> CHAR is a parameter on JANUS DEFINE, which defines and sets characteri...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

<section begin="desc" /><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 (:hdref reftxt=$SOCK_SET refid=skset.) or the Set function (:hdref reftxt=Set refid=setmeth.) 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 (:hdref reftxt=AddField refid=adfield.) or the Content method (:hdref reftxt=Content refid=content.) 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 (:hdref reftxt=XTAB refid=xtab.) setting.

The BINARY parameter (:hdref reftxt=BINARY refid=binary.) 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.