|
Grepp, when I looked at the values once again, I found The OUTQ specified in User profile was *WORKSTN The OUTQ specified in the Workstation was *DEV And the OUTQ specified in QPRTDEV was the name of a *OUTQ object in QGPL. The spool file that I sent was received into the outq specified in QPRTDEV system value. I want to know what is the order in which the outq is searched for? As you have specified, if it was the outq specified in Userprofile, then there it found the entry *WRKSTN, then it searched the entry in workstation, found *DEV. (What does *DEV mean? What does it refer to?) And finally it settled for the value in QPRTDEV. Is that correct? Regards Kumaravel date: Tue, 18 May 2004 16:03:06 -0700 from: "Graap, Ken" <keg@xxxxxxxxxxxxx> subject: RE: SNDNETSPLF and outq It is received into the *OUTQ specified on the user profile of the recipient... -----Original Message----- From: MK, Kumaravel (Cognizant) [mailto:mkumara@xxxxxxxxxxxxxxxxx] Sent: Tuesday, May 18, 2004 3:49 PM To: midrange-l@xxxxxxxxxxxx Subject: SNDNETSPLF and outq I sent a spool file on network to another user. Into which outq is this spool received? There are many places where the OUTQ is mentioned. 1. In the Userprofile definition. 2. In the Workstation. 3. In the QPRTDEV system value. Regards Kumaravel
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. Visit us at http://www.cognizant.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.