scottklement.com

Thanks Scott. We are just going to 7.5 and installed it on our test LPAR and were running some tests which I was not a part of. We are very conservative letting a release be out for a while before we upgrade. It takes over a year to perform a complete upgrade as we have over 60 LPAR's.

My boss just told me that XML parsing is no longer supported by IBM in 7.5. Is that true? Does that mean that IBM is going to treat XML-INTO and DATA_INTO like SEU and not evolve them? I know IBM won't drop these operation codes from RPG. Is it fair to say that the expectation from IBM is that softw...

Agreed. Thank you so much jonboy.

The hundred year date field is 5 digits (42109) and the time field is 6 digits (170931).

It does not contain HHMMSS. It's just a number. Here is what the 2 fields values are: 100 YR TRANS DATE TRANS. TIME 42,109 170,931 42,109 171,058 42,142 111,027 42,254 31,357 42,254 35,251 42,254 40,432 42,254 40,915 42,444 75,103 42,444 80,958

I have a 5 digit field that contains a 100 year date (Number of days difference between the current date and 1899-12-31) and a 5 digit time field (HHMMSS) and I need to convert them to an *ISO timestamp. They are in a a very old file. How would I do that? Thanks.

This is the fourth HTTP service we have created that processes JSON strings. The other three run fine. This one does not. I'm currently testing it through SoapUI 5.7.0 until the .Net app is ready. When I start the HTTP service and I post a request it is consumed by the program correctly and returns ...

I have the code for an external DS below that doesn't covert to free format. I just completed converting a 4000+ line program to Free except for this DS. I know Scott sometimes complains about the code looking sloppy. I put it in the code /code block. Not sure what else to do. D CRSSTL E DS EXTNAME(...

Okay I can use iconv(). I have the example code for it. Thanks Scott.

We use QDCXLATE to convert ASCII to EBCDIC for JSON string that come through a web service. It doesn't convert the JSON brackets [ ] correctly. We tried both QEBCDIC and QTCPEBC and it did not work. Got like a '?' instead. We are trying now to use CCSID(1208) on the JSON string to see if that works....