Re: any ideas to this error message? -- MIDRANGE-L

This is something trying to use memory outside the allocated limits - a leak, you might call it. GPF in Windows terms ;-)

Take F9 on the message display to see what programs are involved. Might be an IBM issue.

From the Knowledge Base:

Message ID . . . . . . . . . : MCH0601
Message file . . . . . . . . : QCPFMSG
Library . . . . . . . . . : QSYS
Message . . . . : Space offset &2 is outside current limit for object &1 Cause . . . . . . : You tried to operate outside the specified space or to set the space pointer outside the specified space. The object referred to is &1. The offset specified is &2. The instruction ended.

Typical Causes:

This is most often due to a programming error.

The from and to program as shown in the job log are the primary suspects. These programs may be operating system or user programs. Most of the problems are user program problems. One way to cause this is to open a file with a buffer that does not match what the program is expecting. The same is true of a program that attempts to read or write a record that is longer than the actual record in the program-described file.

If the from and to programs are system programs, there may be a software bug. If the from and to program is QSQROUTE or some other QSQ module, the error may be in the coding of the user or third-party program that is using SQL. This is often seen in COBOL programs that have defined arrays that do not fit the results coming from SQL.

Resolution:

Debugging the programs is usually the only way to resolve the problem. For example, match the program's file description to the actual record length in the file.

HTH

Vern

At 03:13 PM 6/11/2003 -0700, you wrote:

Message ID . . . . . . : MCH0601 Severity . . . . . . . : 40

Message type . . . . . : Escape

Date sent . . . . . . : 06/11/03 Time sent . . . . . . : 15:06:28

Message . . . . : Space offset X'00000000' or teraspace offset

X'0000000000000000' is outside current limit for object TIM556 TIMH

812415.
Cause . . . . . :   You tried to operate outside the specified space, tried
to
  operate on an unallocated page in teraspace, or tried to set the space
pointer outside the specified space. The object referred to is TIM556

TIMH 812415. The offset specified is X'00000000' for most spaces, but

X'0000000000000000' for teraspace. The space class is X'03'. The secondary

associated space number is X'0000'. The activation group mark is

X'00000002'. The heap space identifier is X'00000000'. The pointer to the

start of the implicit process space used for the allocation is
  X'8000000000000000C52E56FA97001000'. The space class designates the type
of
space as follows:
00-primary associated space (includes space objects)

01-secondary associated space

02-implicit process space for automatic storage

03-implicit process space for static storage

04-implicit process space for activation group-based heap storage

05-constant space

06-space for handle-based heap storage

07-teraspace

The object referenced and space class information is returned, whenever it

is available, for all space classes. The other information is set only when

it applies to the returned space class value. Otherwise zero values are

returned.
Thank you, tim...
This e-mail message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential or privileged
information.  Any unauthorized review, use, disclosure or distribution is
prohibited.  If you are not the intended recipient, please contact the
sender by reply e-mail and destroy the message.
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.