Re: terminal without telnet

"One of those serial ports can be a modem,
and I can get PDOS/386 to emulate a
modem"

Why are you reinventing the wheel?

This already exists....

0020      2703 <http://hercules-390.github.io/html/hercconf.html#2703>
   lport=32003 dial=IN lnctl=tele2 uctrans=yes term=tty skip=88C9DF
iskip=0A
0023      2703 <http://hercules-390.github.io/html/hercconf.html#2703>
   lport=3780 rhost=localhost rport=3781 dial=no
0045      2703 <http://hercules-390.github.io/html/hercconf.html#2703>
   lport=32003 dial=IN lnctl=ibm1 term=2741 skip=5EDE code=ebcd

*Communication Line - TTY*

(Preliminary 2703 TELE2 TTY Support)

Describes a 2703 Telegraph Terminal Control Type II (TTY 33/35)
stop/start line, providing access to the Host OS via a standard TELNET
client. To the host OS the line emulates an asynchronous TELE2
connection. The communication is emulated over a TELNET connection.

The following options define the line emulation behaviour:

LPORT=*port number*

Specifies the TCPIP port to listen on for incoming TCP calls.

DIAL=IN

Specifies that this line is for in-bound calls. Required.

TERM=TTY

Specifies that this definition is for a TTY port. Required

*Additional 2703 Communication Line options*

The following are some additional options that may also be specified
for 2703 devices:

APPEND=*hh..*.PREPEND=*hh...*

Specifies up to four bytes (in S/370 channel format, not ASCII) to be
prepended or appended to input line data received from terminals
before they are sent to the guest OS. Typical use is to add Circle D
and C around each input transmission (2741's for APL\360).

BINARY=NO | YES

Negotiate to telnet binary mode if TERM=RXVT4APL.

BS=DUMBBREAK=DUMB

Backspace and break key handling option.

When using windows telnet it is recommended to always use BS=DUMB and
BREAK=DUMB.

CODE=EBCD | CORR | NONE

Specify code=ebcd for EBCD, code=corr for correspondence code, or
code=none to disable all translation. The code= option applies to 2741
mode only.

CRLF=YES | NO

Option to map 2741 NL to TTY CRLF sequence.

CRLF2CR=YES | NO

Remove LF that immediately follow CR.

EOL=*hh*

Specifies the ASCII byte value that, when received, marks the end of
the input line. The default is EOL=0D.

ISKIP=*hh...*

Specifies up to four ASCII bytes that are to be suppressed during
input processing.

KA=NO | *(idle,intv,count)*

Defines the TCP/IP keepalive settings for this line's connections.
Refer the the CONKPALV
<http://hercules-390.github.io/html/hercconf.html#CONKPALV> statement
for details.

LNCTL=TELE2 | IBM1 | BSC

Specifies the type of communications line being defined.

For asynchronous communications lines specify LNCTL=TELE2 if TERM=TTY
or LNCTL=IBM1 if TERM=2741. For binary synchronous (BSC) lines specify
LNCTL=BSC.

SKIP=*hh...*

Specifies "garbage" code points (either byte-reversed ASCII for
TERM=TTY or correspondence code/EBCD for TERM=2741) that are to be
suppressed in output processing, thereby allowing distinct lists to be
used for different terminal types.

SENDCR=NO | YES

Send CR back to terminal when input line received.

SWITCHED=IN | OUT | INOUT | NO

Switched is just a synonym for the DIAL
<http://hercules-390.github.io/html/hercconf.html#DIAL> option.

TERM=TTY | 2741 | RXVT4APL

Specifies the terminal type. Use RXVT4APL for 8-bit and character
translation in 2741 mode.

UCTRANS=YES | NO

Enable automatic translation to uppercase.


http://hercules-390.github.io/html/hercconf.html

Joe

On Sun, Apr 7, 2019 at 10:56 PM kerravon86-/[email protected] [hercules-390] <
[email protected]> wrote:

>
>
> ---In [email protected], <kerravon86@...> wrote :
>
> > Looking at the Hercules source code, it
> > appears that Hercules first accepts a
> > TCP/IP connection and then does telnet
> > negotiation and only then does it go
> > looking for the 1052 definition. So I
> > can't just add a "notelnet" option to
> > the 1052 like I intended.
>
> I have thought of another solution. If the
> console port is 1052 instead of the
> normal 3270, I can put code into
> Hercules to make it bypass the telnet
> negotiation, so that I can add
> straightforward serial ports to Hercules.
>
> One of those serial ports can be a modem,
> and I can get PDOS/386 to emulate a
> modem.
>
> Then I can write BBS software on the
> mainframe (PDOS/3x0 or MVS).
>
> BTW, modifications to HERCULES in the
> hope that other forks will adopt them too
> (or do them first so that I can copy them)
> is definitely on-topic in the HERCULES
> group.
>
> BFN. Paul.
> 
>