Including a runtime message file

When you are running a freestanding environment and runtime messages are required, you must explicitly include a message file at link-edit time. One of the three following modules can be included to produce these messages:

EDCXLANE: Creates runtime error messages in uppercase and lowercase English
EDCXLANU: Creates runtime error messages in uppercase English
EDCXLANK: Creates runtime error messages in Kanji

If one of these message routines is not included and an exception occurs, the program could terminate without displaying a message. These error messages are directed to stderr. Refer to z/OS Language Environment Debugging Guide for more information.

Table 1 contains the abend codes and reason codes specific to the system programming facilities.

Table 1. Abend and reason codes specific to system programming environments
Code Type	Code	Description
Abend	2100	No storage abend code
	2101	Error freeing storage
	2102	Error finding stack seg home
	2103	Error loading library
	2104	Error with heap allocation
	2105	Error with system level command
	2106	Error initializing statics
	2107	Error establishing error handler for EDCXSTRX
	2108	Error cleaning up heap for EDCXSTRX
	4000	Error when handling abend
Reason	7201	Error in initialization.
	7202	Error in termination.
	7203	Error when extending stack.
	7204	Error during longjmp/setjmp.
	7205	Can not locate static init. The routine EDCRCINT must be included in your module if you use the RENT compiler option.
	7206	Module EDCXABRT was not explicitly included at link edit time.
	7207	No initial heap allocation is specified and a heap is required.