I’ve written a Natural subprogram and generated an IDL from it. It brings back data from my Adabas file just fine, with one small problem. Nine of the records have descriptor values that begin with a space.
“(space)ALTOONA SHOE DEPOT” exists at the beginning of the file and “ALTOONA SHOE DEPOT” as a nearly-duplicate record following “AARDVARK BEAUTY AND PLUMBING SUPPLIES”, which itself follows all of the records with a leading space in the descriptor.
The IDL tester is showing that the leading space has been trimmed in the subprogram output. This is a problem when I try to get back to the “ALTOONA SHOE DEPOT” because without the leading space my read statement starts with the other ALTOONAs and not at the extreme beginning of the file.
I’ve run my subprogram via CALLNAT in TN3270 emulation to verify that the leading space is preserved on the Natural side. The IDL tester and the soap web service I generated show that the leading space to be stripped or trimmed from the field somewhere after the callnat for the RPC.
Where exactly is this happening, and how can I turn this arguably desirable TRIM feature on or off as needed? I’ve stumbled through all of the documentation I could Google, but so far I have found no reference to this trimming or stripping feature or where it might be happening.
I should mention that I did all of this on NaturalONE, and that the data and subprogram reside on an IBM mainframe. My Natural Administrator talked me through defining my RPC environment to access the mainframe subprogram in the IDL. I am very new at all of this, and am timidly stepping off of the green-screen for the first time.
Thank you much for any enlightenment you can provide!