Troubleshooting
Problem
This document provides information about QGYSERVER jobs.
Resolving The Problem
QGYSERVER is a host server job used almost exclusively by Navigator for i in pre-V5R1M0 operating system versions. Its function is to return user list information.
A list operation was added to network print at V5R1M0. The list operation provides better performance over previous operating system versions and has the added benefit of conserving system resources. On a V5R1M0 or later system, each Network Print server job (QNPSERVS) uses an API which is part of the group of QGY components to perform this list operation.
Because the API exists as part of the QGY components, it is necessary to run the QGY server job(s) (QGYSERVER) each time this API is called.
Although the QGY server jobs are still associated with Navigator for i, their APIs are used by many applications, including Java toolbox, SMB, and other client applications.
Typically, the instance of the QGYSERVER job stays active (DEQW or TIMW status) as long as the job that called it stays active. It normally relies on an internal queue to disappear when the calling program cleans up. The internal queue is scoped to the calling program so the QGYSERVER job is cleaned up then. This behavior accounts for the large numbers of QGYSERVER jobs sometimes found on IBM i running V5R1 and later operating systems.
For more information, see, 'System API Programming V4', SC41-5800-00
A list operation was added to network print at V5R1M0. The list operation provides better performance over previous operating system versions and has the added benefit of conserving system resources. On a V5R1M0 or later system, each Network Print server job (QNPSERVS) uses an API which is part of the group of QGY components to perform this list operation.
Because the API exists as part of the QGY components, it is necessary to run the QGY server job(s) (QGYSERVER) each time this API is called.
Although the QGY server jobs are still associated with Navigator for i, their APIs are used by many applications, including Java toolbox, SMB, and other client applications.
Typically, the instance of the QGYSERVER job stays active (DEQW or TIMW status) as long as the job that called it stays active. It normally relies on an internal queue to disappear when the calling program cleans up. The internal queue is scoped to the calling program so the QGYSERVER job is cleaned up then. This behavior accounts for the large numbers of QGYSERVER jobs sometimes found on IBM i running V5R1 and later operating systems.
For more information, see, 'System API Programming V4', SC41-5800-00
[{"Product":{"code":"SWG60","label":"IBM i"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Host Servers","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"Version Independent","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]
Historical Number
26730925
Was this topic helpful?
Document Information
Modified date:
02 January 2020
UID
nas8N1017008