How can I tell which active users are using Client Access using TCP connection versus users on dumb terminals? Client Access sessions are configured so that the job name is not a virtual name.
I'll assume that CA/400 clients are defining device names for their Telnet5250 sessions that don't start with DSP.
If you set system value QDEVNAMING to *NORMAL then DUMB Terminals attached to workstation controllers will be named as follows:
o *NORMAL. Naming conventions must follow AS/400 standards. The following are examples of names following AS/400 standards:
Display Stations DSP01, DSP02
When you then do a WRKACTJOB the DSPxx jobs running in subsystem QINTER would be dumb terminals, while the other jobs would be the CA/400 TCP/IP connected devices.
If you changed your mind and allowed the system to generate a virtual device name, it would be very easy to differentiate between local and IP connected because as you already know, they would be automatically configured by the system with names like QPADEV0001.
That said... You could also experiment with creating additional memory pools on the system and through QINTER subsystem configuration changes and different job descriptions for remote and local devices, route local devices to POOL 2 and remote devices to POOL 3. Using the F11 key from the WRKACTJOB display screen would then allow you to display POOL ID for a job and even to sort by POOL. Which in this example would then be sorting by local and remote devices.
Dig Deeper on Past Releases
Related Q&A from Ken Graap
The BRMS Network feature allows a BRMS system to connect to other BRMS systems via a network, and enables a user to consolidate media such as backup ... Continue Reading
The only option to correct damage preventing file journaling is to use the RCLSTG command. Continue Reading
IBM's iSeries Backup and Recovery manual answers many questions related to system backup and disaster recovery. Continue Reading