We're still upgrading many of the program from our legacy system which uses explicit IOLISTs in the programs. As we update file definitions in Nomads, we also need to update some of these IOLISTs. To help, we've got a program that runs through the Nomads Data Dictionary and creates an IOLIST statement for the defined files, including non-normalized variants. These are loaded out to a line-numbered text file, then run through "*pg.cnv" to convert to a tokenized program.

Trying to run it today, I get an Error #19: Program size too large. The program itself is only about 74K. But is there a limit on the number of variables or the size of the variable table? From what I see, we've got about 3200 different variable names defined in the program (before it stopped accepting more). The program itself consists of !Comments and IOLISTs.

Any insights would be appreciated. Thank you!

I've got a grid with all cells locked except for 2 non-adjacent columns. If I change a value and Tab out, it moves to the next cell. If I don't change the value and Tab or Enter, it moves to the next cell. But if I change a value and Enter out, it ALWAYS moves to the next control, not the next cell in the grid. I've set the 'TabMode and 'EnterMode properties' values to everything, but it's still the same.
Also, %Nomads'Enter_Tab=1.
Am I missing something? I'd like the Enter on a changed cell in a grid to work the same as a Tab.

I've got a file with a secondary key of:
PO_Date/d + PO_Num + Cust + ShipTo + Seq

I can read directly through the file with no problems. But if I want to grab the first entry in a group and skip the rest of the Seq values, I issue:
read (F,key=PO_Date$:PO_Num$:Cust$:ShipTo$:$FF$)

It always goes to the end of file at this point. The file is created properly, with the first field descending and the remaining ascending. Am I missing something?

Thanks, all!

When defining arrays in the Data Dictionary, the field "number" on the main grid doesn't reflect the number of entries in the array (it only counts 1), whereas a single variable with multiple fields will adjust the count for all of them. When printing the formats, however, the field count is represented properly in both cases.

I'm thinking this is just an oversight, but wanted to be sure I'm not missing something.

Thank you!

I'm creating a temporary text file so it can be completely done before dropping it into the final destination directory for export. This time, I'm printing the lines to a *memory* file. However, when I try:

create file OFile$ from (OFile)

to create the disk file from the memory file, it throws Error #13. Is this appropriate? Do I have to create a REAL file to be copied?

Thanks in advance!

According to the documentation, we can get detailed file information by opening a directory with opt="+INFO". This provides:

• File name
• File type ("F" for file, "D" for directory)
• File size in bytes
• Date created
• Date last modified
• Date last accessed

I'm presuming this is the order the data comes back in. If that's the case, how can I get a Creation date that's after the Last Modified date?

Thanks for any clarifications.

It seems like the pgm() function only allows a line NUMBER for a statement reference, not a LABEL.
It also seems like it's the only operation in PxPlus (besides AUTO) that requires a line number and will not permit a label.
Does anyone know if this will ever change? Or does anyone knows a simple way to retrieve a line based on the label, rather than the number, without actually scanning through the program (which I can do but prefer not)?

Thanks in advance!

Stay safe out there!

Is there a way, other than AUTOEXEC.BAT or PxPlus.ini, to set the value of FID(0) on the client before establishing a WindX connection through SimpleCS using .windx files?

Thanks in advance!

  Welcome to 2021!

It looks like we all survived 2020. Congratulations!

Let's have an outstanding and prosperous year!

We've just upgraded from v13.10 to v17.10 (YAY!). We created a process to go through to update all of our client PCs at locations around the country. Installations ran fine.
Until this particular laptop.
I went through the usual routine, but when I got to the point of testing the connection, I got an Error 61 (see attached). I tried uninstalling/reinstalling, to no avail. Looking through other posts, I tried to access WindX Security from the underlying PxPlus window, but it's not there to reset.
Does anyone have any suggestions?
Thanks in advance!

We're upgrading from v13.10 to v17.10. Our standard printer selection window has several DROP_BOXes on it. They are marked with "Signal on Exit" and "Automatic (Signal All Changes)". On v13.10, when a key is pressed to select an option, the on-Select Logic is triggered. Not so on v17.10. We have to actually exit the control. Has there been a change? Is there a setting I'm missing?
Thanks, all!

Since migrating from BBx a couple of years ago, the users on the system love the Viewer. However, they hate that they can't copy text from the viewer to paste into Excel, Word, whatever.

Does anyone have any insights into a text-oriented Viewer alternative that would allow that? Currently, we're only outputting basic text (with some occasional bold modifiers); no 'text' or other mnemonics.

Thanks, all!

We're upgrading from PxPlus v13.10 on Linux Redhat 5 to v17 (with a temporary serial#) on Redhat 7, which is on a completely new server. On my client PC, I've got WindX clients installed for v14.00.0001, 15.00.0000, and 17.00.0000. I'm connecting to the new server using SimpleCS through a .windx file. When I check tcb(88), I get 13, not 17.
Any ideas?
Thanks!

Is there a way to prevent a tab on a folder from being created based on Pre-Display factors? Example: Prevent the tab from being created based on whether contingent files exist. If the file(s) exist, create the tab, else skip it.
Thanks!

v13.10 almost on v17
Linux RH

I noticed the manual page on Link File Extensions that may help us in future upgrades. We're in the process of a big upgrade from v13 (*nthost/*ntslave) to v17 (SimpleCS), with a server simultaneous upgrade. Having about 100 user PCs across the country, we'd like to minimize the manual intervention needed, at least in the future.

Has anyone used this feature? Does is work well for you? The page also mentions the WindX Connection Manager, with a link to usage instructions, but I don't see how to launch it. Pointers?

Thanks all!

While we can get where we are when outputing to a serial file by checking KEC() for the file, is there a way to determine how many characters have been sent to a piped channel? If I open (ch)"|process_prog...", can I know how much went out before I close (ch)?

Thanks!

We're (finally!) upgrading our system from PxPlus v13 to v17. Much of what we have is still legacy character-based. However, the panels we have developed seem to throw Error #88 most of the time. I know there were some changes over the versions. Is there something we need to do to get things working right?

I've tried to use CREATE FILE across a WindX connection, but it doesn't seem to work:

create file "[wdx]C:\Users\James\Documents\Foo.pdf" from "/tmp/Foo.pdf"

generates Error #12. If I open the file and try:

create file "[wdx]C:\Users\James\Documents\Foo.pdf" from (1)

it generates Error #13.

I'm guessing that this is not part of the current design. If not, could it be considered for the future?

Is there a way to programmatically Hide/Show specific Query columns? Rather than have 2 or more separate queries, we would like the program to be able to identify any columns different from standard.
Thanks!

We're going through the process of upgrading our legacy system to modern times. WAY back, there was a field count limit to files, and we've still got a number of "master files" that are split between 2 or 3 actual files with similar names. We're defining each of these in the Nomads Data Dictionary.

When we do get to the point of being able to combine the component files into a single master file record, is there a way within Nomads to blend the files? E.g., Copy the primary Customer Master record to a new file, then add the fields from the secondary (and tertiary, etc.) file to the end of the new file. I know the fields can be copied out to the Global Dictionary and back in, but is there some other method that could preserve the field sequencing so we can minimize the manual intervention?

Thanks for your thoughts!