Multiple session on the iSeries

15 pts.
Tags:
AS/400 user administration
AS/400 user permissions
Client Access
V5R4
One of our as400 users lost the ability to get multiple session on the iseries. When she tried to get a second session, she is getting a blank screen. I looked at the history log, but I cannot see anything there. Can someone please tell me what the problem could be and where to look, if any, for the error log. Thanks.



Software/Hardware used:
Iseries v5r4
ASKED: April 6, 2011  4:13 AM
UPDATED: December 18, 2013  6:53 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

I suspect the user is trying to open the same session twice instead of a new seperate session.

I tested a session which System assigned device ID and found if “auto connect” is not checked under the COMMUNICATION tag the screen just stays blank until I click COMMUNICATION first , then click connect. If “auto connect” is checked when I try to open it again I get a signon screen.

On a display where the DEVICE ID is specified and I try to open it again:
I get a balnk display and a message at the botton – ” Devce name “name ” invalid or in use on the telnet server.

Is it possible that “NOT ME” accidently checked or un-checked the setting for the session?

Discuss This Question: 14  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • djac
    Could the user have changed the Client Access configuration to include a workstation ID, in the mistaken belief that this would automatically log them in? This would also prevent them from getting multiple sessions as they would be trying to use a virtual device that was already in use.
    900 pointsBadges:
    report
  • Ihabik
    Try to Vary Off the device and then vary it On. Or, even delete the object related to the device description completely, and it will be automatically created.
    60 pointsBadges:
    report
  • WoodEngineer
    If you are using Client Access, go to the Configuration screen and check "Avoid duplicate names with other work stations."
    6,045 pointsBadges:
    report
  • TomLiotta
    One of our as400 users lost the ability... If the capability was "lost", then something changed. First place to look is the properties of the .WS file that defines the session(s). Look at its last change date. If that date is close to the date of loss, you probably know the source. If it wasn't changed, then you've nearly eliminated anything on the user's PC side. Of course, if it's been changed while attempting to fix or analyze the problem, then that info is lost. Keep it in mind for the future. Tom
    125,585 pointsBadges:
    report
  • Koohiisan
    Ours use the 'avoid duplicate names' option and this happens all the time. They end up closing one session without signing out, or mess up the password 3 times and lock *that* session. (session 'B', for instance) So, next time they try to get three sessions, they only get session 'A' and 'C', because 'B' is still varied off. So, do a wrkdevd [session name for workstation]* to see them all. For instance: "WRKDEVD DSP21*" would show DSP21A, DSP21B, DSP21C, etc. See if any are varied off.
    5,020 pointsBadges:
    report
  • Amazing0
    Thank you all for your quick response. I did check the workstation id, and it is blank, The user gets the defaults device, ie QPADEV....., so I also checked that all available devices are varied on. Yes, it looks like client access is trying to open the same session twice. One thing that the user changed was her password.
    15 pointsBadges:
    report
  • TomLiotta
    I would go to QAUDJRN and look for T/AF (Authority Failure) entries at the time connections were attempted. If the same device is being selected that is already in use by another session that belongs to this user, and if other QPADEV* devices seem to be available but not selected, then look very carefully at any changed authorities for that user. E.g., has this user become *ALLOBJ/*SECOFR class and is now only authorized to this device? Next, if the system is not allowed to create new QPADEV* devices, let it auto-create a new one for this user, then turn the capability back off. Look for the same device types on the new device and the earlier one. Are they different device types than the devices that weren't selected? Some authority wrinkle that has changed might restrict access. Tom
    125,585 pointsBadges:
    report
  • Splat
    Any change to QLMTDEVSSN limiting the number of user sessions?
    6,255 pointsBadges:
    report
  • TomLiotta
    Yes, it looks like client access is trying to open the same session twice. If just this user is seeing the problem and the configuration is simply requesting any available device, how have you determined that "client access" is trying to open the same session twice? And what did you do you stop it from doing that? So far, everything sounds like a normal, default configuration. Tom
    125,585 pointsBadges:
    report
  • Amazing0
    [...] Multiple sessions on the iSeries [...]
    0 pointsBadges:
    report
  • TomLiotta
    Is it possible that "NOT ME" accidently checked or un-checked the setting for the session? That would be the most likely cause. Be aware that it can also be changed by adding or removing the AutoConnect= line in the .WS file for the session (or by changing the setting from/to 'Y' or 'N'). That opens the possibility of any number of causes since anything that can update a text file can make the change from anywhere, as long as the route is available, permissions are available, etc. Slim possibility, but non-zero. I'd go with "Not me". Tom
    125,585 pointsBadges:
    report
  • Amazing0
    [...] Multiple session on the iSeries [...]
    0 pointsBadges:
    report
  • Daks
    There is a limit (set by you) to the number of qpadevXXXX sessions which can be active at one time. It's possible that through security issues (people varying off their sign on and/or sessions, all available qpadevxxxx sessions are "varied off".... I have seen this many times. You can check this out by typing "wrkcfgsts *dev and then jumping to "qpadev"........scroll down and see how many are are varied on; varied off; active; or on a sign on screen.......
    120 pointsBadges:
    report
  • elizmeinhartas400
    This worked for me when I came across the same issue: Configure your Communication settings in session that you have open. Find where you can specify settings for the Workstation ID and check the option to 'Avoid Duplicate Names on this Workstation'. Click OK, your session will need to terminate, go to file>save. Reconnect and try again. 
    25 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following