|
This is how we have it set up: Subsystem description: QINTER Work station name . . . . . . . . : US* Job description . . . . . . . . . : *USRPRF Library . . . . . . . . . . . . : Maximum active jobs . . . . . . . : *NOMAX Control job at . . . . . . . . . : *ENTER Subsystem description: YOURSBS Work station name . . . . . . . . : US* Job description . . . . . . . . . : *USRPRF Library . . . . . . . . . . . . : Maximum active jobs . . . . . . . : *NOMAX Control job at . . . . . . . . . : *SIGNON This allows any session ID starting with US to run in YOURSBS, but they won't go into QINTER. Regards, Scott Ingvaldson iSeries System Administrator GuideOne Insurance Group -----Original Message----- date: Fri, 2 Sep 2005 16:23:40 +0100 from: "Clare Holtham" <Clare.Holtham@xxxxxxxxxxxxxx> subject: Question about mulitple QINTER subsystems etc Hi, Al or someone, What else do I need to do - I have created a QINTERUS subsystem and an alternate BPCS TCPIP one too, on the UK box, for my client from New Orleans. They will sign in via VPN from various US locations. If they create session IDs starting with US, they should go to the QINTERUS sbs because I have added a wse of US* on Enter, and taken out the types of *cons and *all, so nobody else can get in. This is so that we can take down the US for backups while the UK is still working and vice versa (UK is almost a 24 hr shop). BUT how do I ensure that no US users get into QINTER by mistake?? Do I need to use TFRJOB in their signon pgms, we did try that but it looped! What if QINTER comes up will it try to allocate them? I saw something on the IBm site that said it was 'unpredictable' which sbs would get the device... Thanks for your help guys, Clare Clare Holtham Director, Small Blue Ltd - Archiving for BPCS Web: www.smallblue.co.uk IBM Certified iSeries Systems Professional
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.