Documentation indicates *obj/json was implemented last year: PxPlus 2025.

We're finally moving off 2018 (v15.10) ourselves soon, and will be glad to have the various new objects and tools available.

How about creating a PDF and downloading it?

Global variables are only active within a session, not between sessions.

Have you tried starting with numeric values to convert to Boolean? Would this work?

DEF OBJECT v,"*VARIANT"
v'val=1
v'type$="B"
PRINT v'val
-1
v'val=0
v'type$="B"
PRINT v'val
0

Have you tried passing "true" or "false" instead of 1 or 0?

Registration ran fine.

Has the program started? It's been about 1/2 hour since scheduled start, and still in the waiting room.

The client (WindX) is the client. The server (Linux, Unix, Windows, etc.) is the server. One side of the client-server pair can talk with the other side, regardless of the mix.

Caveat: If you have system calls to one type of server (e.g., Linux), they may need to be modified or changed to retrieve the desired information from another server (e.g., Windows).

This probably doesn't have a bearing on the situation, but do you have <CR> characters with the <LF> where POSTMAN does not?

The downloads only seem to have updates for Windows and WindX. Do the updates affect any of the other builds?

It seems to follow the same search logic for non-exename ("mystuff.ini") files as well, instead of the prefix sequencing.

After resetting a few things, including restarting a new session, it looks like all is working as documented.

(Still curious about the default path, though...)

Presuming you have confirmed the source of the transmission sent it properly...

There is a phenomenon that is pretty rare earthside, but seems to happen more commonly outside the atmosphere: cosmic ray bit-flipping. The 64 value change suggests that, as it's just a single bit in the byte. If it happens consistently at the same character, that might also suggest a memory error or failure of some sort.

Not sure what you're referring to with "the R asc 54 will be asc 12", as "R" is ascii 82.

We're looking at using an INI file on our Linux server for some startup information. The documentation indicates the file spec can include a path, but that doesn't seem to be the case. It also doesn't look for the file in the same directory as the executable, which is what we would expect if no path is specified. It's actually in the user launch (home) directory. (We've got that part under control, btw)

Is there something wrong in the usage? The documentation? Other? We're using v15.10 (I know...) on RHEL 7 through WindX.

If you're not adding it in there (accidentally?), then I'm not sure what else it could be.
Are you including images that might overflow the column size?

Looks like it's space-padded. Remove those and "..." should go away.