Procedure for the revision upgrade


[Content revised from the 8th edition]

Date of Revision

Description

March 5, 2024

Added "(6) Required memory sizes for resident programs"


 

After you complete the preparation for the Revision Upgrade, carry out the Revision Upgrade work in accordance with the following procedure.

(1) Restoration of new release

Modify Example 1 of JCL shown below and execute the modified JCL to restore the member name 'REVUP' from HULFT JCL library (HULFT.V8.JCL) for HULFT installation files restored in Procedure for restoration from the provided media to the existing HULFT JCL library (HULFT.JCL).

 

[Example 1 of JCL]

//INSTALL  JOB  CLASS=A,MSGCLASS=B                                              
//*                                                                             
//JCLGEN   EXEC PGM=IEBCOPY                                                     
//IN       DD   DSN=HULFT.V8.JCL,DISP=SHR                                       
//OUT      DD   DSN=HULFT.JCL,DISP=SHR                                          
//SYSUT3   DD   UNIT=SYSDA,SPACE=(CYL,(5))                                      
//SYSUT4   DD   UNIT=SYSDA,SPACE=(CYL,(5))                                      
//SYSPRINT DD   SYSOUT=*                                                        
//SYSIN    DD   *                                                               
    COPY  OUTDD=OUT,INDD=((IN,R))                                               
    SELECT M=(REVUP)                                                            
//*                                                                             

DD Name

Value

Description

IN

HULFT.V8.JCL

HULFT JCL library (HULFT installation file)

OUT

HULFT.JCL

HULFT JCL library (installation destination file)

Parameter Name

Value

Description

UNIT

SYSDA

UNIT

 

The restored 'REVUP' is shown in Example 2 of JCL below. Modify and execute this JCL to overwrite the existing releases of the following libraries with the new releases of the libraries from HULFT installation files:

  • HULFT load module library

  • HULFT ISPF panel library

  • HULFT ISPF message library

 

[Example 2 of JCL]

//REVUP    JOB  CLASS=A,MSGCLASS=B                                              
//*                                                                             
//PANEL    EXEC PGM=IEBCOPY                                                     
//IN       DD   DSN=HULFT.V8.JPN.PANEL,DISP=SHR                                 
//OUT      DD   DSN=HULFT.PANEL,DISP=SHR                                        
//SYSUT3   DD   UNIT=SYSDA,SPACE=(CYL,(5))                                      
//SYSUT4   DD   UNIT=SYSDA,SPACE=(CYL,(5))                                      
//SYSPRINT DD   SYSOUT=*                                                        
//SYSIN    DD   *                                                               
    COPY  OUTDD=OUT,INDD=((IN,R))                                               
//*                                                                             
//MSG      EXEC PGM=IEBCOPY                                                     
//IN       DD   DSN=HULFT.V8.JPN.MSG,DISP=SHR                                   
//OUT      DD   DSN=HULFT.MSG,DISP=SHR                                          
//SYSUT3   DD   UNIT=SYSDA,SPACE=(CYL,(5))                                      
//SYSUT4   DD   UNIT=SYSDA,SPACE=(CYL,(5))                                      
//SYSPRINT DD   SYSOUT=*                                                        
//SYSIN    DD   *                                                               
    COPY  OUTDD=OUT,INDD=((IN,R))                                               
//*                                                                             
//LOAD     EXEC PGM=IEBCOPY                                                     
//IN       DD   DSN=HULFT.V8.LOAD,DISP=SHR                                      
//OUT      DD   DSN=HULFT.LOAD,DISP=SHR                                         
//SYSUT3   DD   UNIT=SYSDA,SPACE=(CYL,(5))                                      
//SYSUT4   DD   UNIT=SYSDA,SPACE=(CYL,(5))                                      
//SYSPRINT DD   SYSOUT=*                                                        
//SYSIN    DD   *                                                               
    COPY  OUTDD=OUT,INDD=((IN,R))                                               
//*                                                                             
//                                                                              

DD Name

Value

Description

IN

HULFT.V8.JPN.PANEL

HULFT ISPF panel library (JPN HULFT installation file)

OUT

HULFT.PANEL

HULFT ISPF panel library (JPN installation destination file)

IN

HULFT.V8.JPN.MSG

HULFT ISPF message library (JPN HULFT installation file)

OUT

HULFT.MSG

HULFT ISPF message library (JPN installation destination file)

IN

HULFT.V8.LOAD

HULFT load module library (HULFT installation file)

OUT

HULFT.LOAD

HULFT load module library (installation destination file)

Parameter Name

Value

Description

UNIT

SYSDA

UNIT

Note
  • If you execute the JCL, the environment for HULFT that you are currently using will be modified. The following operations include work that involves the use of backup files. Before starting this work, be sure to create backup files of HULFT as explained in Backup in HULFT Ver.8.

  • Since new members may be added and the number of members in HULFT load module library may increase, the capacity of the existing library may be insufficient.

(2) Definition in APF-authorized Library

For details about the method of definition in the APF-authorized Library, refer to Definition in the APF-authorized Library.

(3) Creation or restoration of custom character table

If you use one of the following methods to replace modules, you must restore or re-create the custom character table that was in use prior to module replacement:

  • Creation of a new HULFT load module library

  • Deletion of all members in HULFT load module library

 

Use either of the following methods to make the custom character table available for use:

  • Restoration from HULFT load module backup files (a) )

  • Use of the definition card to generate a custom character table that you previously created (b) )

a) Restoration from HULFT load module backup files

Restore custom character tables from the backup files for HULFT load module created in preparation for the Revision Upgrade. Refer to the following list for the custom character tables to be restored.

Table 11.1 List of Custom Character Tables

Input Code

Output Code

Custom Character Table Name

IBM Kanji

Shift-JIS

ITSTBL

IBM Kanji

EUC-JP

ITETBL

IBM Kanji

JEF

ITJTBL

IBM Kanji

KEIS

ITKTBL

IBM Kanji

NEC

ITNTBL

IBM Kanji

UTF-8

ITU8TBL

Shift-JIS

IBM Kanji

STITBL

EUC-JP

IBM Kanji

ETITBL

JEF

IBM Kanji

JTITBL

KEIS

IBM Kanji

KTITBL

NEC

IBM Kanji

NTITBL

UTF-8

IBM Kanji

U8TITBL, U8TITBL2

b) Use of definition card to generate custom character table

Specify the definition card for generating a custom character table that was created before the Revision Upgrade, and execute the Custom Character Table Expand program (XRECTBL).

(4) Re-creation of EBCDIC user tables

If you have created EBCDIC user tables in the environment before the Revision Upgrade, use the JCL templates for EBCDIC user tables to create new EBCDIC user tables.

In the JCL templates for EBCDIC user tables, you can specify the conversion tables that you used to create the EBCDIC user tables in the environment before the Revision Upgrade.

For details, refer to Administration Manual.

(5) System Environment Settings

The following fields were added to the System Environment Settings due to improvements to functions in HULFT Ver.8.4.1.

Field name:

Storage for Code Conversion Table

Tag name:

CODE-CONVERSION-LOCATION

Edit the System Environment Settings File (HULPRM) for HULFT Ver.8 as necessary.

In order to use the new functions in HULFT, you must define each definition correctly.

For details about the System Environment settings, refer to Administration Manual.

(6) Required memory sizes for resident programs

For details about the required memory sizes for resident programs, refer to Required memory sizes for resident programs.

 

The Revision Upgrade procedure is now complete.