iSeries inactivity timeout: Do break messages sent to QSYSOPR count as activity so the *console does not get timed out?

10 pts.
Tags:
AS400 Console
iSeries
QINACTITV
QSYSOPR
iSeries inactivity timout:  do break messages sent to QSYSOPR count as activity so the *console does not get timed out?

Answer Wiki

Thanks. We'll let you know when a new response is added.

A message shouldn’t alter an activity condition as long as no one responds to it in some way, e.g., presses <Enter>. A test on my system showed QSYSOPR at the console being shown inactive after and while a QSYSOPR message was on screen.

It can depend on what your settings are, though. If you have an inactivity program, that program might make decisions to let the session continue or to end it.

Tom

Discuss This Question: 3  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
  • pdraebel
    I am not sure that the CONSOLE will actually be among the jobs affected by the QINACTITV system value and QINACTMSGQ action. I have a procedure that starts the BRMS console and at that time the console is not ended. Will be checking this further.
    2,580 pointsBadges:
    report
  • pdraebel
    Seems I interpreted the question wrong. I think that as long as you have a program running on the console that at certain intervals shows some activity, like sending a message, that will be counted as an activity. Sending *break messages to the console does not seem to count as an activity and the session will be considered as being INACTIVE.
    2,580 pointsBadges:
    report
  • Vatchy
    "Sending *break messages to the console does not seem to count as an activity" I think that is because once the console breaks for the message nothing else will happen there until the message is manually removed from the display. This is definitely a non-starter if you are running a program from the console because the break message will interrupt the program; the program will not continue until the message has been taken care of.
    1,410 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