++ASSIGN MCS

The ++ASSIGN MCS assigns a source identifier (source ID) to one or more specified SYSMODs, as long as those SYSMODs are in the SMPPTS data set by the end of RECEIVE processing.

Syntax

++ASSIGN MCS

Read syntax diagramSkip visual syntax diagram++ASSIGNSOURCEID(source_id) TO( ,sysmod_id )

Operands

SOURCEID
is a 1- to 64-character string identifying the source of the SYSMODs being processed. SMP/E associates the SOURCEID value with the SYSMODs named on the ++ASSIGN MCS. The SOURCEID value can consist of any nonblank character (X'41' through X'FE') except single quotation mark ('), asterisk (*), percent (%), comma (,), left parenthesis (() and right parenthesis ()).
TO
specifies the SYSMODs with which the source ID is to be associated.

Usage notes

  • The source ID specified on the ++ASSIGN statement is added to any source ID that was assigned to a specified SYSMOD by the RECEIVE command. It is also added to any source IDs currently associated with a specified SYSMOD that has already been received.
  • ++ASSIGN statements are processed only when the SMPPTFIN data set is processed.
    • If the whole SMPPTFIN data set is processed, all ++ASSIGN statements are processed.
    • If only selected SYSMODs are processed, the ++ASSIGN statements for those SYSMODs are processed.

    ++ASSIGN statements are not processed when only the SMPHOLD data set is being processed.

  • The SOURCEID and TO values must be validly specified and cannot be blank or null. For more information about source ID naming conventions, see Naming conventions for source IDs.
  • The source ID is not assigned to any SYSMODs that are not in the global zone.
  • The same SYSMOD cannot appear more than once on a single ++ASSIGN MCS.
  • If the same SYSMOD appears on more than one ++ASSIGN MCS, all the source IDs are associated with the SYSMOD.
  • The ++ASSIGN MCS is used in the SMPPTFIN data set and can be placed between, before, or after SYSMODs, ++FEATURE MCS, or ++PRODUCT MCS.

    It must be followed by one of the following: a ++APAR, ++FEATURE, ++FUNCTION, ++PRODUCT, ++PTF, or ++USERMOD MCS; another ++ASSIGN MCS; or an end-of-file. If one of these does not follow, SMP/E does not receive the SYSMOD being processed, and it skips the ++ASSIGN MCS.

Examples

Here are some examples of ++ASSIGN statements for SYSMODs from several preventive service levels that have been merged into the same ESO tape. A ++ASSIGN MCS has been placed between the groups of SYSMODs to identify their source:
++ASSIGN SOURCEID(PUT0701)  /* service level 0701.      */
TO(UZ12345,UZ12346).
++PTF(UZ12345)              /* PTF UZ12345              */.
++VER(Z038) FMID(HXP1100)   /* for MVS function HXP1100.*/.
++MOD(A) DISTLIB(DN554)     /* Update module A.         */.
A
++PTF(UZ12346)              /* PTF UZ12346              */.
++VER(Z038) FMID(HXP1200)   /* for MVS function HXP1200.*/.
++MOD(C) DISTLIB(DN554)     /* Update module C.         */.
C
            •
            •
            •
++ASSIGN SOURCEID(PUT0702)  /* service level 0702.      */
TO(UZ12347,UZ12348).
++PTF(UZ12347)              /* PTF UZ12347              */.
++VER(Z038) FMID(HXP1100)   /* for MVS function HXP1100.*/.
++IF FMID(HXP1200) THEN REQ(UZ12348).
++MOD(D) DISTLIB(DN554)     /* Update module D.         */.
D
++PTF(UZ12348)              /* PTF UZ12348              */.
++VER(Z038) FMID(HXP1200)   /* for MVS function HXP1200.*/.
++MOD(A) DISTLIB(AOS12)     /* Update module A.         */.
A
++MOD(B) DISTLIB(AOS12)     /* Update module B.         */.
B
            •
            •
            •