Re: SQL0443, RNX8001 from calling stored procedure on remote machine.

I can duplicate this in Run SQL Scripts now...
If I connect to the remote database with the user used in the job.

CALL ROUTINES.GDSSYS002 (0, 0, 0, 0);
SQL State: 38501 Vendor Code: -443 Message: [CEE9901] Application error.
RNX8001 unmonitored by GDSSYS002 at statement *N, instruction X'0000'.
Cause . . . . . : The application ended abnormally because an exception
occurred and was not handled. The name of the program to which the
unhandled exception is sent is GDSSYS002 GDSSYS002 _QRNP_PEP_GDSSYS002.
The program was stopped at the high-level language statement number(s) *N
at the time the message was sent. If more than one statement number is
shown, the program is an optimized ILE program. Optimization does not
allow a single statement number to be determined. If *N is shown as a
value, it means the real value was not available. Recovery . . . : See
the low level messages previously listed to locate the cause of the
exception. Correct any errors, and then try the request again.

I used the tools within Run SQL Script to look at the job log of the
server job on the server. I saw
MCH1001 Attempt to use permanent system object &1 without authority.
This helped but the object name would be nice.
So I looked up that joblog (twas nice that the tool gave me the job name,
user, number) using 5250 and saw
Attempt to use permanent system object GDSSYS002 without authority.
This helped.

Object type would be nice to know if it is the stored procedure, or the
program based off of it.

But from there I was able to determine it was the program by signing on as
the user involved, and calling the program from the command line.
New lpar, program was restored with the wrong owner. The right owner was
the group profile this user belonged to.



Rob Berendt