RE: MCH3601 - Pointer not set for location referenced

Thanks everyone for all your input.
The 3rd party app is Netcracker's API Gateway, runs 1 main job and 8 secondary jobs.
Two of Netcracker's other apps, (Connection Manager and ICAPI), are configured to communicate to the API Gateway.
The 8 secondary jobs get auto recycled daily at midnight, the main job on when the subsystem is ended/started.
Based on the from user, WSCUSER, we know it's coming from another of our Netracker app, WebSelfCare, which uses the Connection Manager to communicate to the API Gateway.
We also have jobs using RXS that communicate to ICAPI.
We had a long running process from RXS/ICAPI at the time, it was using the other APISTART jobs, not impacted.
The other APISTART jobs kept the WebSelfCare app running.
We probably won't be able to recreate the error.

From all various logs and time stamps, we might be able to find the transaction/account which triggered the error.

It will be reported, but probably no resolution found.
We don't get many of these, maybe 2 or 3 a year.
If it was a coding issue, I would expect to see more failures.

Subsystem/Job User Number User Type Pool Pty CPU Int Rsp AuxIO CPU% Function Status Threads
IC_GTWYP1 QSYS 283363 QSYS SBS 2 0 .1 0 .0 DEQW 2
APISTART IC_GTWYP1 402027 WSCUSER BCI 4 20 2.2 1551 .0 PGM-APISTART TIMW 1
APISTART IC_GTWYP1 402028 IC_GTWYP1 BCI 4 20 .3 0 .0 PGM-APISTART TIMW 1
APISTART IC_GTWYP1 402054 WSCUSER BCI 4 20 4405.9 30499 .1 PGM-APISTART TIMW 1
APISTART IC_GTWYP1 402059 APIUSER BCI 4 20 44.7 1397 .0 PGM-APISTART TIMW 1
APISTART IC_GTWYP1 402062 APIUSER BCI 4 20 4.3 914 .0 PGM-APISTART TIMW 1
APISTART IC_GTWYP1 402065 APIUSER BCI 4 20 3.0 395 .0 PGM-APISTART TIMW 1
APISTART IC_GTWYP1 402084 APIUSER BCI 4 20 1.4 279 .0 PGM-APISTART TIMW 1
APISTART IC_GTWYP1 402620 APIUSER BCI 4 20 .5 15 .0 PGM-APISTART TIMW 1
IC_GTWYP1 IC_GTWYP1 283369 IC_GTWYP1 ASJ 4 20 3258.0 0 .1 PGM-RUNGWY SIGW 28

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark S Waterbury
Sent: Sunday, March 16, 2014 3:01 PM
To: Midrange Systems Technical Discussion
Subject: Re: MCH3601 - Pointer not set for location referenced

Paul:

For any "3rd party application" I think you should be opening an incident with that vendor's customer support help desk ...

Do you have source code for this application? If so, then you might try to look at statement 59 in procedure DoProcess in module APIPROC2 in program (or service program) APIPROC ...

Do you have any "custom modifications' to this "3rd party application"?
For example, do you have any code written by someone in your shop that calls one or more programs or procedures that are part of this "3rd
party application"? If so, it is possible that one of them is calling
this procedure incorrectly, for example, not passing the required number of parameters, or passing a "null pointer" where a valid address is required, etc.

It might help if you could identify the vendor in question and the name of this particular "3rd party application" ...

HTH,

Mark S. Waterbury

On 3/16/2014 2:17 PM, Steinmetz, Paul wrote:
Periodically, our one 3rd party application results in a MCH3601 Pointer not set for location referenced. A pointer was used, either directly or as a basing
pointer, that has not been set to an address.

What could be the cause of the MCH3601?
What can be captured to resolve the issue?

MCH3601 Escape 40 03/16/14 08:36:45.622618 APIPROC ICGTWYP1OC *STMT APIPROC ICGTWYP1OC *STMT
From user . . . . . . . . . : WSCUSER
From module . . . . . . . . : APIPROC2
From procedure . . . . . . : DoProcess
Statement . . . . . . . . . : 59
To module . . . . . . . . . : APIPROC2
To procedure . . . . . . . : DoProcess
Statement . . . . . . . . . : 59
Message . . . . : Pointer not set for location referenced.
Cause . . . . . : A pointer was used, either directly or as a basing
pointer, that has not been set to an address.
CEE9901 Escape 30 03/16/14 08:36:45.623605 QLEAWI QSYS *STMT APISTART ICGTWYP1O 00BD
From user . . . . . . . . . : WSCUSER
From module . . . . . . . . : QLEDEH
From procedure . . . . . . : Q LE leDefaultEh
Statement . . . . . . . . . : 204
Message . . . . : Application error. MCH3601 unmonitored by APIPROC at
statement 0000000059, 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 APIPROC APIPROC2 DoProcess. The program was
stopped at the high-level language statement number(s) 0000000059 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.

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.com/

--
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.