scottklement.com

Wow... I don't know. I'll attach my complete program and maybe there is something else going on there that you see. I'm writing to a flat file called ATDRCVWA that is 350 characters long.

This is a first draft so don't laugh too hard!

Hey Scott, I think you told me about the EXPROPTS(*ALWBLANKNUM) before and I do have it in my CTL-OPT specs. I'm getting the reason code of 5. I'm going to change that currentLaborRate to character and see if that makes a difference. This company has been notorious for sending me examples of the JSO...

I had this issue with one program and thanks to JonBoy49 was able to get past it. I'm now getting the same error but it has a little different twist to it. I'm using a handler due to the size of the incoming JSON. Here is my DS: dcl-ds REPAIRINGOUTLETRECORD_t qualified template; REPAIRINGOUTLETBUSIN...

I think what is really throwing me is the "dim()". For the procedure it is showing this: item likeDS(REPAIRINGOUTLETRECORD_T) Dim(1) Const; There may be over 100 outlets now and more to come later. Same for the other arrays in the JSON data. There is no num_REPAIRINGOUTLETRECORD on the tem...

Jon, This got put on the back-burner for a while but now I'm back at it. Still a little confused on where my "dcl-ds" definitions of the json I'm "reading" goes when using the %HANDLER. I really didn't know what you meant when you said "<snip out definitions>" or the &q...

I have my DATA-INTO data structure created like this: dcl-ds jsonDoc qualified; STATUS varchar(10) inz(''); MESSAGE varchar(50) inz(''); INTERFACENAME varchar(50) inz(''); num_BATCHCLAIMRESPONSE int(10) inz(0); dcl-ds BATCHCLAIMRESPONSE dim(150); dcl-ds CLAIMINFO; TRACKINGNUMBER varchar(10) inz('');...

Thank you!!!!

Still a little confused... In my current program I roll through the REPAIROUTLETRECORD array as follows (condensed version): for a = 1 to advicedoc.creditadviceheader.num_repairingoutletrecord; for b = 1 to advicedoc.creditadviceheader.repairingoutletrecord(a). num_workinprogressclaimsrecord; clear ...

Scott... yeah I knew I was in trouble with size when I saw that error. Just did not have a clue what the solution(s) was. Jon has given me something to chew on for a bit. Thanks to both for the input on this. I'm still getting my feet wet but this project is teaching me a bunch!

I needed to change some of my DIM values due to the number of elements being returned. Now I'm getting this error: ============================================================ *RNF0376 30 13 001300 Total length 23473050 of data item REPAIRI... exceeds 16,773,104 bytes. 109 end-ds; *RNF0501 20 8 0008...