Assembly errors when applying usermod MZ2C023 member JCLMSG
search cancel

Assembly errors when applying usermod MZ2C023 member JCLMSG

book

Article ID: 407162

calendar_today

Updated On:

Products

JCLCheck Workload Automation

Issue/Introduction

Installed the last maintenance available for JCLCheck. When done, have re-apply JCLMSG - MZ2C023.

During the APPLY of the usermod, received assembly errors such as 

ASMA144E Begin-to-continue columns not blank

Environment

Release: All Releases
Component: JCLCheck Workload Automation

Cause

Customer wanted to replace the entire JCLMSG member and not update records within the existing member.

 

Resolution

To replace the entire copy of JCLMSG use SMP/E command ++SRC.

++USERMOD(MZ2C023)          /* IDENTIFY USERMOD */.    
++VER(Z038)  FMID(CAZ2C00) /* PRE(xxxxxxx) */ .        
++SRC (JCLMSG) DISTLIB(AAZ2SRC).                    
JCLMSG   TITLE 'JCLCHECK ERROR MESSAGES'                
     the rest of JCLMSG goes here                                             
$$         

 

Additional Information

The ++SRC statement in an SMP/E SYSMOD (System Modification) is used to introduce entirely new source code into a system or to replace existing source code. When SMP/E processes a SYSMOD containing a ++SRC statement, it creates or updates a SRC entry in the distribution and target zones, which describes the source code and its location.

The ++SRCUPD describes a single set of source update statements within a PTF, an APAR fix, or a USERMOD. It must immediately precede the source update statements within the SYSMOD.

The REWORK operand is used on header MCS statements like ++PTF, ++FUNCTION, ++APAR, or ++USERMOD within a SYSMOD. It indicates that the SYSMOD has been "reworked" by the software vendor (typically IBM) for minor changes, such as corrections or enhancements that do not warrant a new functional level. When SMP/E encounters a SYSMOD with the REWORK operand, and the REWORK level is higher than the previously installed version of the SYSMOD, it allows for automatic re-reception of the SYSMOD, even if it had been successfully received before. This facilitates the application of minor updates without requiring manual rejection and re-reception of the SYSMOD.