D3/Linux program abort

#1

I'm running a basic program which is called from a proc. This type
situation is EXTREMELY common throughout our software. The proc
selects records, & the program processes them. This particular
program isn't one that is run very often, perhaps ever, & is resulting
in the following error, shortly after entering the basic program, but
before it actually begins to process any records. It APPEARS as
though it has to do with the opening of a particular DICT file in the
program, but I've been unable to stumble across a fix so far. The
abort message is as follows:

Unrecognized Opcode @ br.store.rtn:05B

O=Logoff / Q=Quit / <CR>=Go to debugger ?

Does anyone have any idea what the error signifies??

Thanks in advance,

Mark Wright
Eastex Crude Company

#2

On Feb 27, 3:21 pm, "mwright" <wright.m... (AT) gmail (DOT) com> wrote:

Quote:

I'm running a basic program which is called from a proc. This type
situation is EXTREMELY common throughout our software. The proc
selects records, & the program processes them. This particular
program isn't one that is run very often, perhaps ever, & is resulting
in the following error, shortly after entering the basic program, but
before it actually begins to process any records. It APPEARS as
though it has to do with the opening of a particular DICT file in the
program, but I've been unable to stumble across a fix so far. The
abort message is as follows:

Unrecognized Opcode @ br.store.rtn:05B

O=Logoff / Q=Quit / <CR>=Go to debugger ?

Does anyone have any idea what the error signifies??

Thanks in advance,

Mark Wright
Eastex Crude Company

Hello Mark,
Maybe someone can determin the problem from the error message but I
think it would be helpful to post the PROC to the user group and might
have a better chance of a solution
Bob Marik

#3

Make a copy of the PROC.
Change all lines with a P to PW.
Hit <CR> as each statement appears.
The bad statement will be the last statement before the abort.
If it aborts
Change the SELECT to a LIST and execute at TCL.
If it aborts immediately
Do the SELECT one Dictionary at a time.
when you find the bad guy
SSELECT THE FILE
LIST FILE DICT
The bad data is in the next item in your list
ELSE
Do the SELECT and run the program with a (D
"RUN BP PROG (D
walk the debugger
END
END

Patrick, <;=)

mwright wrote:

Quote:

I'm running a basic program which is called from a proc. This type
situation is EXTREMELY common throughout our software. The proc
selects records, & the program processes them. This particular
program isn't one that is run very often, perhaps ever, & is resulting
in the following error, shortly after entering the basic program, but
before it actually begins to process any records. It APPEARS as
though it has to do with the opening of a particular DICT file in the
program, but I've been unable to stumble across a fix so far. The
abort message is as follows:

Unrecognized Opcode @ br.store.rtn:05B

O=Logoff / Q=Quit / <CR>=Go to debugger ?

Does anyone have any idea what the error signifies??

Thanks in advance,

Mark Wright
Eastex Crude Company

#4

On Feb 28, 3:56 pm, latimerp <"(latimerp)"@comcast.net> wrote:

Quote:

Make a copy of the PROC.
Change all lines with a P to PW.
Hit <CR> as each statement appears.
The bad statement will be the last statement before the abort.
If it aborts
Change the SELECT to a LIST and execute at TCL.
If it aborts immediately
Do the SELECT one Dictionary at a time.
when you find the bad guy
SSELECT THE FILE
LIST FILE DICT
The bad data is in the next item in your list
ELSE
Do the SELECT and run the program with a (D
"RUN BP PROG (D
walk the debugger
END
END

Patrick, <;=)

mwright wrote:
I'm running a basic program which is called from a proc. This type
situation is EXTREMELY common throughout our software. The proc
selects records, & the program processes them. This particular
program isn't one that is run very often, perhaps ever, & is resulting
in the following error, shortly after entering the basic program, but
before it actually begins to process any records. It APPEARS as
though it has to do with the opening of a particular DICT file in the
program, but I've been unable to stumble across a fix so far. The
abort message is as follows:

Unrecognized Opcode @ br.store.rtn:05B

O=Logoff / Q=Quit / <CR>=Go to debugger ?

Does anyone have any idea what the error signifies??

Thanks in advance,

Mark Wright
Eastex Crude Company

Bob/Patrick,

Thanks for the suggestions.

However, the proc is not the problem. It makes its selection, &
passes control to the program successfully.

At first, I thought bad data was a possible cause, as well. But, in
this case, it's not. I've done the select at TCL, & it runs fine.
I've listed & counted the records the select finds, & there are no
problems. The program never gets as far as processing the selected
records. I'm still doing some debugging to try to find the problem.
If anyone comes up with any other ideas, I'd LOVE to hear 'em!!!!

MW

#5

<snip>

Quote:

However, the proc is not the problem. It makes its selection, &
passes control to the program successfully.

At first, I thought bad data was a possible cause, as well. But, in
this case, it's not. I've done the select at TCL, & it runs fine.
I've listed & counted the records the select finds, & there are no
problems. The program never gets as far as processing the selected
records. I'm still doing some debugging to try to find the problem.
If anyone comes up with any other ideas, I'd LOVE to hear 'em!!!!

MW
I know you've done this but.

1. Does ABS Verify
2. Have you recompiled.
3. Have you copied and renamed, complied, cataloged and
rerun the process under the new name
4. Have you done the same with subroutine calls.
5. Is Common intact throughout
6. Who touched what i.e. what has changed recently?
7. Have contractors or children been near the System?

8. How about the Boss or his/her children?

Patrick, <;=)

#6

Isn't this BASIC object code corruption (Mark?) Have you tried recompiling
the program?

Chandru
"mwright" <wright.mark (AT) gmail (DOT) com> wrote

Quote:

I'm running a basic program which is called from a proc. This type
situation is EXTREMELY common throughout our software. The proc
selects records, & the program processes them. This particular
program isn't one that is run very often, perhaps ever, & is resulting
in the following error, shortly after entering the basic program, but
before it actually begins to process any records. It APPEARS as
though it has to do with the opening of a particular DICT file in the
program, but I've been unable to stumble across a fix so far. The
abort message is as follows:

Unrecognized Opcode @ br.store.rtn:05B

O=Logoff / Q=Quit / <CR>=Go to debugger ?

Does anyone have any idea what the error signifies??

Thanks in advance,

Mark Wright
Eastex Crude Company

#7

On Mar 1, 9:20 am, "Chandru Murthi"
<cmur_xyz_thi (AT) xyz_seeinggree_xyz_n (DOT) net> wrote:

Quote:

Isn't this BASIC object code corruption (Mark?) Have you tried recompiling
the program?

Chandru"mwright" <wright.m... (AT) gmail (DOT) com> wrote in message

news:1172614910.068578.50350 (AT) q2g2000cwa (DOT) googlegroups.com...

I'm running a basic program which is called from a proc. This type
situation is EXTREMELY common throughout our software. The proc
selects records, & the program processes them. This particular
program isn't one that is run very often, perhaps ever, & is resulting
in the following error, shortly after entering the basic program, but
before it actually begins to process any records. It APPEARS as
though it has to do with the opening of a particular DICT file in the
program, but I've been unable to stumble across a fix so far. The
abort message is as follows:

Unrecognized Opcode @ br.store.rtn:05B

O=Logoff / Q=Quit / <CR>=Go to debugger ?

Does anyone have any idea what the error signifies??

Thanks in advance,

Mark Wright
Eastex Crude Company

Patrick/Chandru,

I've done everything I know to do, INCLUDING this. I created a new
"dummy" file, copied all the dict/data items to it, deleted the
original file, & renamed the "dummy" file to the original. And STILL
I get the same problem. I've recompiled, copied the program to a new
item, recompiled it, & called the new program from the proc, ALL with
the same results. No one new has been on/near the system,
either!!! :^) That I know of.

I honestly don't know what else to do at this point.

MW

#8

Quote:

I've done everything I know to do, INCLUDING this. I created a new
"dummy" file, copied all the dict/data items to it, deleted the
original file, & renamed the "dummy" file to the original. And STILL
I get the same problem. I've recompiled, copied the program to a new
item, recompiled it, & called the new program from the proc, ALL with
the same results. No one new has been on/near the system,
either!!! :^) That I know of.

I honestly don't know what else to do at this point.

As was suggested above, I would run the program with the (D option so
it hits the debugger on line 1, and then step through it to see what
line it blows up on. If it blows up before it even hits the debugger,
then your problem might be worse than you think.

#9

On Mar 1, 12:55 pm, "Tracy Raines" <livebl... (AT) gmail (DOT) com> wrote:

Quote:

I've done everything I know to do, INCLUDING this. I created a new
"dummy" file, copied all the dict/data items to it, deleted the
original file, & renamed the "dummy" file to the original. And STILL
I get the same problem. I've recompiled, copied the program to a new
item, recompiled it, & called the new program from the proc, ALL with
the same results. No one new has been on/near the system,
either!!! :^) That I know of.

I honestly don't know what else to do at this point.

As was suggested above, I would run the program with the (D option so
it hits the debugger on line 1, and then step through it to see what
line it blows up on. If it blows up before it even hits the debugger,
then your problem might be worse than you think.

Tracy,

I already know where it blows up, I just don't know WHY!!!!!!!!!!!!!!!

The program aborts with the weird error message shown above whenever
it tries to read from a particular DICT file. If I comment all those
reads out (probably 15 or so lines), it runs fine. If I comment out
the line that opens the DICT file, I get an error telling me I haven't
opened the required file when it gets to the aforementioned DICT
reads, just like I would expect.

Sorry for the confusion.

MW

#10

mwright wrote:
<snip>

Quote:

The program aborts with the weird error message shown above whenever
it tries to read from a particular DICT file. If I comment all those
reads out (probably 15 or so lines), it runs fine. If I comment out
the line that opens the DICT file, I get an error telling me I haven't
opened the required file when it gets to the aforementioned DICT
reads, just like I would expect.

Sorry for the confusion.

MW

Has the DICT portion of this file been cleared?

Have you done a LD on the file to make sure no one
has created any *additional* DICT portions?

<scratching head>
Patrick, <;=)