I am perhaps not understanding the scenario, but let me point out some things Nothing is shown about the input to the function (i.e., your setting of "ADDINFO" and "DELINFO"). No conclusion can be reached about what happened since there is no way of knowing if the input is correct. Capture/show the data that comes "in" and also the data that "came out" for the ADDs and DELETEs.. I surely hope this is a test system. It is almost never knowable that it is safe to "delete". An unsafe delete is a system integrity error. Somehow you have to know that there is no work unit currently traversing (or might traverse in the future, having saved the address) the module in question.
For what it's worth, LpmedModprobFunction is part of LpmedOutputFlags, the second byte. So when you write LpmedOutputFlags 4001 LPMEDMODPROBFUNCTION 00 00004001 00000004 00000401 00000000 it is incorrect that LpmeaModprobFunction is 00. LpmedModprobFunction is x'01' - the module is not part of dynamic LPA. So there was no match by the input token. That means (for example) if a subsequent CSVQUERY by-name still works, then your token is incorrect. You need to make sure that it does match what was returned on the corresponding CSVDYLPA ADD. I have no idea what "00004001 00000004 00000401 00000000" is. It appears to contain the values you talked about for LpmedModprobFunction, and the return and reason code. But not Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
