Model 170 – Problem creating PC5250 session

20 pts.
Tags:
AS/400
PC/Windows Connectivity
Dear All, I know what the problem is and what the resolution is (see below) but how do I create a 5250 session now in order to sign on to the AS400 and change the system value QAUTOVRT. (There is no Twinax connection on the 170 so no dumb terminal available.) Can you help ? PC5250 Displays E8940 Error When Connecting iSeries Access for Windows > >Problem Summary: >Configuring a PC5250 session with iSeries Access for Windows V5R2 >results in the error E8940. > >Resolution: >Verify the QAUTOVRT system value which is set too low. This system value >controls the total number of virtual display devices that can be created >on the system. Increase the value to something more than the current >total number of virtual devices so the new virtual display device for >this session is able to be created.
1

Answer Wiki

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

If you can’t start an 5250 session, you can try to change the value with ftp. Start an ftp session to the as/400, login as qsecofr (or another account with enough rights) and enter the following command :
quote rcmd call qcmdexc (‘chgsysval sysval(qautovrt) value(999)’ x’000000003700000F’)
The 37 in the second parameter is the length of the first parameter (if I counted right), change this after filling in the 999 with the right value to the new length of the command.
In this way you can start almost any command to be remotely executed, if the rights are correct.

A second method, which is better in this case but not as flexible, is to go to the Client access operations navigator on the your pc. Go to your system, configuration and service (I have a dutch version, so I’m translating back), system values, devices and change the value in automatic configuration, pass-through devices.

Succes.

Discuss This Question: 8  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.
  • KasMcc
    You can use operations navigator to make changes to system values, or the most simple method is to telnet on to the machine. Start, run - Command Telnet xx.xx.xx.xx (address of your as400)You will get a signon screen and can access from there.
    230 pointsBadges:
    report
  • Ayahel1
    You can TELNET, STRPASTHR or 5250 emulation while setting the device name. So if you know of an existing display device (for example QPADEV0001) that already exists, varied on and matches your device type you can set it: TELNET RMTSYS(system) RMTVRTDSP(QPADEV0001) or STRPASTHR RMTLOCNAME(system) VRTCTL(ctl) VRTDEV(QPADEV0001) or Set the device name in the emulation program
    0 pointsBadges:
    report
  • Xasanchez
    Have you tried TELNETing into the iSeries? It should be clean and easy. Like TELNET 192.168.0.5 which is a sample IP address for your iSeries.
    0 pointsBadges:
    report
  • Rockgirl
    Dear All, Thank you so much for all your helpful advice and your speedy response. Ended up using FTP and increasing the sysval value of QAUTOVRT which allowed sign on but Now another problem seem to be getting CPF1110 - not authorised to workstation (but can log on as Qsecofr OK) changed the sysval QCRTAUT from *Public *use to *Public * Change but this does NOT seem to have helped. Can still only sign on as Qsecofr. More help needed
    20 pointsBadges:
    report
  • FreedomOfSpeech
    You need to change the default create authority for the library QSYS: CHGLIB LIB(QSYS) CRTAUT(*CHANGE) This will allow the virtual devices to be used by users in the system. The system value QCRTAUT is only good for new objects being created. I would put it back to its original value unless you are performing an upgrade or PTF install.
    0 pointsBadges:
    report
  • JDWWms
    If the QLMTSECOFR system value is set to '1' (on) and the a profile has *ALLOBJ or *SERVICE authority then it must be granted private rights to a device description before it can signon to that device. Regular users should not have these special authorities assigned and QSECOFR shouldn't need to signon to more than a few specific devices.
    0 pointsBadges:
    report
  • Rockgirl
    problem now resolved. Thanks to all for your advice.
    20 pointsBadges:
    report
  • TomLiotta
    A few minor comments... TELNET RMTSYS(system) RMTVRTDSP(QPADEV0001) or STRPASTHR RMTLOCNAME(system) VRTCTL(ctl) VRTDEV(QPADEV0001) Those are pretty tough to do when you only have one AS/400. quote rcmd call qcmdexc ('chgsysval sysval(qautovrt) value(999)' 37) The QCMDEXC length parm is already defined as *dec (15 5), so the default handling of 37 works. CPF1110 - not authorised to workstation Note that authority may be needed to both the *DEVD and the device *MSGQ. changed the sysval QCRTAUT from *Public *use to *Public * Change For most systems, this should probably always be *CHANGE. Since it only applies to 'newly created' objects and items such as device descriptions are among the few objects in QSYS that get created, *CHANGE is useful. As for non-IBM libraries, the libraries should have their CRTAUT() attribute set when the libraries were created. Original objects in those libraries should have their appropriate authorities when the libraries were created. About the only objects that should ever be affected are user objects anyway. Tom
    125,585 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.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: