scottklement.com

Hi Scott,

It turns out that I had copied and pasted the code incorrectly. Below is the actual way it is in the programs. Sorry for the confusion.


CL program @@MT002CL - START====================================================
PGM

DCL VAR(&USER) TYPE(*CHAR) LEN(10)

CHGJOB LOG(4 00 ...

Hi Scott,

I included the code that is part of the CALL that's causing the error and left out the rest. What I'm showing passes parameters. Some of my tests where I removed the parameters also gave me the same MCH3601 error. I made the problem CALL statement bold and marked with an arrow to make it ...

I don't think it would be reproducible on another system. Currently this program also gives me the MCH3601 error when calling from the command line. I removed the parms from the program and in the command line call. It is compiled as an ILE SQL COBOL program. Some other programs are giving me this ...

I stripped the test down a little more to make sure nothing was getting in the way. I removed the parameters and linkage section from the program and called it from the command line. This program was working until a few weeks ago. It gets compiled the same now as it was before the problem.

CALL ...

Here's more detail. I left out entries prior to the couple just before the pointer not set message. Again, the statement that is giving the error is a CALL to the program and doesn't have parameters.


3800 - CALL PGM(@@UT007CB) /* The CALL command contains
parameters */
- RETURN /* RETURN due ...

This started occurring a few weeks ago and I haven't been able to diagnose the problem. All of a sudden, calls to subprograms started getting MCH3601 errors. Thinking that maybe something went because of the parameters being passed, I removed the parameters from both the calling and called programs ...