Replies

You've left out some info (OS, OS version, firewalls, where you are running CTTerm, data path, etc) but...here are some suggestions:

Does putting in wrong account/password yield same symptom?

1) If you are running CTTerm on the same box check to see if Cache Telnet server enabled, permissions good, local box firewall not interfering, Cache license appropriate/applied, etc.

2) If running CTTerm from network check above plus all applicable firewalls or network protections. Some networks may prevent old Telnet running across specific paths without opening up a hole.

3) If you are using terminal servers to old serial terminals or PCs check the terminal servers.

Tom Fitzgibbon | 3474648531 | gototomAtG...l

CLS is kept in the system globals in each namespace. With some work you could probably write a COS routine to display the CLS in a human readable format.

Tom Fitzgibbon | gototomATg...l.com

SMTP servers can have different requirements (port, SSL level, etc). You have read AOL SMTP requirements? Sometimes it requires some fiddling.

From Lifewire: Enter these SMTP settings to send outgoing email through to your AOL Mail account from any email program.

  • Incoming Mail Server: imap.aol.com
  • SMTP Outgoing Server Address: smtp.aol.com. Set the port to 587
  • SMTP Username: "user@aol.com" (or @love.com, @games.com or @verizon.net)
  • SMTP password. The password you use to log in to AOL Mail

Some ISPs block port 25, see the SMTP server specs for other ports you can use (465, 587, etc).

Code below has worked for me in the past.

Tom Fitzgibbon | gototomATg...l.com

-------------------------------------------------------------------------------------------------------

SendMail(Message,SendTo,Subject) ;send mail

s s=##class(%Net.SMTP).%New()

s auth=##class(%Net.Authenticator).%New() ; use default auth

s auth.UserName="user@domain.com"

s auth.Password="xxxxxxxx"

s s.authenticator=auth

s s.smtpserver="smtpout.secureserver.net"

s s.timezone="Local"

s s.port="80" ;for secureserver

s m=##class(%Net.MailMessage).%New()

s m.Charset="iso-8859-1"

s m.From="person@domain.com"

Send ;where to?

d m.To.Insert(SendTo)

;subject

s m.Subject = Subject

d m.TextData.Write(Message)

s status=s.Send(m)

d m.%Close()

d auth.%Close()

q status

I agree with Benjamin: VMs (and containers) are the way to make testing environments. Once you set up your VM/container structure it's easy to create/delete identical testing instances.  Obviously make sure that you carefully isolate your cloned Cache from the real world or it may start interacting with real world production.

Tom Fitzgibbon | tom@tec.today | 3474648531

If you've had any experience with packet monitors you probably should try Wireshark since it's the most widely used. Various plugins, addons are available. I've used to monitor CSP, SOAP, JSON, Ensemble and other transactional comm.

Fiddler is a bit more user friendly but once you're in the packet details you have to spend time deciphering no matter what monitor.

Tom Fitzgibbon | gototomATG...l | 3474648531

As Robert indicates Shadowing and Mirroring on the Cache level are the ways to go.

Shadowing creates a copy of the master via journal Sets, Kills and $Bit. It's slower to sync and, I think, more prone to desync issues.

Mirroring is fairly immediate sync, offers more flexibility and features, like automatic failover. It's pretty awesome.

Tom Fitzgibbon | gototomAtG...l | 3474648531