Exit program not called. Reason code 2.

Our software has been installed on thousands of IBM machines without us ever
encountering this error.

Our software is simply a single library with programs, commands, files etc.

We do not use any exit programs or Adopt authorities or change anything
system related.



We now have a potential new customer that installed our software onto their
system without any issues (that we know of)

1. RSTLIB OURLIB

2. OURLIB/DDINSTALL





Here is the issue:

EVERY single command (starting with the first one DDINSTALL) in our software
that is executed generates an Exit program error.





Example: Exit point QIBM_QCA_CHG_COMMAND with format CHGC0100 does not
exist.



Cause . . . . . : The exit point specified does not exist. Recovery . . . :

Do one of the following and try the request again: -- Correct the spelling

of the exit point or format name. -- Ensure the exit point requested exists.



CPI0001 Information 20 04/15/15 15:45:09.237496 QCADRV2 QSYS 02CC QUIMNDRV
QSYS 055F

Message . . . . : Exit program not called. Reason code 2.



Cause . . . . . : An exit program for exit point QIBM_QCA_CHG_COMMAND for

command OURLIB/DDINSTALL was not called. Command processing will continue

without calling the exit program.

Possible reason codes are:

1 - Exit program / was registered but was not found. Either create the exit
program

or remove the exit program from the registration facility repository. The

Remove Exit Program (RMVEXITPGM) command can be used to remove the exit

program. The program was not found in the job name space.

2 - The exit program information could not be retrieved from the
registration facility

repository. See the previous messages in the joblog for more information.

Correct the condition and try your request again.



They also get

Exit point QIBM_QCA_RTV_COMMAND with format *ALL does not exist.



These errors occur on every single one of our commands, the IBM commands
execute without this error.



Of course this company has no IT department and they have nobody on staff
that knows anything about their system.

P.S. They do not have IBM support either (Surprise!)



Does anyone have any idea what could cause this?

Or where do I look for the possible cause?



Thanks

John