lock out access to communications drop down menu in client access emulator

115 pts.
Tags:
AS/400
We need a way to prevent users from changing or creating .WS files.  The reason is that we have an external application that prints the patient arm bands to a printer based on an external table which uses the WorkstationID to Map printer.  Users are always modifying this and breaking the application which is a critical app.  

Software/Hardware used:
IBM AS400 Client Access V5.8 or 5.9

Answer Wiki

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

I’m not sure that there is a way to stop users from doing this. What you may want to try is using the device IP address or the user profile rather than the device name.

Discuss This Question: 2  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
  • KatanaBeach
    Thanks for your reply. Unfortuneately we don't have control of these values. For lack of a direct solution I have developed a batch file which will remove all ws files from the desktop and client access program folders and replace the desktop with saved ones each time the user logs on. This will lessen but not eliminate the issue. I would like a better solution. The real problem is having to tie printer devices to workstation ID's in the 1st place!
    115 pointsBadges:
    report
  • TomLiotta
    Even if the menu item is removed, the .WS files can still be changed. The problem is in the design of the app -- it's designed for terminals and is being used with terminal emulators. Further, the emulators are run in PC environments that allow PC users to make changes to the environment. You can't allow permissions to be available and then expect them not to be used. (I sympathize and expect that you don't have much choice.) Any chance you could control WorkstationID from the server side through the telnet device initialization exit point? 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.

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