iseries telnet passthru subsystems
Question;
I have a setup in which an international users who is 12-13 hours infront of us needs access to our system. The problem arises that the user want to pass thru ( Telnet ) from system A to System B during our backup window. So my thought process was to create a alternate subsystem ( copy of QINTER ) which has very specific WSE. in this way I can restrict the user to a specific location and via some creative programming the user can only use a certain terminal ID to sign into the device. The question I have for the community is can I force a user to go to a specific subsystem on a passthr ( telnet ).
Example: User A comes from SYS A -> Telnet to SYS B ( I know I can force his DEV ID) to a specific name, How do I get him to go to QINTER2. Will it default to QINTER2 if QINTER1 and can I force his DEVID to carry into QINTER2 via WSE.
And without doing a mayor modification to QINTER1 can I restrict a user from gaining access to QINTER1. Remember the default WSE is *ALL in QINTER1
I hope I have not confussed anybody. Any help would be appreciated.
Software/Hardware used:
Software/Hardware used:
ASKED:
June 5, 2009 3:53 PM
UPDATED:
June 8, 2009 5:56 PM
Answer Wiki:
Just to be sure I understand what you are doing...
User A is going to start a TELNET session from System A to System B. You want to force User A to log in to QINTER2 based on the WSID. You'll have a preset WSID for the user.
1. I think you'll need to set the WSID using the RMTVRTDSP parameter of the TELNET command.
2. Add a WSE in QINTER2 on system B for that workstation name and specify the maximum active jobs. (The default is *NOMAX)
3. Add a WSE in QINTER1 on system B for that workstation name and specify 0 (zero) for the maximum active jobs. That will prevent any signon to QINTER1 from that workstation.
We do something similar where we have more than one interactive subsystem and force users into one subsystem based on WSID. In our case, we wildcard the WSID using the first two letters of the WSID and an * (for example AK*) . We found if we did not have the entry specifying max active 0 in QINTER for that name that sometimes the jobs would start in QINTER.
Regards
Mike
Mike
Thanks for your reply, I beat this issue up this weekend bouncing it back and forth thru the different iseries.
I was not aware of the entry being 0, that's good to know, however, as I left it. the user signs on with the device ID specified, when the subsystem QINTER1 goes down it automatically switches to QINTER2. It was cool seeing it change.
Thanks again for your help. You always learn something new.
Regards,
Mark
To see all answers submitted to the Answer Wiki: View Answer History.
RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
