It seems if a rls server had an rli-rli update pair and then later
had it deleted. Running globus-rls-admin -s against the server would
always have a "globus_rls_client: RLI doesn't exist: NULL,NULL" msg show up.
this does not happen for globus-rls-admin -S call.

It turns out that -s (show) option tracked the return code of
globus_rls_client_rli_rli_get_part
and
globus_rls_client_lrc_rli_get_part and when the t_rli tables exist
but empty then it will return RLI doesn't exist error code.

In -S (status) option, the return code was not tracked and
hence the !GLOBUS_SUCCESS return code got dropped after it leaves the
switch case.

perhap SHOW option also should be handle similarly to the STATUS option.