Facebook

Fill out this form to subscribe to news, tips and information about updates.

Read more
Search known errors
From date:
To date:

Follow us
Facebook    Twitter    LinkedIn

G&R » Support » Known Errors  

Known Errors

These are the known errors in our products, logged as reported with versions and platforms affected as well as corrections and work-arounds.

This list is largely historical, since it records all problems that have been reported throughout G&R history. Only the most recently reported problems still exist, unless you are using a very old copy of the product, in which case you should update the product to the most recent version.


E1128: Ggate/TNVIP, default RESOURCE/CONAME (documentation error)

Product: Ggate
Platform: All
Status: Documentation corrected for R6.4
Last updated: 2006-07-17 07:26:50

The Ggate manual incorrectly documents that the default RESOURCE/CONAME of
'TNVIP' is always used if the client specifies no, or an incorrect,
RESOURCE/CONAME.

In fact the default is only applied if the banalize (-ba) is set. The
updated text in the manual is:

   Ggate TNVIP clients can configure a resource name, and this is
   interpreted as a CONAME in dsa.cfg. You can use RESOURCE as an
   alternative to CONAME in dsa.cfg; they are synonymous. The
   CONAME/RESOURCE must be preconfigured to connect the user to a
   specific GCOS application. A RESOURCE can be shared by many users
   using POOLS for LID, USERID, BILLING, PROJECT as needed, or using
   local dialog in order to obtain the connection parameters. The
   Ggate administrator can configure a default CONAME with the name
   TNVIP. Clients can use TNVIP specifically as a resource, but if
   the Ggate banalize parameter (-ba) is set TNVIP clients that
   specify no resource, or a non-existent resource, are allocated the
   default TNVIP resource.
(c) Copyright 1982-2017 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

URL: http://www.gar.no/support/errors
 
PARTNERS