|
That explains it. The active writer is the XDPELIB/XEROX, whereas that is the QUEUE the WRKSPLF *BASIC picks up. Thanks for the solution...... pytela1@midas-kapiti.com on 10/09/98 12:34:47 PM Please respond to MIDRANGE-L@midrange.com To: MIDRANGE-L@midrange.com cc: (bcc: Jim Anderson/KKI/US/ICENET) Subject: RE: WRKSPLF *INTERM vs *BASIC I think WRKSLF *INTERM will go directly to OUTQ by name. But when you use WRKSPLF *BASIC, it will try to locate active writer first and then find an assocoated OUTQ, which can be completely different. Best regards, Alexei Pytel > -----Original Message----- > From: jim_anderson@kandkinsurance.com > [SMTP:jim_anderson@kandkinsurance.com] > Sent: Friday, October 09, 1998 4:19 PM > To: MIDRANGE-L@midrange.com > Subject: WRKSPLF *INTERM vs *BASIC > > I do not understand this and if someone could shead some light, it > would be > very appreciated. > > I have on my system two outq's of the same name (it is a requirement > of the > special printing software we are using). > > Example: OUTQS: QUSRSYS/XEROX > XDPELIB/XEROX > > Up to this point, all the programmers were using WRKSPLF with the > *INTERM > level. They would change a spool file to the outq XEROX and > everything > would be just fine. The spool file would go to the proper outq > (QUSRSYS/XEROX). > > I have a new programmer that prefers the WRKSPLF *BASIC level. When > that > person changes the outq, the spool file gets placed on the wrong outq > (XDPELIB/XEROX). It cannot be the library list, because if I have > that > person switch to WRKSPLF *INTERM, it works as desired. > > Why would the WRPSPLF *INTERM locate a different outq than WRKSPLF > *BASIC > (keeping in mind the same profile and library list and same session > for > that matter). > > Jim Anderson > > > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@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 > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@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 +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@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.