I am getting the above error in a program in a production environment. Earlier in a development environment I didn't receive any error. The source code is the same, but the load modules for the two environments are different, as the compile JCLs are different. The development compile JCL does not work in production environment.
Using the development load module in production job gives no error.
The option used in Linking in Production is RMODE(ANY) and in the Job REGION=0M has been specified.
Can anyone please let me know of possible solutions to this problem?
Thanks in advance.
Thanks! I will talk to the Support guys in our company.
This program wasn't working in this environment before.
I was using the load module form development to run the program in production.
Also for the dev. module AMODE = ANY and RMODE = 24. Is there a difference between AMODE and DATA parameters.
In the prod. JCL there are DATA and RMODE options, but neither in dev. JCL.
Joined: 23 Nov 2006 Posts: 19270 Location: Inside the Matrix
Hopefully, your support people can explain why there are differences.
When i'm part of the group that makes "rules", one i strive for is that once a module is compiled/linked, if it not re-compiled in the target environment - just to prevent this sort of thing. Also, if the code is re-compiled/linked it juct became untested. . . .