Skip to main content

Hi,

please I have this code:

05 w-string1 pic x(500).
05 w-x pic s9(04) comp.

...

call "SYSTEM" using w-string1(1:w-x)

where in w-string1 is 'bpsXmlConverter bpsdata\\SXJNMP-PK1_2017032715521837.DAT utf-8'

but in bpsXmlConverter program (it's .NET utility), when I check, how I was called it's:

bpsXmlConverter bpsdata\\SXJNMP-PK1_2017032715521837.DAT utf-8 270320174

When I debugging, just before CALL "SYSTEM" value in w-string1 is OK. And when I run bpsXmlConverter just alone, it's also OK.

Please can you help me, from where this strange number parameter comes?


#cobolnetexpress

Hi,

please I have this code:

05 w-string1 pic x(500).
05 w-x pic s9(04) comp.

...

call "SYSTEM" using w-string1(1:w-x)

where in w-string1 is 'bpsXmlConverter bpsdata\\SXJNMP-PK1_2017032715521837.DAT utf-8'

but in bpsXmlConverter program (it's .NET utility), when I check, how I was called it's:

bpsXmlConverter bpsdata\\SXJNMP-PK1_2017032715521837.DAT utf-8 270320174

When I debugging, just before CALL "SYSTEM" value in w-string1 is OK. And when I run bpsXmlConverter just alone, it's also OK.

Please can you help me, from where this strange number parameter comes?


#cobolnetexpress
I think you need to NULL terminate your input string with a x'00' after the utf-8 parameter. Or just change the storage slightly to add one after end of the string
05 w-string1.
10 filler pic x(500).
10 filler pic x(1) value x"00".

Hi,

please I have this code:

05 w-string1 pic x(500).
05 w-x pic s9(04) comp.

...

call "SYSTEM" using w-string1(1:w-x)

where in w-string1 is 'bpsXmlConverter bpsdata\\SXJNMP-PK1_2017032715521837.DAT utf-8'

but in bpsXmlConverter program (it's .NET utility), when I check, how I was called it's:

bpsXmlConverter bpsdata\\SXJNMP-PK1_2017032715521837.DAT utf-8 270320174

When I debugging, just before CALL "SYSTEM" value in w-string1 is OK. And when I run bpsXmlConverter just alone, it's also OK.

Please can you help me, from where this strange number parameter comes?


#cobolnetexpress
Great! Thats it, thanks a lot
Terms & ConditionsAccessibility statement