|
I just did a test of this scenario and as long as the printer (the correct device type) is not in a Varied On condition, an iSeries Access session that has the id configured as a display (the incorrect type) will replace the other device description with its own. There are no job logs or any printer output that shows this creation. The History only shows "Description for device xx deleted," then "Description for device xx created," and, finally, "Vary on completed for device xx."
We don't have that many PC workstations; maybe twenty [20] and, I'm guessing, six [6] have dual sessions (display and printer) configured. I've checked most of these myself and have not found any Access configuration errors. One gap, which I'm going to ask the sys admin to check out, is the two or three laptops that sales managers bring into the office.
I don't think this rogue device is being created from outside the building as the System i5 is behind a firewall, but, then, nothing is 100%. I have set the system value QAUTOVRT (Autoconfigure virtual devices) to "0". I tested that out and, as long as it is a new device id, it blocks the creation of the device. Apparently, though, not if the id already exists, even if it is a different type. I even tried changing the QAUTOCFG (Autoconfigure devices) system value to "0" (No); didn't prevent the deletion and creation of the device id.
If our scan of the laptops turns up empty, is there any way to determine from where or how this device id is getting changed/created?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
