Customized ADSMVS60 module shorter than the original one

Products

• Disk Backup and Restore - MVS
• DISK BACKUP AND RESTORE- ADD-ON OPTIO
• DISK BACKUP AND RESTORE

Issue/Introduction

The DISK SVC module ADSMVS60 is available as source code in CCUWSAMP and can be customized as described in Disk tech guide for Configuring Your Product 

If the DISK SVC module ADSMVS60 is installed using Usermod SDU1811 provided in CCUWJCL member USERMOD1 the new load module is shorter than the original one supplied in CCUWLPA.

What is the reason for that? Is there something missing?

For example:

The ADSMVS60 module in CCUWLPA at PTF level RO87785 has a length of hex 1360 bytes.
AMBLIST with LISTLOAD OUTPUT=XREF,MEMBER=ADSMVS60 shows:

CONTROL SECTION                              

 

After installation of Usermod SDU1811 from CCUWJCL(USERMOD1) the length is hex 12B8.
AMBLIST shows, that the ADSMVS60 CSECT is shorter than before:

CONTROL SECTION                                

NOTE: The numbers in the example above may vary at different PTF levels for ADSMVS60.

Environment

Release: Disk-Backup and Restore 12.5

Resolution

The MLIST macro at the end of the source code includes the internal #MODID macro, which is not provided to customers in the CCUWMAC library. 

The #MODID macro is expanded only, if the module is assembled at Broadcom and not at the customer site and therefore the original module is longer than the module installed using USERMOD1.

NOTE: The #MODID macro contains level information only for the original module under SMPE control, like PTF level, assembly Date and Time. It does not contain any executable code, so there is no impact, if it is missing in the customized module.