I am new to using API's and have a problem regarding the data structure associated with the rerceiver value for the Retrieve Job Description API ( 'QWDRJOBD' ).
The API definition in the ISeries Information Center lists the fields returned as offsets in a single data structure.
The first five are:-
Binary (4) Bytes Returned
Binary (4) Bytes Available
Char (10) Job Description Name
Char (10) Job Description Library Name
Char (10) User Name
Funny thing is that when I call the API the results are offset by a further four bytes that do not appear in the definition. My data structure looks like this:-
DRETURN_VALUE DS
D D1B1 4B 0
D D1B2 4B 0
D D1JOBD 10
D D1JOBDL 10
D D1USER 10
The D1JOBD, D1JOBDL and D1USER are all offset by four bytes
and so I have had to change my data structure to look like this:-
DRETURN_VALUE DS
D D1B1 4B 0
D D1B2 4B 0
D D1B3 6B 0
D D1JOBD 10
D D1JOBDL 10
D D1USER 10
Why is this?
Am I misunderstanding the lengths og Binary fields?
The API definition in the ISeries Information Center lists the fields returned as offsets in a single data structure.
The first five are:-
Binary (4) Bytes Returned
Binary (4) Bytes Available
Char (10) Job Description Name
Char (10) Job Description Library Name
Char (10) User Name
Funny thing is that when I call the API the results are offset by a further four bytes that do not appear in the definition. My data structure looks like this:-
DRETURN_VALUE DS
D D1B1 4B 0
D D1B2 4B 0
D D1JOBD 10
D D1JOBDL 10
D D1USER 10
The D1JOBD, D1JOBDL and D1USER are all offset by four bytes
and so I have had to change my data structure to look like this:-
DRETURN_VALUE DS
D D1B1 4B 0
D D1B2 4B 0
D D1B3 6B 0
D D1JOBD 10
D D1JOBDL 10
D D1USER 10
Why is this?
Am I misunderstanding the lengths og Binary fields?