hi sebastien,
thanx for you advice. i will have job names like
SIM_JOB_READ, SIM_JOB_UPDATE, SIM_JOB_GSMALGO,... i am a bit unsure about the
path array. i always thought that each EF has a unique ID. the DF where it is
located, can be determined by the first byte of the EF ID. but if it is possible
to have a sim with multiple DFgsm, then a path is required of
course.
for PIN handling, i
will use result codes that gives cause of an error. if a PIN is required
(to read the IMSI for example), the error code would show that. then the sim
reading process prompts for PIN. the SIM can be unlocked ("enabled") by a
message like SIM_JOB_ENABLE_CHV1.
outgoing data (UPDATE) is located behind the header.
incomming data is also located behind the header when the job returns (callback
fn is called). but the READ job must be
triggered.
when my code must deal with record types, i will expand
the header. i will create the API step by
step.
regards
andreas