Version upgrade from HULFT Ver.8
Restoration of new release
Modify Example 1 of JCL shown below and execute the modified JCL to restore the member name 'VERUP8' from HULFT JCL library (HULFT.V10.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.V10.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=(VERUP8)
|
DD Name |
Value |
Description |
|---|---|---|
|
IN |
HULFT.V10.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 'VERUP8' 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 JCL library
-
HULFT load module library
-
HULFT ISPF panel library
-
HULFT ISPF message library
-
HULFT parameter library
Note that you must re-create the HULFT load module library.
[Re-creation of the HULFT load module library (HULFT.LOAD)]
You need to change the type in DSNTYPE of the HULFT load module library.
Beginning with HULFT10, you must store the HULFT load module library in the PDSE data set.
Rename the existing HULFT load module library and back it up.
The following shows the attributes for the HULFT load module library that is newly created:
|
Capacity (CYL) |
Attribute |
||||
|---|---|---|---|---|---|
|
Primary |
Organization |
Record Format |
Record Length |
Block Size |
DSNTYPE |
|
50 |
PO |
U |
0 |
19069 |
LIBRARY |
Executing Example 2 of JCL for "VERUP8" re-creates the HULFT load module library.
//VERUP JOB CLASS=A,MSGCLASS=B
//*
//JCLGEN EXEC PGM=IEBCOPY
//IN DD DSN=HULFT.V10.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=(BACKUP7,BACKUP8,BACKUP10)
SELECT M=(HULVSAM,LOGVSAM)
SELECT M=(XRFILCNV,XRLOGCNV)
SELECT M=(SMPLOGAP)
//PNLGEN EXEC PGM=IEBCOPY
//IN DD DSN=HULFT.V10.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))
//*
//MSGGEN EXEC PGM=IEBCOPY
//IN DD DSN=HULFT.V10.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))
//*
//PARMGEN EXEC PGM=IEBCOPY
//IN DD DSN=HULFT.V10.PARMLIB,DISP=SHR
//OUT DD DSN=HULFT.PARMLIB,UNIT=SYSDA,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))
//*
//LOADGEN EXEC PGM=IEBCOPY
//IN DD DSN=HULFT.V10.LOAD,DISP=SHR
//OUT DD DSN=HULFT.LOAD,UNIT=SYSDA,
// VOL=SER=HUL001,DSNTYPE=LIBRARY,
// DCB=(DSORG=PO,RECFM=U,LRECL=0,BLKSIZE=19069),
// DISP=(NEW,CATLG),SPACE=(CYL,(50))
//SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(5))
//SYSUT4 DD UNIT=SYSDA,SPACE=(CYL,(5))
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
COPY OUTDD=OUT,INDD=IN
//*
//
|
DD Name |
Value |
Description |
|---|---|---|
|
IN |
HULFT.V10.JCL |
HULFT JCL library (HULFT installation file) |
|
OUT |
HULFT.JCL |
HULFT JCL library (installation destination file) |
|
IN |
HULFT.V10.JPN.PANEL |
HULFT ISPF panel library (JPN HULFT installation file) |
|
OUT |
HULFT.PANEL |
HULFT ISPF panel library (installation destination file) |
|
IN |
HULFT.V10.JPN.MSG |
HULFT ISPF message library (JPN HULFT installation file) |
|
OUT |
HULFT.MSG |
HULFT ISPF message library (installation destination file) |
|
IN |
HULFT.V10.PARMLIB |
HULFT parameter library (HULFT installation file) |
|
OUT |
HULFT.PARMLIB |
HULFT parameter library (installation destination file) |
|
IN |
HULFT.V10.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 |
If the version is Ver.8.4.0 or higher and lower than Ver.8.4.6, specify the following for the SYSIN definition card of the job step "JCLGEN."
COPY OUTDD=OUT,INDD=((IN,R)) SELECT M=(BACKUP7,BACKUP8,BACKUP10) SELECT M=(HULVSAM,LOGVSAM) SELECT M=(XRFILCNV,XRLOGCNV) SELECT M=(XRHSMVFY,SMPLOGAP)
If the version is Ver.8.1.0 or higher and lower than Ver.8.4.0, specify the following for the SYSIN definition card of the job step "JCLGEN."
COPY OUTDD=OUT,INDD=((IN,R)) SELECT M=(BACKUP7,BACKUP8,BACKUP10) SELECT M=(CNTLVSAM,FILEVSAM,HOSTVSAM,HULVSAM,LOGVSAM,XRCREATE) SELECT M=(XRFILCNV,XRLOGCNV) SELECT M=(QUEVSAM,OPLVSAM,HULSNDGO) SELECT M=(SMPHSAP,SMPLOGAP,XRHSMVFY)
-
If you execute the JCL, the environment for HULFT that you are currently using will be modified. The following operations include 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.
-
If you have installed HULFT Ver.6 as an upgrade from HULFT Ver.5, HULFT parameter library may not exist. Then, perform the New Installation of HULFT parameter library.
Definition in the APF-authorized Library
For details about the method of definition in the APF-authorized Library, refer to Definition in the APF-authorized Library.
Creation of HULFT Ver.10 system files
Re-create the following HULFT Ver.8 files in a format that can be used in HULFT Ver.10:
-
Send and Receive Management file
-
Host Information file
-
Send Control file
-
Send and Receive Log file
-
System Control file
For details about the size, refer to Calculation of the size of the VSAM file.
You must recalculate the size of the INDEX components. Calculate the size based on the Key Length.
When creating each file, you must also carry out the initialization processing.
Creation of the Send and Receive Management file
The procedure for creating the Send and Receive Management file for HULFT Ver.10 is shown below.
Modify the member name 'FILEVSAM' in HULFT JCL library and execute the JCL.
[Example of JCL]
//FILEVSAM JOB CLASS=A,MSGCLASS=B
//*------< VSAM DEFINE CLUSTER >---------------------------------------
//DEFCLSTR EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE HULFT.FILE
DEFINE CLUSTER -
(NAME(HULFT.FILE) -
INDEXED) -
DATA -
(NAME(HULFT.FILE.DATA) -
KEYS(54 0) -
SHAREOPTIONS(4 3) -
VOLUMES(HUL001) -
CYLINDERS(1 1) -
RECORDSIZE(610 22300)) -
INDEX -
(NAME(HULFT.FILE.IDX) -
VOLUMES(HUL001) -
CYLINDERS(1 1) -
SHAREOPTIONS(4 3))
//*------< FILE CREATE >---------------------------------------
//XRCREATE EXEC PGM=XRCREATE,REGION=1024K
//STEPLIB DD DSN=HULFT.LOAD,DISP=SHR
//XRLOG DD DUMMY
//XRLOG1 DD DUMMY
//XRLOG2 DD DUMMY
//XRFILE DD DSN=HULFT.FILE,DISP=SHR
//XRQUE DD DUMMY
//XRHOST DD DUMMY
//XRCNTL DD DUMMY
//XROPLC1 DD DUMMY
//XROPLC2 DD DUMMY
//XROPLF1 DD DUMMY
//XROPLF2 DD DUMMY
//SYSUDUMP DD SYSOUT=*
//
|
DD Name |
Value |
Description |
|---|---|---|
|
STEPLIB |
HULFT.LOAD |
HULFT load module library |
|
XRFILE |
HULFT.FILE |
Send and Receive Management file |
|
Parameter Name |
Value |
Description |
|---|---|---|
|
VOLUMES |
HUL001 |
Volume name |
|
CYLINDERS |
(*1) |
Capacity |
|
NAME |
HULFT.FILE |
Send and Receive Management File |
|
NAME |
HULFT.FILE.DATA |
Names of entries for data component of Send and Receive Management File |
|
NAME |
HULFT.FILE.IDX |
Names of entries for index component of Send and Receive Management File |
|
*1 |
: |
(1ST Extent Secondary) |
Creation of the Host Information file
The procedure for creating the Host Information file for HULFT Ver.10 is shown below.
Modify the member name 'HOSTVSAM' in HULFT JCL library and execute the JCL.
[Example of JCL]
//HOSTVSAM JOB CLASS=A,MSGCLASS=B
//*------< VSAM DEFINE CLUSTER >---------------------------------------
//DEFCLSTR EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE HULFT.HOST
DEFINE CLUSTER -
(NAME(HULFT.HOST) -
INDEXED) -
DATA -
(NAME(HULFT.HOST.DATA) -
KEYS(51 0) -
SHAREOPTIONS(4 3) -
VOLUMES(HUL001) -
CYLINDERS(1 1) -
RECORDSIZE(500 500)) -
INDEX -
(NAME(HULFT.HOST.IDX) -
VOLUMES(HUL001) -
CYLINDERS(1 1) -
SHAREOPTIONS(4 3))
//*------< FILE CREATE >---------------------------------------
//XRCREATE EXEC PGM=XRCREATE,REGION=1024K
//STEPLIB DD DSN=HULFT.LOAD,DISP=SHR
//XRLOG DD DUMMY
//XRLOG1 DD DUMMY
//XRLOG2 DD DUMMY
//XRFILE DD DUMMY
//XRQUE DD DUMMY
//XRHOST DD DSN=HULFT.HOST,DISP=SHR
//XRCNTL DD DUMMY
//XROPLC1 DD DUMMY
//XROPLC2 DD DUMMY
//XROPLF1 DD DUMMY
//XROPLF2 DD DUMMY
//SYSUDUMP DD SYSOUT=*
//
|
DD Name |
Value |
Description |
|---|---|---|
|
STEPLIB |
HULFT.LOAD |
HULFT load module library |
|
XRHOST |
HULFT.HOST |
Host Information file |
|
Parameter Name |
Value |
Description |
|---|---|---|
|
VOLUMES |
HUL001 |
Volume name |
|
CYLINDERS |
(*1) |
Capacity |
|
NAME |
HULFT.HOST |
Host Information File |
|
NAME |
HULFT.HOST.DATA |
Names of entries for data component of Host Information File |
|
NAME |
HULFT.HOST.IDX |
Names of entries for index component of Host Information File |
|
*1 |
: |
(1ST Extent Secondary) |
Creation of the Send Control file
The procedure for creating the Send Control file for HULFT Ver.10 is shown below.
Modify the member name 'QUEVSAM' in HULFT JCL library and execute the JCL.
[Example of JCL]
//QUEVSAM JOB CLASS=A,MSGCLASS=B
//*------< VSAM DEFINE CLUSTER >---------------------------------------
//DEFCLSTR EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE HULFT.QUEUE
DEFINE CLUSTER -
(NAME(HULFT.QUEUE) -
INDEXED) -
DATA -
(NAME(HULFT.QUEUE.DATA) -
KEYS(61 0) -
VOLUMES(HUL001) -
CYLINDERS(1 1) -
SHAREOPTIONS(4 3) -
RECORDSIZE(7600 7600) -
CONTROLINTERVALSIZE(26624)) -
INDEX -
(NAME(HULFT.QUEUE.IDX) -
VOLUMES(HUL001) -
CYLINDERS(1 1) -
SHAREOPTIONS(4 3))
//*------< FILE CREATE >---------------------------------------
//XRCREATE EXEC PGM=XRCREATE,REGION=1024K
//STEPLIB DD DSN=HULFT.LOAD,DISP=SHR
//XRLOG DD DUMMY
//XRLOG1 DD DUMMY
//XRLOG2 DD DUMMY
//XRHOST DD DUMMY
//XRFILE DD DUMMY
//XRQUE DD DSN=HULFT.QUEUE,DISP=SHR
//XRCNTL DD DUMMY
//XROPLC1 DD DUMMY
//XROPLC2 DD DUMMY
//XROPLF1 DD DUMMY
//XROPLF2 DD DUMMY
//SYSUDUMP DD SYSOUT=*
//
|
DD Name |
Value |
Description |
|---|---|---|
|
STEPLIB |
HULFT.LOAD |
HULFT load module library |
|
XRQUE |
HULFT.QUEUE |
Send Control File |
|
Parameter Name |
Value |
Description |
|---|---|---|
|
VOLUMES |
HUL001 |
Volume name |
|
CYLINDERS |
(*1) |
Capacity |
|
NAME |
HULFT.QUEUE |
Send Control File |
|
NAME |
HULFT.QUEUE.DATA |
Names of entries for data component of Send Control File |
|
NAME |
HULFT.QUEUE.IDX |
Names of entries for index component of Send Control File |
|
*1 |
: |
(1ST Extent Secondary) |
Creation of the Send and Receive Log file
The procedure for creating the Send and Receive Log file for HULFT Ver.10 is shown below.
Modify the member name 'LOGVSAM' in HULFT JCL library and execute the JCL.
[Example of JCL]
//LOGVSAM JOB CLASS=A,MSGCLASS=B
//*------< VSAM DEFINE CLUSTER >---------------------------------------
//DEFCLSTR EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE HULFT.LOG
DELETE HULFT.LOG.PATH1
DELETE HULFT.LOG.PATH2
DEFINE CLUSTER -
(NAME(HULFT.LOG) -
INDEXED -
REUSE) -
DATA -
(NAME(HULFT.LOG.DATA) -
KEYS(59 0) -
VOLUMES(HUL001) -
CYLINDERS(5 1) -
SHAREOPTIONS(4 3) -
RECORDSIZE(1600 1600) -
CONTROLINTERVALSIZE(26624)) -
INDEX -
(NAME(HULFT.LOG.IDX) -
VOLUMES(HUL001) -
CYLINDERS(1 1) -
SHAREOPTIONS(4 3))
DEFINE CLUSTER -
(NAME(HULFT.LOG.PATH1) -
INDEXED -
REUSE) -
DATA -
(NAME(HULFT.LOG.PATH1.DATA) -
KEYS(59 59) -
VOLUMES(HUL001) -
CYLINDERS(5 1) -
SHAREOPTIONS(4 3) -
RECORDSIZE(1600 1600) -
CONTROLINTERVALSIZE(26624)) -
INDEX -
(NAME(HULFT.LOG.PATH1.IDX) -
VOLUMES(HUL001) -
CYLINDERS(1 1) -
SHAREOPTIONS(4 3))
DEFINE CLUSTER -
(NAME(HULFT.LOG.PATH2) -
INDEXED -
REUSE) -
DATA -
(NAME(HULFT.LOG.PATH2.DATA) -
KEYS(9 118) -
VOLUMES(HUL001) -
CYLINDERS(5 1) -
SHAREOPTIONS(4 3) -
RECORDSIZE(1600 1600) -
CONTROLINTERVALSIZE(26624)) -
INDEX -
(NAME(HULFT.LOG.PATH2.IDX) -
VOLUMES(HUL001) -
CYLINDERS(1 1) -
SHAREOPTIONS(4 3))
//*
//*------< FILE CREATE >---------------------------------------
//XRCREATE EXEC PGM=XRCREATE,REGION=1024K
//STEPLIB DD DSN=HULFT.LOAD,DISP=SHR
//XRLOG DD DSN=HULFT.LOG,DISP=SHR
//XRLOG1 DD DSN=HULFT.LOG.PATH1,DISP=SHR
//XRLOG2 DD DSN=HULFT.LOG.PATH2,DISP=SHR
//XRHOST DD DUMMY
//XRFILE DD DUMMY
//XRQUE DD DUMMY
//XRCNTL DD DUMMY
//XROPLC1 DD DUMMY
//XROPLC2 DD DUMMY
//XROPLF1 DD DUMMY
//XROPLF2 DD DUMMY
//SYSUDUMP DD SYSOUT=*
//*------< LOGCNT >---------------------------------------
//XRLOGCNT EXEC PGM=XRLOGCNT,REGION=1024K
//STEPLIB DD DSN=HULFT.LOAD,DISP=SHR
//XRLOG DD DSN=HULFT.LOG,DISP=SHR
//XRLOG1 DD DSN=HULFT.LOG.PATH1,DISP=SHR
//XRLOG2 DD DSN=HULFT.LOG.PATH2,DISP=SHR
//XRCRD DD *
LOGCNT=ALL
//SYSOUT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//
|
DD Name |
Value |
Description |
|---|---|---|
|
STEPLIB |
HULFT.LOAD |
HULFT load module library |
|
XRLOG |
HULFT.LOG |
Send and Receive Log File ID Key File |
|
XRLOG1 |
HULFT.LOG.PATH1 |
Send and Receive Log Host Name Key File |
|
XRLOG2 |
HULFT.LOG.PATH2 |
Send and Receive Log Date Key File |
|
Parameter Name |
Value |
Description |
|---|---|---|
|
VOLUMES |
HUL001 |
Volume name |
|
CYLINDERS |
(*1) |
Capacity |
|
NAME |
HULFT.LOG |
Send and Receive Log File ID Key File |
|
NAME |
HULFT.LOG.DATA |
Names of entries for data component of Send and Receive Log File ID Key File |
|
NAME |
HULFT.LOG.IDX |
Names of entries for index component of Send and Receive Log File ID Key File |
|
NAME |
HULFT.LOG.PATH1 |
Send and Receive Log Host Name Key File |
|
NAME |
HULFT.LOG.PATH1.DATA |
Names of entries for data component of Send and Receive Log Host Name Key File |
|
NAME |
HULFT.LOG.PATH1.IDX |
Names of entries for index component of Send and Receive Log Host Name Key File |
|
NAME |
HULFT.LOG.PATH2 |
Send and Receive Log Date Key File |
|
NAME |
HULFT.LOG.PATH2.DATA |
Names of entries for data component of Send and Receive Log Date Key File |
|
NAME |
HULFT.LOG.PATH2.IDX |
Names of entries for index component of Send and Receive Log Date Key File |
|
*1 |
: |
(1ST Extent Secondary) |
Creating the System Control file
The procedure for creating the System Control file for HULFT Ver.10 is shown below.
Modify the member name "CNTLVSAM" in HULFT JCL library and execute the JCL.
Then, you must specify the created System Control file in the System Environment Settings.
For details, refer to System Environment Settings.
[Example of JCL]
//CNTLVSAM JOB CLASS=A,MSGCLASS=B
//*------< VSAM DEFINE CLUSTER >---------------------------------------
//DEFCLSTR EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE HULFT.SYSCNTL
DEFINE CLUSTER -
(NAME(HULFT.SYSCNTL) -
INDEXED) -
DATA -
(NAME(HULFT.SYSCNTL.DATA) -
KEYS(52 0) -
VOLUMES(HUL001) -
CYLINDERS(1 1) -
SHAREOPTIONS(4 3) -
RECORDSIZE(400 400) -
CONTROLINTERVALSIZE(18432)) -
INDEX -
(NAME(HULFT.SYSCNTL.IDX) -
VOLUMES(HUL001) -
CYLINDERS(1 0) -
SHAREOPTIONS(4 3))
//*------< FILE CREATE >---------------------------------------
//XRCREATE EXEC PGM=XRCREATE,REGION=1024K
//STEPLIB DD DSN=HULFT.LOAD,DISP=SHR
//XRLOG DD DUMMY
//XRLOG1 DD DUMMY
//XRLOG2 DD DUMMY
//XRHOST DD DUMMY
//XRFILE DD DUMMY
//XRQUE DD DUMMY
//XRCNTL DD DSN=HULFT.SYSCNTL,DISP=SHR
//XROPLC1 DD DUMMY
//XROPLC2 DD DUMMY
//XROPLF1 DD DUMMY
//XROPLF2 DD DUMMY
//SYSUDUMP DD SYSOUT=*
//
|
DD Name |
Value |
Description |
|---|---|---|
|
STEPLIB |
HULFT.LOAD |
HULFT load module library |
|
XRCNTL |
HULFT.SYSCNTL |
System Control file |
|
Parameter Name |
Value |
Description |
|---|---|---|
|
VOLUME |
HUL001 |
Volume name |
|
CYLINDERS |
(*1) |
Capacity |
|
NAME |
HULFT.SYSCNTL |
System Control file |
|
NAME |
HULFT.SYSCNTL.DATA |
Names of entries for data component of the System Control file |
|
NAME |
HULFT.SYSCNTL.IDX |
Names of entries for index component of the System Control file |
|
*1 |
: |
(1ST Extent Secondary) |
Conversion of system files
The procedure for converting HULFT Ver.8 system files so that they can be used in HULFT Ver.10 is shown below.
Conversion of the Send and Receive Management file and the Host Information file
Convert HULFT Ver.8 Send and Receive Management file and Host Information file so that they can be used in HULFT Ver.10. Modify the member name 'XRFILCNV' in HULFT JCL library and execute the JCL.
[Example of JCL]
//XRFILCNV JOB CLASS=A,MSGCLASS=B //XRFILCNV EXEC PGM=XRFILCNV,REGION=1024K,PARM='V8,HULCHARSET=939' //STEPLIB DD DSN=HULFT.LOAD,DISP=SHR //XRBKUP DD DSN=HULFT.FILE.BKUP,DISP=SHR //XRBKUP2 DD DSN=HULFT.HOST.BKUP,DISP=SHR //XRFILE DD DSN=HULFT.FILE,DISP=SHR //XRHOST DD DSN=HULFT.HOST,DISP=SHR //
|
DD Name |
Value |
Description |
|---|---|---|
|
STEPLIB |
HULFT.LOAD |
HULFT load module library |
|
XRBKUP |
HULFT.FILE.BKUP |
Send and Receive Management File (backup file) (*1) |
|
XRBKUP2 |
HULFT.HOST.BKUP |
Host Information File (backup file) (*1) |
|
XRFILE |
HULFT.FILE |
Send and Receive Management File |
|
XRHOST |
HULFT.HOST |
Host Information file |
|
Parameter Name |
Value |
Description |
|---|---|---|
|
PARM= |
V8 |
Version of migration source HULFT |
|
HULCHARSET= |
939 |
CCSID (Coded Character Set Identifier) of the emulator |
|
*1 |
: |
Specify backup files created with the following procedure: |
-
Management information fields that do not exist in HULFT before a version upgrade are set to their default values.
-
We recommend that you set the default value "0" for the following fields in HULFT10. However, when you perform a version upgrade, the field values in the environment before the migration will be inherited.
-
Transfer Block Length (BLOCKLEN) in the Send Management Information
-
Transfer Block Count (BLOCKCNT) in the Send Management Information
Modify the setting values after a version upgrade as necessary.
-
Conversion of the Send and Receive Log file
The procedure for converting HULFT Ver.8 Send and Receive Log file so that it can be used in HULFT Ver.10 is shown below.
Modify the member name 'XRLOGCNV' in HULFT JCL library and execute the JCL.
[Example of JCL]
//XRLOGCNV JOB CLASS=A,MSGCLASS=B //XRLOGCNV EXEC PGM=XRLOGCNV,REGION=1024K,PARM='V8,HULCHARSET=939' //STEPLIB DD DSN=HULFT.LOAD,DISP=SHR //XRBKUP DD DSN=HULFT.LOG.BKUP,DISP=SHR //XRLOG DD DSN=HULFT.LOG,DISP=SHR //XRLOG1 DD DSN=HULFT.LOG.PATH1,DISP=SHR //XRLOG2 DD DSN=HULFT.LOG.PATH2,DISP=SHR //
|
DD Name |
Value |
Description |
|---|---|---|
|
STEPLIB |
HULFT.LOAD |
HULFT load module library |
|
XRBKUP |
HULFT.LOG.BKUP |
Send and Receive Log File (backup file) (*1) |
|
XRLOG |
HULFT.LOG |
Send and Receive Log File ID Key File |
|
XRLOG1 |
HULFT.LOG.PATH1 |
Send and Receive Log Host Name Key File |
|
XRLOG2 |
HULFT.LOG.PATH2 |
Send and Receive Log Date Key File |
|
Parameter Name |
Value |
Description |
|---|---|---|
|
RARM= |
V8 |
Version of migration source HULFT |
|
HULCHARSET= |
939 |
CCSID (Coded Character Set Identifier) of the emulator |
|
*1 |
: |
Specify backup files created with the following procedure: |
-
You cannot omit the PARM definition.
-
If you execute the Send and Receive Log Conversion program (XRLOGCNV) again, re-create the Send and Receive Log file.
Addition of information on log record count for Send and Receive Log file
Add the information on log record counts so that the Send and Receive Log file can be used in HULFT Ver.10. Modify the member name 'XRLOGCNT' in HULFT JCL library and execute the JCL.
[Example of JCL]
//XRLOGCNT JOB CLASS=A,MSGCLASS=B //* //XRLOGCNT EXEC PGM=XRLOGCNT,REGION=1024K //STEPLIB DD DSN=HULFT.LOAD,DISP=SHR //XRLOG DD DSN=HULFT.LOG,DISP=SHR //XRLOG1 DD DSN=HULFT.LOG.PATH1,DISP=SHR //XRLOG2 DD DSN=HULFT.LOG.PATH2,DISP=SHR //SYSOUT DD SYSOUT=* //XRCRD DD * LOGCNT=ALL //
|
DD Name |
Value |
Description |
|---|---|---|
|
STEPLIB |
HULFT.LOAD |
HULFT load module library |
|
XRLOG |
HULFT.LOG |
Send and Receive Log File ID Key File |
|
XRLOG1 |
HULFT.LOG.PATH1 |
Send and Receive Log Host Name Key File |
|
XRLOG2 |
HULFT.LOG.PATH2 |
Send and Receive Log Date Key File |
Creation or restoration of custom character table
If you are using custom character tables, you can continue to use them after a version upgrade.
Use one of the following methods to allow the use of custom character tables after an upgrade:
-
Restoration from HULFT load module backup files (Restoration from HULFT load module backup files)
-
Use of the definition card to generate a custom character table that you previously created (Use of the definition card to generate a custom character table)
-
Starting with HULFT Ver.6, the conversion of custom characters is carried out by using custom character tables, instead of using custom character conversion exit routines. In addition, in HULFT Ver.6 and higher, custom character conversion exit routines created in COBOL are no longer supported.
-
If you intend to use custom character tables created in HULFT lower than Ver.6.0.3, and specify '1' for Use Custom Character Table (GAIJIFILE) in the System Environment Settings after a version upgrade, perform the procedure in Use of the definition card to generate a custom character table to create the custom character tables.
For details about how to use custom character tables, refer to the following:HULFT10 for zOS Administration Manual :
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
Restoration from HULFT load module backup files
Restore the custom character tables from the backup files for HULFT load module created in preparation for the version upgrade. Refer to the following list for the custom character tables to be restored.
|
Input Code |
Output Code |
Custom Character Table Name |
|---|---|---|
|
IBM Kanji |
Shift-JIS |
ITSTBL |
|
IBM Kanji |
EUC-JP |
ITETBL |
|
IBM Kanji |
JEF |
ITJTBL |
|
IBM Kanji |
UTF-8 |
ITU8TBL |
|
Shift-JIS |
IBM Kanji |
STITBL |
|
EUC-JP |
IBM Kanji |
ETITBL |
|
JEF |
IBM Kanji |
JTITBL |
|
UTF-8 |
IBM Kanji |
U8TITBL, U8TITBL2 |
Use of the definition card to generate a custom character table
Specify the definition card for generating a custom character table that was created before the Version Upgrade, and execute the Custom Character Table Expand program (XRECTBL).
Re-creation of EBCDIC user tables
If you have created EBCDIC user tables in the environment before a version upgrade, use the JCL templates for EBCDIC user tables where you have modified member names that are shown in the list in Confirmation of EBCDIC User Table of Preparation for a version upgrade and create new EBCDIC user tables.
For details about incorporating EBCDIC user tables, refer to the following:
HULFT10 for zOS Administration Manual :
You cannot use the JCL templates for EBCDIC user tables that you used in HULFT before a version upgrade. Be sure to use the JCL templates for EBCDIC user tables that were restored from the provided media.
Settings for using the HULFT Management Console and HULFT TSO commands
Configure the settings required for use of the HULFT Management Console and HULFT TSO commands.
Registration of help messages
For information on how to register help messages when you use the Instant Transfer Send File Issuance command, refer to Registration of help messages.
Modification of the procedure
Configure one of the following settings according to operation.
-
Configuring settings in the logon procedure
Perform the following procedures:
-
Configuring settings after logging on
Perform the following procedures:
System Environment Settings
Refer to the System Environment Settings file (HULFT.PARMLIB(HULPRM)) in HULFT Ver.8 to edit the System Environment Settings file (HULFT.PARMLIB(HULPRM)) in HULFT Ver.10.
In order to use the new functions in HULFT, you must define each definition correctly.
For details about the System Environment settings, refer to the following:
HULFT10 for zOS Administration Manual :
-
If you want to use HULFT in Japanese, specify 'JPN' (Japanese) for HULFT Operation Language (HULLANG). Otherwise, specify 'ENG' (English).
-
If you have specified Operation Log EBCDIC Code (OPLEBCDIC), delete the setting by deleting the field itself. In HULFT Ver.8.1 or higher, we recommend that you specify HULFT Character Set.
If you specify Operation Log EBCDIC Code, the setting of Operation Log EBCDIC Code becomes valid, instead of the setting of HULFT Character Set.
-
In a HULFT version that is lower than Ver.8.4.0, the function for checking the requestor hosts was set with Request Acknowledge Host Check (APTHSTCHK). In HULFT Ver.8.4.0 and higher, you can set the function by specifying separate fields for each service type, as shown below:
-
Allow Send/Resend Request from Unregistered Host (ALLOWSNDREQ)
-
Allow Post-Receive Job Result Inquiry from Unregistered Host (ALLOWPOSTRJOBRSLT)
-
Allow Job Result Notification Request from Unregistered Host (ALLOWJOBRSLTNTFY)
-
Allow Remote Job Execution Request from Unregistered Host (ALLOWRMTJOBEXE)
If you have carried out a version upgrade, set the function for checking the requestor hosts by using the fields listed above.
For details about the observe setting functions for unregistered hosts, refer to the following:
HULFT10 for zOS Administration Manual :
HULFT10 for zOS Administration Manual :
-
-
In HULFT Ver.10.2.0 and higher, some of the parameters that were defined by using the execution parameters (for EXEC statement) of the resident programs of HULFT can now be set in the System Environment Settings. Check which settings have been added to the System Environment Settings, and hereafter configure those settings in the System Environment Settings and not by using the execution parameters (for EXEC statement). For details about the settings that have been added to the System Environment Settings, refer to the following:
HULFT10 for zOS Administration Manual :
-
For details about how to configure the settings for the Forced Strong Key mode, refer to Preparation before using Forced Strong Key mode.
-
Be sure to specify the System Control file created in the following procedure for System Control File Name (CONTROL-FILE):
Creation of HULFT Ver.10 system files - Creating the System Control file
Registration of product information
Register the Serial Number and the Product Key in the System Environment Settings file (HULFT.PARMLIB(HULPRM)) so that HULFT runs. For details about registration methods, refer to Registration of the product information.
Definition of the OMVS segment
For details about how to define the OMVS segment, refer to Definition of the OMVS segment.
If you will start HULFT with the same job (PROC) name in an environment where HULFT system is already running, you do not need to perform this procedure, because the OMVS segment is already defined.
Registration of user ID and password in RACF
With HULFT Ver.7 and higher, you can now use the user ID and password you registered for user authentication in RACF (Resource Access Control Facility) when connecting from HULFT Manager. RACF is a function provided by IBM Security Server.
You can select either the method of using the conventional user definition file, or the method of using RACF. You can define this definition with User ID/Password Check (USRIDCHKMODE) in the System Environment Settings file (HULFT.PARMLIB(HULPRM)). For details, refer to the following:
HULFT10 for zOS Administration Manual :
If you switch to using RACF in HULFT Ver.10, you must register in RACF the user ID and password that you registered in the user definition file in the environment for the previous version. Check the definition for the user definition file (DD name: XRPASSWD) for the Startup JCL of the Observe program (XRACCPT), and register the user ID and password in RACF. For details about user defined files, refer to the following:
HULFT10 for zOS Administration Manual :
Editing of Observe Definition files
Refer to the Observe Definition file (HULAPT) in HULFT Ver.8 to edit the Observe Definition file (HULAPT) in HULFT Ver.10.
When you edit the Observe Definition file, do not delete any services, even if they are not defined in the Observe Definition file for HULFT Ver.8.
For details about how to edit the Observe Definition file, refer to the following:
HULFT10 for zOS Administration Manual :
Then, perform the procedure in Modifications to the JCL following a version upgrade.