ca.portal.admin

Re: ""Required"" 256-byte Sort Key

Discussion created by ca.portal.admin on Sep 9, 2006
Hi Dan,
That is exactly it for the few problems I have encountered on this - I
have only seen it a couple of times in about 15 years, always on batch
jobs. It goes 0C4 on a 'MVC' trying to read past the end of a 4K page
into another page not owned by the task. When you look at the dump it
has gone over on an OBTAIN USING SORT KEY and the sort key it is using
is right at the end of the storage owned by the task. Padding the field
resolves the problem.

Steve

BT

'This post represents the views of the author and does not necessarily
accurately represent the views of BT.'
British Telecommunications plc
Registered office: 81 Newgate Street London EC1A 7AJ
Registered in England no. 1800000

This electronic message contains information from British
Telecommunications plc which may be privileged and confidential. The
information is intended to be for the use of the individual(s) or entity
named above. If you are not the intended recipient, be aware that any
disclosure, copying, distribution or use of the contents of this
information is prohibited. If you have received this electronic message
in error, please notify us by telephone or e-mail (to the number or
address above) immediately.-----Original Message-----
From: IDMS Public Discussion Forum [mailTo:IDMS-L@LISTSERV.IUASSN.COM]
On Behalf Of Casey, Don J
Sent: 08 September 2006 20:45
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: Re: ""Required"" 256-byte Sort Key

As I'm reading this, it isn't an overlay issue, it's a ""fetch
protection"" issue, as Steve says below.

IDMS will move 256 bytes into an internal area large enough to hold 256
bytes (separate from task storage; my guess is somewhere in the VIB or
possibly ERE if this only relates to ERUs calls), but if the SOURCE
field extends into a 4K chunk of storage in a different key, you'll get
a S0C4 for attempting to read out of a block you're not allowed to see.

This is most likely going to happen if you're pointing into a file
buffer, or somewhere towards the end of your working storage (if COBOL).


* DQC

Outcomes