Unless something has changed with this new functionality, there's no
easy way to tell if a command sent via STRPCCMD has failed. Therefore,
sending a longer command and checking if it bombs isn't going to work..
Also, I don't like the idea of finding out which emulator you are
communicating with... what happens when other emulators increase their
STRPCCMD size now that such a feature is possible? Keeping a hard-coded
list of emulators and the sizes they support is not a good solution
here... even if it were possible, which I don't think it is.
The way STRPCCMD works under the covers is by sending a
specially-formatted screen, and the emulator sees this particular screen
and instead of showing it to the user, extracts the command and runs it.
It'd be nice if an API like QsnQuery5250 could tell us the max length of
a STRPCCMD -- but unfortunately, I'm pretty sure that adding
functionality like that would require changes to all existing emulators.
On 8/21/2015 7:23 AM, DrFranken wrote:
Try running a command that is 124 characters and see if it bombs?
I don't have such a command off the top of my head but it seems like you
could concoct something that would end up telling you that you can go
past the old 123 char limit.
- Larry "DrFranken" Bolhuis