× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: a new sign-on screen
  • From: "Kahn, David" <KAHN@xxxxxxxxxxxxxxxxxx>
  • Date: Wed, 12 Nov 1997 21:00:35 +0500

Booth,

Remember that this digression into workstation entries was related to
testing the custom sign-on display before attaching it to QINTER. Once
you've done this you would delete the test subsystem description so the
issue of which user gets which susbsystem would not apply.

*SIGNON entries cause the subsystems to allocate inactive workstations
and display the sign-on screen. When you sign on you will initially be
in the subsystem that had the workstation allocated. *ENTER entries are
used to allow a job to transfer from one subsystem to another after
sign-on. This may be done through a routing entry, for example, so that
the transfer for certain users occurs after sign-on but before the
subsequent display.

When subsystems have conflicting *SIGNON entries obviously only one of
them will be able to allocate an inactive workstation, and it's
difficult to predict which of them will get any given one. When a
subsystem starts up it will try to allocate all workstations matching
it's *SIGNON entries. Any that have active jobs (i.e. that are already
signed on) cannot be allocated by the subsystem. But it will be able to
"steal away" from other subsystems any workstations displaying the
sign-on screen.

The initial program is determined by the user profile, not the
subsystem; or were you referring to the routing entries?

I'm not sure whether I've answered your question. The process is quite
subtle. The best thing is to reread the description of it in the Work
Management guide several times and then try a few gentle tests (on your
production system in the middle of a payroll run during month end, to
show your confidence <G>).

Dave Kahn, TCO, Kazakstan
=========

kahn@tengizchevroil.com   (to November 25)
dkahn@cix.compulink.co.uk (from November 26)

>-----Original Message-----
>From:  boothm@ibm.net [SMTP:boothm@ibm.net]
>Sent:  Tuesday, November 11, 1997 7:10 AM
>To:    MIDRANGE-L@midrange.com
>Subject:       RE: a new sign-on screen
>
>on 11/12/97at 12:51 AM, the Great and Grand  Wazir "Kahn, David"
><KAHN@tengizchevroil.com> said:
>
>
>For either type of entry you have an alloaction (AT) parameter. This can
>be at *SIGNON or at *ENTER. If it's a *SIGNON entry the subsystem will
>attempt to allocate the workstation when it starts up. If successful it
>will display the sign-on screen. If another subsystem has already
>allocated the screen it will not be able to. The *ENTER allocation allows
>a job to transfer into the subsystem after sign-on.
>
>uh-oh.  Does this mean the second person to log-in gets the original
>QINTER log-in screen and initial program?
>
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.