CL call from VB

I am having a problem when I called a CL procedure(The CL in turn calls a
Cobol/400 program)from Visual Basic in a
multi-user environment, Does the CL object get locked by the call and the
other users cannot access the CL or is it the files in the CL getting
locked......... I was not able to comprehend whenever I get the MESSAGE WAIT
on the WRKACTJOB saying the file is already in use, and I cannot understand
whether it is the CL procedure called by Visual Basic that is getting
locked.

In simple words when a CL is called by Visual Basic in multi-user
environment, Why doesn't the CLRPFM
command work?

Thanking you all in Advance..

Shaik Basha



+---
| This is the COBOL/400 Mailing List!
| To submit a new message, send your mail to COBOL400-L@midrange.com.
| To subscribe to this list send email to COBOL400-L-SUB@midrange.com.
| To unsubscribe from this list send email to COBOL400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---END