|
Well...pseudo random..they all start with QPADEV*, right? I'd check those devices to see if the object authority changed. Also, are the host servers running? Do a STRHOSTSVR *ALL...it's ok if they're already running. > -------- Original Message -------- > Subject: RE: CPF1110 error message > From: "Dwayne Allison" <Dwayne.Allison@xxxxxxxxxxxxxxxxxxxxxxxx> > Date: Mon, May 16, 2005 1:32 pm > To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> > > We are using Client Access on an XP platform, so the terminal id is a random > number. > > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx > Sent: Monday, May 16, 2005 10:04 AM > To: Midrange Systems Technical Discussion > Subject: Re: CPF1110 error message > > > What terminal id? > > WRKOBJ OBJ(ROBS1) OBJTYPE(*DEVD) > 5=Display authority > If it doesn't have *PUBLIC at *CHANGE. > Object > User Group Authority > *PUBLIC *CHANGE > > Then you > DSPSYSVAL QCRTAUT > and you changed it from the default. If so, then you need to modify these > terminal sessions to allow what users should be using them. *public > *change works pretty good. > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com > > > > > > "Dwayne Allison" <Dwayne.Allison@xxxxxxxxxxxxxxxxxxxxxxxx> > Sent by: midrange-l-bounces@xxxxxxxxxxxx > 05/16/2005 09:34 AM > Please respond to > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > > > To > "Midrange Systems Technical Discussion \(E-mail\)" > <midrange-l@xxxxxxxxxxxx> > cc > > Subject > CPF1110 error message > > > > > > > Good Morning, > > We our user are getting load off the system and then when they try to log > back on they get a CPF1110 Not Authorized To Work Station. > > Any idea? > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l.
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.