z/OS Communications Server: SNA Network Implementation Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Considerations for changing load module names

z/OS Communications Server: SNA Network Implementation Guide
SC27-3672-01

If you only rename a load module on the MOSS disk and do not change the VTAMLST and NCPLOAD library members, the following problems might occur:
  • The load module does not activate if the name is changed only on the MOSS disk.
    If you code the following, the activation of the load module will not occur:
    F NET,LOAD,ID=NCPA,LOADMOD=NCPA,NEWNAME=NCPA2,ACTION=RENAME
    V NET,ACT,ID=NCPA,LOADMOD=NCPA2,LOADFROM=EXT,LOAD=YES
    VTAMLST or NCPLOAD library members have not been changed.
    Note: VTAM® searches the VTAMLST file for load module NCPA2. If VTAM cannot find it, VTAM rejects the command. VTAM does not activate NCPA, even if the VTAMLST and NCPLOAD library member names have changed to NCPA2, because the NEWNAME parameter in the VTAMLST will not have a matching NCP generation on the NCPLOAD library. Remember, you changed only the external member names; you did not change the NEWNAME parameter and generate the load module.
  • The renamed load module cannot be replaced if it is renamed only on the MOSS disk. The following procedure will not work:
    F NET,LOAD,ID=NCPA,LOADMOD=NCPA,NEWNAME=NCPA2,ACTION=RENAME
    F NET,LOAD,ID=NCPA,ACTION=REPLACE,LOADMOD=NCPA2.
    VTAMLST and NCPLOAD library members were never changed.
    Note: VTAM processes the MODIFY LOAD command and tries to load NCPA2. VTAM looks for the NCPA2. Because VTAM does not find the NCPA2, VTAM fails the load. If the NCPA (the VTAMLST member) and NCPA (the NCPLOAD library member) are changed externally to NCPA2, the replace will occur.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014