Consultor Eletrônico



Kbase P14373: Error (778) with index pointer errors on AS/400
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   7/1/2004
Status: Verified

FACT(s) (Environment):

Progress 9.1C

SYMPTOM(s):

Error 778: Error reading <socket> ret=<n>, errno 0 (778)

Error reading socket, ret=0, errno=4. (778)

The error 778 is a client side error

Space offset X'0030405E' or teraspace offset X'0000000000000000' is outside current limit for object <OBJECT NAME> <DICTIONARY LIBRARY NAME> 105340.

The progress server (PROSERVER) is crashed on the as/400 machine when a batch program is run.

The error in the Joblog is:

MCH0601 Escape 40 02/12/06 11:38:12 stringEAO
000048 PROSERV PROGRESS
*STMT
To module . . . . . . . . . : ASDBIX
To procedure . . . . . . . : as4ixfnd
Statement . . . . . . . . . : 103
Message . . . . : Space offset
X'00108000' or teraspace offset
X'0000000000000000' is outside current
limit for object PROSERVER <DICTIONARY LIBRARY NAME>
930749.

0 07/24/03 11:38:04 stringEAO 000090 PROCLIENT PR
To module . . . . . . . . . : ASDBIX
To procedure . . . . . . . : as4ixnxt
Statement . . . . . . . . . : 71
Message . . . . : Space offset X'002040E5' or teraspace offset
X'0000000000000000' is outside current limit for object TRDCTRPPX3DICK
258824.
Cause . . . . . : You tried to operate outside the specified space, tried t
operate on an unallocated page in teraspace, or tried to set the space
pointer outside the specified space. The object referred to is
TRDCTRPPX3DICK 258824. The offset specified is X'002040E5' for most
spaces, but X'0000000000000000' for teraspace. The space class is X'04'. Th
secondary associated space number is X'0000'. The activation group mark is
X'00000000'. The heap space identifier is X'00000000'. The pointer to the
start of the implicit process space used for the allocation is
X'8000000000000000E1B338BF19001000'.

CAUSE:

The problem message in the joblog under the "escape" is the pointer error for the index as4ixfnd. This could happen from one of the following reasons:

The batch program is trying to access indexes which is outside of the space or do not have the permission to the spaces that the index resides.

FIX:

In one instance the problem is solved by fixing the group previliage problem of the CL program that is running in the as/400 machine through progress native 4GL client.

It seemed that the CL program which was called from the Progress Program was causing the problem. We had to create a QILE Cl to call that CL Program which seems to have corrected the Activication group problem.