For information about migrating from a previous supported release of ISPF, refer to z/OS Migration.

It is also possible to migrate to z/OS V2R1.0 ISPF from earlier versions of ISPF.

Customization of ISPF had major changes in OS/390® Version 2 Release 8.0. When migrating from a version of OS/390 earlier than V2R8.0 you must convert your ISPF customization to the new format. See The ISPF Configuration Table for more information.

Major changes were made to the ISPF profiles for OS/390 V1R1.0. The profiles for earlier versions of ISPF are not compatible with z/OS® ISPF.

Use this information to help you during the transition stage.

• The z/OS V2R1.0 ISPF data sets are all named ISP.SISPxxxx and ISP.AISPxxxx. Version 4 ISPF data sets were named ISP.V4RxM0.xxxxx.
• Using SMP to install z/OS V2R1.0 ISPF deletes these licensed programs:
  • ISPF Version 3.n and ISPF/PDF Version 3.n
  • ISPF Version 4.n
  • OS/390 VnRn.0 ISPF
  • z/OS V1R2.0 ISPF
  • z/OS V1R5.0 ISPF
  • z/OS V1R6.0 ISPF
  • z/OS V1R7.0 ISPF
  • z/OS V1R8.0 ISPF
  During the transition stage, maintain the previous programs on a separate set of back-up packs or in a set of libraries that does not interfere with the execution of z/OS V2R1.0 ISPF.
• During the transition stage, it is assumed that the predecessor programs reside in the system pageable link pack area. ISPF and the new programs are assumed to be running from a set of execution libraries, as described in the z/OS Program Directory.
• Many of the modules in ISPF have the same names as modules in the previous licensed programs. Therefore, the ISPF module libraries should not be in your system LNKLSTxx definition during the transition period.
• During the initial testing period, ISPF should be run from the SISPLOAD and SISPLPA data sets created during the SMP APPLY processing step. Use a STEPLIB DD statement in the TSO LOGON procedure to accomplish this.

  If you are using the ISPF client/server feature or the z/OS UNIX Directory List utility, include the Language Environment® run-time library data sets SCEERUN and SCEERUN2 in the STEPLIB if they are not already in the LNKLIST.

  If you are also running with an ISPLLIB DD statement, you must include the z/OS V2R1.0 ISPF SISPLOAD and SISPLPA data sets in the ISPLLIB concatenation and remove any load library data sets from a previous version or release of ISPF.

• If only the top modules of z/OS V2R1.0 ISPF (ISPICP and alias ISPSTART as well as ISRPCP and alias entries PDF and ISPF) are in the step libraries, and the other load modules for the new and previous ISPF versions are in libraries allocated to the ISPLLIB ddname, both the old programs and the new programs can be executed concurrently under the same LOGON procedure. Concurrent execution assumes that a CLIST is used to provide the allocations of the other required ISPF libraries.
• Do not use the command names ISPF, PDF, or ISPSTART during the transition stage. Conflicts can occur if you invoke modules from earlier versions of ISPF with the same names. One solution is to rename the alias entries of the top ISPF modules in the step library to temporary names (for example, from ISPF to NEWISPF) until the transition stage is complete.
• After the transition stage, the z/OS V2R1.0 ISPF LPA-eligible load modules (data set SISPLPA) should be put in LPA, and the LPA-ineligible load modules (data set SISPLOAD) should be put in LNKLST. See Improving ISPF performance for more information. At that time, remove any DD statements for a STEPLIB or ISPLLIB definition of the ISPLOAD/ISPLPA data set from the LOGON procedure.
• Panel ISRLOGO was renamed to ISR@LOGO at z/OS Version 1 Release 1.0. If you have a modified version of ISR@PRIM, check that the correct panel value is used in the HELP Action Bar pull-down menu.