|
On Mon, 2 Mar 1998 16:33:05 -0500, you wrote: >ghutchinson@tstoverland.com (Gord Hutchinson) wrote: >>We have just installed an S10 to replace a model 300. We also have a >>model 620. >> >>When we did a SBMRMTCMD from the 300 to the 620, a job runs in QCMN >>using my userid. However, when I do a SBMRMTCMD from the s10 to the >>620, it uses QUSER. > >On the SBMRMTCMD command there is a DDM file parameter. The DDM file >you are specifying contains both the remote system name you are >submitting the command to, as well as the mode description to use. >Display the DDM and note what mode is being used. Now, on the remote >system display the subsystem description for subsystem QCMN. Select >option 8 to display the communication entries. Find the mode being >used by your SBMRMTCMD, then look in the default user column. The >default user determines the user profile the remote command will run >under. > >Terry Herrin Terry, DDM file created on either the s10 or the 300 to the 620 shows a mode of *NETATR. There are no system specific CMNEs in QCMN on the 620. Thus I am guessing that it is picking up device *ALL and mode *ANY for both. The default user is *SYS. Yet, from the 300 I have a job active in QCMN using my userid. From the s10, the userid is QUSER. This is an issue because of object authorities. QUSER does not have authority to our application objects. My userid has higher authority than the users (or our development staff). Gord -- Gord Hutchinson TST Overland Express ghutchinson@tstoverland.com +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.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.