Share This:

This method of implementing upgrades is using a facility that is relatively recent in z/OS that allows the usage of MVS symbolic in aliases.

The net result of using this method is implementing or backing out is done by updating 2 lines in IEASYMxx.

A dataset naming convention has to be in place to allow the use of one of the qualifiers to indicate the delineation of the various iterations of the libraries. Something along the line of versions-release-modification level or PUTLEVEL, for example HLQ.VvRrMmm.BBLINK or HLQ.PUTyymmx.BBLINK.

 

The actual copy, move or creation of the libraries, which makes up the product, can and should be done ahead of time.

 

It works like a 3 course meal.

 

1-) Appetizer:

 

//* DEFINE ALIASES
//DEFINE   EXEC PGM=IDCAMS
//SYSPRINT DD   SYSOUT=*
//SYSIN    DD   *
/* ********     DEFINES FOR SYSTEM     ********  */
  DEFINE ALIAS (NAME(
HLQ.MAINVIEW.BBACTDEF) -
    SYMBOLICRELATE(HLQ.MAINVIEW
.&MVPUTLVL..BBACTDEF))
  DEFINE ALIAS (
NAME(HLQ.MAINVIEW.BBCLIB) -
    SYMBOLICRELATE(HLQ.MAINVIEW
.&MVPUTLVL..BBCLIB))
...

 

2-) Entrée

The symbolics in IEASYMxx in PARMLIB of z/OS itself.

 

BROWSE    SYS1.SND1PLEX.PARMLIB(IEASYM77) - 01.00    Line 00000000 Col 001 080
Command ===>                                                  Scroll ===> CSR
********************************* Top of Data **********************************
SYSDEF SYSNAME(SND1)
SYSDEF SYMDEF(&SYSR2='SNDR04')
SYSDEF SYMDEF(&TSOJCLP='$STDZ77')
SYSDEF SYMDEF(&SUFFIX='77')
SYSDEF SYMDEF(&BBIVAR='00')
SYSDEF SYMDEF(&MVPUTLVL='PUT1102B')
SYSDEF SYMDEF(&MVVOL='SND006')

 

3-) Deserts

Other members of PARMLIB referencing the various libraries (PROGXX, and others) do not require any change after the initial set-up.

 

BROWSE    SYS1.SND1PLEX.PARMLIB(PROG77) - 01.01      Line 00001126 Col 001 080
Command ===>                                                  Scroll ===> CSR
APF ADD /* BMC SOFTWARE */                                             11260000
    DSNAME(HLQ.MAINVIEW
.&MVPUTLVL..TOSZLINK)                           11270000
    VOLUME
(&MVVOL.)                                                    11280000
APF ADD /* BMC SOFTWARE  */                                            11290000
    DSNAME(HLQ.MAINVIEW
.&MVPUTLVL..TOSZRTCS)                           11300000
    VOLUME
(&MVVOL.)                                                    11310000
APF ADD /* BMC SOFTWARE  */                                            11320000
    DSNAME(HLQ.MAINVIEW
.&MVPUTLVL..BBLINK)                             11330000
    VOLUME
(&MVVOL.)                                                    11340000

 

and finally the digestive is when doing a LISTCAT on an entry you will see the following result:

 

ALIAS --------- HLQ.MAINVIEW.BBLINK
      IN-CAT --- CATALOG.ICF.UCATSND1
      HISTORY
        RELEASE----------------2
      ASSOCIATIONS
       
SYMBOLIC-HLQ.MAINVIEW.&MVPUTLVL..BBLINK

        RESOLVED-HLQ.MAINVIEW.PUT1102B.BBLINK ***

 

The activation of new symbolic does not required an IPL per se.

 

IBM provides a program IEASYMUP that allow updates on the fly of symbolics.

For the detail on how to use this program please consult Appendix B of this IBM Red Book: z/OS Planned Outage Avoidance Checklist [SG24-7328-00].

 

As well dynamic update to APF and LinkList is done using usual SET MVS commands.