Installing required IMS links to z/OS

You must install these modules and procedures on your z/OS® system.

Stage 2 of IMS system definition might make the following modifications:

Binds the CTC Channel-end Appendage routine (if the MSC with the CTC option is defined) into IMS.SDFSRESL
Copies cataloged procedures into IMS.PROCLIB

In addition, you must run JCL to bind the following modules into IMS.SDFSRESL:

Type 2 SVC routine. If you specify TYPE=GEN,SVC2=xxx in the DFSIDEF macro, where xxx is the type 2 SVC number, sample JCL is generated that you can use to bind the module.
DBRC Type 4 SVC routine. If you specify TYPE=GEN,SVC4=yyy in the DFSIDEF macro, where yyy is the type 4 SVC number, sample JCL is generated that you can use to bind the module.

The following table provides is an overview of the actions needed in order for your IMS system to run under z/OS.

Table 1. Steps required to run under z/OS depending on the IMS environment
Action	DB batch system	DBCTL system	DB/DC system	DCCTL system
Bind the Type 2 SVC with the z/OS nucleus	Yes	Yes	Yes	Yes
Load the Type 2 SVC from SYS1.NUCLEUS using one of the following methods: The Nucleus Module Loader facilities A SYS1.IPLPARM member, NUCLSTxx A SYS1.PARMLIB member, NUCLSTxx	Yes	Yes	Yes	Yes
Bind the DBRC Type 4 SVC module into LPALIB (or, optionally, into an MLPA library)	Yes	Yes	Yes	Yes

The following table shows the modules that are required by the z/OS interface. The table shows the module name in its distribution library (IMS.ADFSLOAD) and the load module name in its target library (IMS.SDFSRESL) after the module is bound.

Table 2. z/OS interface modules
IMS.ADFSLOAD	IMS.SDFSRESL	Description
DFSVC200²	IGCiii²	Type 2 SVC Vector routine³
DSP00MVS¹	IGC00nnn¹	DBRC Type 4 SVC routine³
Notes: iii Specifies the Type 2 SVC number nnn Indicates the signed decimal Type 4 SVC number, for example, SVC 255 is 25E ¹ These modules must be bound with the RENT and REFR attributes. ² This module must be bound with the RENT, REFR, and SCTR Binder options. The modules are placed in SYS1.NUCLEUS. ³ You must run JCL to bind these modules.