IBM Mainframe Forum

Hi Steve,
Thanks for the JCL. It's not working. Error Out with MAXCC=008. Below is the error message.

IKJ56241I DATA SET IS ALLOCATED TO ANOTHER JOB OR USER
IDC0548I ** MEMBER TEST2 NOT DELETED

Thanks

Now why would you want to actually do this?

Oh sure, "It's the requirement"

Suspicious git that I am, but my question is: Why do you want to remove the evidence that you submitted the job?

I have seen doing it for some home grown scheduling of user requested jobs..

the dataset would work as some kind of drop box for user requests

deleting the member would clean up the request queue

ugly but it used to work a few decades ago.

Submitting job A.B.C(job1) whose last step is submitting job A.B.C(job2) via INTRDR to delete A.B.C(job1) seems to work if the delete in job2 is done via IDCAMS. As prino says, I would think that you would want to justify deleting the job that was submitted originally.

Vineet wrote:Hi Steve,
Thanks for the JCL. It's not working. Error Out with MAXCC=008. Below is the error message.

IKJ56241I DATA SET IS ALLOCATED TO ANOTHER JOB OR USER
IDC0548I ** MEMBER TEST2 NOT DELETED

Thanks

I take it you did not bother with the HOLDDS DD statement.

Steve's solution works just fine also. I moved the PARM value down to the SYSTSIN DD * though. So both IDCAMS and TSO work but stay away from IEFBR14 for the delete step unless you want to delete the entire A.B.C PDS.

Hi Vineet, ok, got it.
So someone or something is holding the dataset+member (the correct MVS is "enqueue"). What you should do is find out who. How is the job submitted - manually by someone using ISPF ? If so, then they must release the enqueue by PF3 out of the member.

It's possible that Vineet is the user who has PDS A.B.C enqueued.