I am setting up a new Caché instance and I have managed to configure it where Caché username/password is required to initiate the Caché session:

csdfalsdkfjf@fra23e234sco:/opt/labmed/test/test81/proc$ csession cache1

Node: frxxco, Instance: CACHE1

Username:

I cannot find the setting in the management console that allows for unauthenticated login to a Caché session. Any help is much appreciated.

I wanted to share a little tidbit which is in the Studio documentation (http://docs.intersystems.com/cache20152/csp/docbook/DocBook.UI.Page.cls?...) but many people who have been using the InterSystems Studio for a long time missed the addition of this *very* useful feature, and every time I mention this to an audience I see at least one face light up because of how excited they are to learn about it!

Within Studio, the Output pane (View -> Output) is actually misnamed. It is actually an Input/Output window which can be used to run Caché ObjectScript commands!

hi, everybody!

i wanna connect to a remote server through Terminal.

after i add a server in [Preferred Server] and click the server name( [Remote System Access]->[Terminal] -> server name)

i got an Error dialog telling me that:

Failed to establish security context.

Reason:(-2146893042, 0x8009030e)No credentials are available in the security package

so do i miss some configuration?

Grateful for your help!

I use DataGrip (JDBC client) to query Caché server via JDBC.

The problem I encountered, is that if I wait 10 or more minutes between queries I get an error:

[08S01][461] Communication link failure: Socket closed

To fix that I need to disconnect and connect to server again. Is there a JDBC timeout setting somewhere I can change?

Hello,

I'd like to know if there is an easy way to get result from a $ZF(-1) into a varaible to use it in HS code.

Thanks

or "Didn't you say you would cover Persistent Objects in Part 5, Chris?"

Yes, that was the plan. This is a pretty important topic, so it get's its own Article

Up until now, we've display widget JSON that has been created by a basic loop. Clearly this isn't of much value. Now we have our stack connected together, and we can see that the data is flowing to the Welcome page, it's time to complete the stack and start feeding our service from "real" data.

Hey Community,

Ready for the next contest? We are glad to invite you all to the 19th InterSystems online programming competition:

🏆 InterSystems Globals Contest 🏆

Duration: March 21 - April 10, 2022

In prizes: $10,000

Hello.

For debugging purposes I sometimes need to display stack information to the current device or save it (to a global for example).

There is this snippet offered in documentation:

ClassMethod StackToDisplay()
{
    For loop = 0:1:$Stack(-1) {
        Write !, "Context level:", loop, ?25, "Context type: ", $Stack(loop)
        Write !, ?5, "Current place: ", $Stack(loop, "PLACE")
        Write !, ?5, "Current source: ", $Stack(loop, "MCODE")
        Write !
    }
}

And to save stack to a global there's always an exception method:

Hello!

I'm trying to get files from FTP server. Bellow my code:

I would like to remove the login requirement, such that when

the Terminal option on the Cache Cube is clicked, the session goes directly

to the mumps prompt.

Also, how can I change terminal user's login password.

Hi guys,

I'm working on a project with my client.
They have a visit table which has about 7,000,000 records. The table is used in a random search page witch holds 20+ conditions to be combined.
The table is defined as below:

In the previous article, we talked about the flow of data to request the test and receive the results of the requested test. Now let's talk about one of the most important messages of HL7v2 standard.

Every time a receiving application accepts a message and consumes the message data, it is expected to send an ACKnowledgement (ACK) message back to the sending application. The sending application is expected to keep on sending a message until it has received an ACK message. It is done to inform the sending application that its message was successfully received, that it is (not) valid in accordance with HL7 rules and, if it is compliant, that it will be processed at some point.

I have the following class:

This announcement is to inform clients about changes in our 2016.2 and 2016.3 field test programs.

The 2016.2 field test has been extended in order to address important syntax changes related to JSON. Simply stated, the JSON syntax introduced in 2016.1 had several inconsistencies that we did not want to perpetuate. This is now addressed and the updated 2016.2 field test will be published today. Concurrently, the syntax changes and guidance for developers will be posted on the Developer Community shortly. JSON is critically important to our Caché roadmap.