× 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 00:51:15 +0500

Marc,

It can be by name or type. If you display the susbsystem description you
will see that you have option 4 for name entries and option 5 for type
entries. You can add either type of entry using the ADDWSE command.

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.

If you look at the default entries for QCTL and QINTER you will see that
QCTL has a *SIGNON entry for type *CONS and an *ENTER entry for type
*ALL, while QINTER has these the other way round. That's why only the
console defaults into QCTL while all the others default into QINTER.

To test your signon screen create a named entry for the workstation
you're signed on to in the test subsystem with AT(*SIGNON). Issue a
TFRJOB xxxxx command where xxxxx is the name of the test subsystem, then
sign off. You should then be staring at your artistic masterpiece.  :-)

HTH

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

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


>-----Original Message-----
>From:  Marc Zylka [SMTP:mzylka@netpath.net]
>Sent:  Monday, November 10, 1997 3:26 PM
>To:    MIDRANGE-L@midrange.com
>Subject:       Re: a new sign-on screen
>
>I few notes back in this thread it was suggested to test a new
>signon screen using a test subsystem.  I have created a test
>subsystem, which looks similar to QINTER, but how is the test subsystem
>associated with the display I'm using?  Is this by display id?
>
+---
| 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.