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.


E0938: Host Links, servers fail to start on Windows server

Product: All Host Links servers
Platform: All Windows ser
Status: Fixed for R6.2, fix available for R6.1
Last updated: 2003-11-17 07:23:41

Host Links server programs are started in the background as
'services'. A Windows service program needs special resources
such as 'noninteractive window stations and desktops', and these
Windows resources are limited. The limit varies with Windows
versions and server configuration but can limit the Windows
server to as few as 50 simultaneously active service programs.

In a Host Links configuration, problems can occur if you try to
prestart too many programs from 'gservice.cfg' or if the
mainframe tries to initiate too many sessions simultaneously 'on
demand'. This could typically happen in large GCOS7 Twriter
configurations.

The lack of Windows service resources causes the start of the
Host Links server to fail in unpredictable ways. The external
symptoms of the problem vary, but typically, if the Host Links
server was started by the mainframe 'on demand', the session was
accepted by the listener but the target Host Links server (e.g.
Gspool) never started. This would often lead to restart/recovery
problems on the mainframe.

In order to ensure that the mainframe is informed in a
predictable way when there are not sufficient Windows resources
available for Host Links, we have introduced a configurable
session limit in the listener. The default 'on demand session
limit' is set by a new listener command line parameter '-ODLIM
nn'. The default is set to 50. When this session limit is
reached, new sessions will be rejected by the listener with DSA
reason code 0106 ('mailbox saturated'), rather than risking an
unpredictable failure due to Windows resource limitations. This
reason code can be changed by another new option '-ODREJ xxxx'.

Example:

  nl_dsa -odlim 30 -odrej 0105 ...

starts the listener and allows 30 simultaneous 'on demand'
sessions. Attempts from the mainframe to start more sessions
cause a 0105 (mailbox inoperable) session reject to be sent
back from the listener.

Note that this is not a problem for interactive upstream
sessions (e.g. Glink/Ggate sessions) since such sessions are not
separate service programs, but simply 'threads' in the listener.
(c) Copyright 1982-2017 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

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