Re: a new sign-on screen, thanks

Dave,

  Thanks for your help and information.  

Marc Zylka ( mzylka@netpath.net )
Flynt Fabrics, Inc.

>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.  :-)


+---
| 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
+---