We have just installed the PC Console to our AS400 system. This is installed in a remote server. Can we login through QCTL subsystem while the system is up and running or will it affect the production?
logging into QCTL will not affect the environment. But you may not be able to execute and accomplish work as you do from QINTER. qctl mostly for backups and restricted work...as SAVSYS etc..
Last Wiki Answer Submitted: November 28, 2012 5:30 pm by harisudhan21995 pts.
If you live outside the United States, by submitting your email address you consent to having your personal data transferred to and processed in the United States.
Usually, the times that you log in will be times when the system is up and running. However, it’s best if you limit console access to circumstances when you intend to bring the system down to a restricted state or farther. Otherwise, you can do almost everything else through any common telnet session (or the iSeries Navigator or similar interface). True console access should be a restricted operation, for system security and integrity more than for general interference. — Tom
Thanks Tom!!
Now am not going to do any operation using the PC Console, what I ve to do is need to check whether I am able to login or not. As it is a production server I cannot put it down or to restricted state.
When you sign into a System Console you will be at a Priority 10 where other Interactive jobs are usually at a 20. This means you can signon to test but if for some reason you say run a query or a long running Interactive job from there it could effect other Interactive users
what I ve to do is need to check whether I am able to login or not.
Testing connection and logon won’t affect anything. If the console session is used to do work, it can slow some other processes because it runs at a higher priority. If you’re just connecting, signing on and looking at basic system features, you won’t interfere with anything.
Mostly, you just don’t to be running major apps and queries and similar tasks from the console session.
Also, the more the console is in use, the more the risk increases of object damage happening to the device description and related objects. (The risk is tiny, but there’s no point in tempting fate.) This is similar to any risk to an important system component. You should avoid using user profiles such as QSECOFR for the same reason. Why do it if it’s not required?
But the console is intended to be used. It should be tested. Just keep in mind that it’s an important resource that should be used only for its intended purpose. It’s simple common sense is all.
If you are using a Operations Console running on a PC or Server then you can VNC or remote desktop into and use the console. If you have a Twinax System Console out of Luck
Usually, the times that you log in will be times when the system is up and running. However, it’s best if you limit console access to circumstances when you intend to bring the system down to a restricted state or farther. Otherwise, you can do almost everything else through any common telnet session (or the iSeries Navigator or similar interface). True console access should be a restricted operation, for system security and integrity more than for general interference. — Tom
Thanks Tom!!
Now am not going to do any operation using the PC Console, what I ve to do is need to check whether I am able to login or not. As it is a production server I cannot put it down or to restricted state.
When you sign into a System Console you will be at a Priority 10 where other Interactive jobs are usually at a 20. This means you can signon to test but if for some reason you say run a query or a long running Interactive job from there it could effect other Interactive users
what I ve to do is need to check whether I am able to login or not.
Testing connection and logon won’t affect anything. If the console session is used to do work, it can slow some other processes because it runs at a higher priority. If you’re just connecting, signing on and looking at basic system features, you won’t interfere with anything.
Mostly, you just don’t to be running major apps and queries and similar tasks from the console session.
Also, the more the console is in use, the more the risk increases of object damage happening to the device description and related objects. (The risk is tiny, but there’s no point in tempting fate.) This is similar to any risk to an important system component. You should avoid using user profiles such as QSECOFR for the same reason. Why do it if it’s not required?
But the console is intended to be used. It should be tested. Just keep in mind that it’s an important resource that should be used only for its intended purpose. It’s simple common sense is all.
Tom
If you in nedd to use it remotely, it is possable if you have HMC..Hassan
…to use it remotely, it is possable if you have HMC..
It is also possible if you don’t use a HMC.
Tom
Hello, how can we do it using HMC..?
Using HMC Follow http://www-912.ibm.com/s_dir/slkbase.nsf/1ac66549a21402188625680b0002037e/37396cfd67d5ef5886256f01000bda50?OpenDocument&Highlight=2,PC5250,Configuration,for,HMC,Remote,ConsoleTom: How can we use it witout HMC????Hassan
If you are using a Operations Console running on a PC or Server then you can VNC or remote desktop into and use the console. If you have a Twinax System Console out of Luck
u can login to QCTL when system is up. but u should to do IPL or take system to restrict state. rest of the things u can check.