|
Better still, use CA Express with the latest service packs, and you can use stuff like &COMPN= as the session ID, which will use the client computer name then add a unique identifier to the end (1-9, then A-Z). You only need one session icon on the desktop, one .WS file, and you can still identify where a session is attached to. If a device is in use, it simply clicks over to the next identifier. Definitely worth checking out. Dwayne Lindner Senior Analyst - Data Centre Wesfarmers Rural Division 184 Railway Parade, Bassendean WA 6054 Ph: (08) 9273 5365 Email: dwayne.lindner@writ.wesfarmers.com.au > ---------- > From: Mark A. Manske[SMTP:mmanske@minter-weisman.com] > Reply To: MIDRANGE-L@midrange.com > Sent: Wednesday, 8 November 2000 22:52 > To: MIDRANGE-L@midrange.com > Subject: RE: Client Access Session Dropping and Can't Re-Connect > > Look at the device too since you have "hard-coded" or "named workstations" > - > odds are you have to vary off and vary on the device - > sometimes the AS/400 is "slow" about re-setting devices > whose job ends abnormally. > > Another suggestion/question - why not use virtual devices? > We have more trouble with "users" just turning off their PC's > to end their jobs here and then turning them back on, or > simply closing the client access session instead of minimizing it. > Training seems to work for about a week, sometimes less, so it became > less work and stress on us and the users just to go virtual. > > HTH > > Mark A. Manske > [mailto:mmanske@minter-weisman.com] > Sr. Project Lead > Minter-Weisman > > > > -----Original Message----- > From: owner-midrange-l@midrange.com > [mailto:owner-midrange-l@midrange.com]On Behalf Of Joe Giusto > Sent: Wednesday, November 08, 2000 7:56 AM > To: 'midrange-l@midrange.com' > Subject: Client Access Session Dropping and Can't Re-Connect > > > I am running C/A V3R2M0 with service pack SF59075. OS400 V4R4M0. Using > named workstation. > > A session drops and I can not reconnect. In the past, all I have had to > do > is end the jobs that were signed into the C/A Workstation and then it > would > free up and I could re-connect. > > Now, there is no job running under the workstation, but I still can not > connect (black screen of death is all that appears). > > Is there another place (job or subsystem to look in) on the system that I > have to reset to be able to re-use the session name? > > Thank you for any advice or hints that you can give. > > +--- > | 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.