|
Message: 6 Date: 8 Nov 2002 07:28:34 -0000 From: "MURALI DHAR" <nmuralidhar@rediffmail.com> To: rpg400-l@midrange.com Subject: Called program Reply-To: rpg400-l@midrange.com Generally how can I find out whether the program is called one or nt ? ------------------------------------------------- Not sure I understand your question. Do you mean, if I "call" a program (either from a command line or another program) how do I know if the program that "runs" is the actual compiled object I think it is? If so, display the job (alt sysrequest, option 3, option 11.) This will tell you what processes are running in the job, and the library the process object is in. I.e., if I have two programs named PROGRAM, each in a different library, then I CALL PROGRAM from the command line, the one that runs is the first one found when the operating system searches sequentially through the job's library list. Displaying the job will verify which process object is being used. ------------------------------------------------- If 2 users are working on same program source ,how can I lock and release the program source ?how do other user come to know whether the program source is locked or nt for updation? ------------------------------------------------- Again, your question is unclear. Others have answered assuming you were talking about concurrent editing of a source member. Or, are you talking about two people copying the source to their own libraries to make modifications independently? In that case, you need a change management tool like Aldon or SoftLanding. I'm not sure, but I think PDM also has a rudimentary source management component...? ------------------------------------------------- Regards&Thanks Murali Jeff Markel Developer, Merchandise Accounting Costco Wholesale Corporate Office Issaquah, Washington Office (425) 427-7662 FAX (425) 313-6800 JMarkel@Costco.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.