Unconfigured Ad Widget

Collapse

Announcement

Collapse
No announcement yet.

Kill signon screen?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Kill signon screen?

    Several possibilities occur to me. Change or override the SIGNOFF command to ENDCNN(*YES). Use the exit point QIBM_QWT_JOBNOTIFY to vary off the device when the job ends. Use the command analyzer exit points, QIBM_QCA_CHG_COMMAND and/or QIBM_QCA_RTV_COMMAND, on the SIGNOFF command. There may be others.

  • #2
    Kill signon screen?

    Have you tried dropping the line as the default on the SIGNOFF command? Dave

    Comment


    • #3
      Kill signon screen?

      How do you suppress the signon screen after signoff or end the client all together??? With a combination of MS and CA we have successfully locked down a PC in an unsecure area by allowing a certain stripped down profile to start windows then automatcially start a CA session using the windows profile and pwd. The exposure is after signoff they are presented with a signon screen. At this point another user with a valid higher level profile could access the AS400 and leave the session up. This allows someone else to use their profile to do bad things and place the blame on the other if they left it up. Besides inactivity timeout what can be done to kill the CA session to make the user fire up another session that automatically signs on with profile we expect?

      Comment


      • #4
        Kill signon screen?

        Thanks guys for the replies.

        Comment

        Working...
        X