Migration considerations for sample procedures removal enhancement

Migration considerations introduced in IMS 15

In IMS 14 and earlier, the PROCLIB= parameter of the IMSGEN macro determines whether SYSGEN generates the IMS sample procedures in the IMS.PROCLIB dataset.

In IMS 15, the PROCLIB= parameter of the IMSGEN macro is obsolete. Only PROCLIB=NO is allowed. The default value for the parameter is changed to PROCLIB=NO. If PROCLIB=YES or PROCLIB=IMS is specified, the IMS system generates an MNOTE return code 2 with message G918 issued.

Delete the PROCLIB= keyword, or change PROCLIB=YES or PROCLIB=IMS to PROCLIB=NO to avoid a return code of 2 during stage 1 system definition.

If sample procedures are used, copy them from IMS.SDFSPROC to IMS.PROCLIB data set. Rename the data sets if necessary to match the original data sets generated by SYSGEN.

For sample procedures that are not delivered during the SMP/E processing in the IMS SDFSPROC library, use the DFSPROCB JCL to create the sample procedures and rename the sample procedures whose names do not match what they would have been if they are generated by system definition.

For more information about using the DFSPROCB JCL to create and rename certain sample procedures, see Running the DFSPROCB job to complete sample procedures.

In IMS 14 or earlier, most sample procedures generated by SYSGEN includes variable data that the IMS system sets based on various specifications in the stage 1 system definition macros. In IMS 15, because sample procedures are now provided as copy source during SMP processing, you can update these sample procedures so that the variable data matches what they would have been if generated by SYSGEN when it is necessary.

In IMS 14 or earlier, some sample procedures omit entire sections of the sample procedure, or have different versions of the sample procedure, depending on the type of system or other specifications in stage 1 system definition macros.

In IMS 15, the new sample procedures, in general, assume a ‘standard’ DB/DC system, because the actual system environment is not known. For each procedure that has conditionally-generated statements for ‘non-standard’ environments, the prolog in the sample procedure includes detailed instructions on how the sample procedure should be modified.