Users in QINTER2 Subsystem?

2,300 pts.
Tags:
AS/400
AS/400 subsystem
QINTER
Hi everyone! How can I allow some particular users to run in QINTER2 subsystem? For example, let us take user A & B. Whenever user A logging in AS/400 he must run in QINTER subsystem and user B should run in QINTER2. How can I do this? And is it possible to set different Sign on Screen for user A & B? I mean different sign-on screen for the users running in QINTER subsystem and QINTER2? Surey.
ASKED: August 4, 2013  6:21 AM
UPDATED: August 7, 2013  5:31 PM

Answer Wiki

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

Discuss This Question: 4  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
  • TomLiotta
    There is a technical possibility of routing "users" to different interactive subsystems, but subsystems usually handle devices rather than users. If users are assigned their own devices, you can assign different devices to the subsystems that you want them in. If you absolutely must route by user, you can write a routing program for QINTER. The routing program can check the job user and run TFRJOB for any user who should be in a different subsystem. Tom
    125,585 pointsBadges:
    report
  • TomLiotta
    Signon screens are associated simply by setting the SGNDSPF() attribute of the subsystem. That can be done when you create the subsystem with the CRTSBSD command, or you can change an existing subsystem description with CHGSBSD.   A signon display screen has specific attributes that must be preserved. The text can be anything you want, and the fields can be anywhere you want them to show on the screen. But data types and sizes of the fields must always stay the same, and the order and positions of the fields in the I-O buffer must stay the same.   The subsystem monitor program has to receive the fields the same way every time.   Tom
    125,585 pointsBadges:
    report
  • WoodEngineer
    We tried something very similar at our shop so that IT staff would work from MISINTER subsystem.  Then we added "COIS*" as workstation name in the subsystem description.  All IT staff work from device names that start with "COIS".The results are not consistent.  Sometimes the user lands in MISINTER, sometimes in QINTER.  Perhaps there is a way to tell the system to check device names in  MISINTER before checking QINTER but we have not found it.
    6,045 pointsBadges:
    report
  • TomLiotta
    If a device sometimes starts in one subsystem and sometimes in a different subsystem, it's because both subsystems have been configured to allocate the device. Remove the allocation from the subsystem that shouldn't have it. Most likely one of the subsystems has some kind of catch-all entry like "*ALL". The last subsystem to allocate a device will be the one that gets it. It takes time during startup for subsystems to process all device descriptions, so you can't tell which one will reach a particular device description last. -- Tom
    125,585 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