Trigger buffer problem causes lock-up -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

We've never seen anything quite like this before, and it's happened twice (thankfully, to us, not to a paying customer).

We have the "first trigger parameter" defined thusly:

DPARM_01 DS DFILENAME 1 10 DLIBNAME 11 20 DMBRNAME 21 30 DTRG_EVT 31 32 DP_B4OFF 49 52B 0 DB4LEN 53 56B 0 DP_AFOFF 65 68B 0 DAFLEN 69 72B 0 DDATA 1 10240

and we have a variable defined thusly:

D XRAW 1 1086

and this SUBST statement:

C 1087 SUBST DATA:AFOFF XREC

seems to be blowing up (maybe consistently, maybe intermittently), with this appearing in the dump (the names have been changed to protect the innocent)

PARM_01 DS AFLEN BIN(9,0) 000000174. B4LEN BIN(9,0) 000000174. DATA CHAR(10240) NOT ADDRESSABLE FILENAME CHAR(10) 'BAR ' LIBNAME CHAR(10) 'FOO ' MBRNAME CHAR(10) 'BAR ' P_AFOFF BIN(9,0) 000000294. P_B4OFF BIN(9,0) 000000096. TRG_EVT CHAR(2) '31' PARM_02 DS BUFFLEN BIN(9,0) 000000492.

Can anybody tell me what in blazes this "NOT ADDRESSABLE" is all about? And why this code would suddenly start blowing up, after working as intended for years?

--
JHHL

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.