Re: QZRCSRVS

John,

Here is more information from another of my co-workers.

I've got a minor correction to the information Dawn provided, along with my
perspectives on the original note.

When running APPC, the name of the remote command server job is QZRCSRVR.
If they are seeing QZRCSRVS jobs in QCMN, it is likely because of somehow a
batch-immediate job was started there.  Seems to me I have seen a case
where our jobs were running in other subsystems when coming through Toolbox
for Java, but I'm not certain of the exact circumstance around that.

Operations Navigator is the big user of these jobs - nearly everything they
do is via command or API call.  Dawn is correct about the central server
and signon server - they have different functions and they have different
job names.

It is possible that the client is not cleaning up after themselves - if
John does a "netstat *cnn" he can look for connections to port 8475
(as-rmtcmd) to see if the active connections seem to match up with the
number of active jobs.  That would be the first thing to check.  Call
stacks of the seemingly unused jobs could be inspected, as well, to see if
they are just sitting on a receive function.

Ed Fishel,
edfishel@US.IBM.COM