A REPL call returned a status code of 'DJ' even after a succesfull GHU call for the same segment.
We checked the logs and found a checkpoint b/n the GHU call and the REPL.
Both these calls are a made using a macro IM300DYN in a BMP.
Is there any call made using the same DB-PCB mask (which was used for issuing GHU and REPL calls) between the two GHU and REPL calls.If so then this will definatley give you DJ status code.
Joined: 07 Nov 2005 Posts: 1143 Location: The Netherlands at Hole 19
I'm sure you checked the manual out but the cause must be one of below:
Quote:
Explanation
The program issued a DLET or REPL call that was rejected because the segment was not currently in hold status. Some possible reasons for this status code are:
The segment had not been previously retrieved with a Get Hold call.
The segment was already deleted using this PCB. After one Get Hold call, multiple REPL calls or a DLET call following a REPL call are valid, but multiple DLET calls are not.
The segment was obtained using a secondary index as the processing sequence. A subsequent DLET or REPL call using either this PCB or another PCB within the PSB caused the current secondary index entry for this PCB to be deleted.
A checkpoint call was issued following the Get Hold call and preceding the REPL or DLET call.
A rollback call was issued following the get hold call and preceding the REPL or DLET call.
Check your module and if you can't find it post the call structure so we can help.
I actually wanted to know if the IM300DYN which is a macro responsible for the auto checkpoint is used in other shops .
I could not decipher this macro and was hoping IM300DYN is used by other shops as well.
I cannot post the call structure owing to strict security requirements.
Joined: 23 Nov 2006 Posts: 8726 Location: 221 B Baker St
Hello,
Quote:
I actually wanted to know if the IM300DYN which is a macro responsible for the auto checkpoint is used in other shops .
It might have been helpful if you mentioned this was your actual question in the original post
Quote:
I cannot post the call structure owing to strict security requirements.
That will make it much more difficult for someone to help. . . I've seen a lot of data that needed security, but don't recall the bit of code that makes the call needing to be protected. . .
Joined: 07 Nov 2005 Posts: 1143 Location: The Netherlands at Hole 19
If you got a dump at the end of it the last number and types of DLI-calls should be found. May be some other application killed your HOLD by using a command code.
