IBM OS/390 User Manual
•
acts as an ACB without RESET (add new records to existing file)
•
DISP=OLD overrides IDCAMS REPRO with REUSE
To rewrite a reusable data set -
/ / DLBL .....,VSAM,DISP=NEW
/ / DLBL .....,VSAM,DISP=NEW
•
acts as an ACB with RESET (delete old records, add new records)
•
DISP=NEW overrides IDCAMS REPRO with NOREUSE
Partition Independent File Names
VSE/VSAM partition independent file names start with the character % or
characters %%, for example %MY.FILE. These special characters cause the
partition identifier (or cpuid and partition identifier) to be appended to the file
name when it is DEFINED or accessed. In the example shown, the file name
would be MY.FILE.BG if the job was running in the background partition. Access
to the file is actually
characters %%, for example %MY.FILE. These special characters cause the
partition identifier (or cpuid and partition identifier) to be appended to the file
name when it is DEFINED or accessed. In the example shown, the file name
would be MY.FILE.BG if the job was running in the background partition. Access
to the file is actually
dependent on the partition in which the job is running.
Again referring to the example, the same job running in the Foreground 4
partition would access file MY.FILE.F4.
partition would access file MY.FILE.F4.
OS/390 does not have partitions. It has address spaces. An address space does
not have an external identifier. Address space independence is automatically
provided for all temporary data sets.
not have an external identifier. Address space independence is automatically
provided for all temporary data sets.
VSE partition independent files are frequently used for
″
temporary
″
work files.
They should be converted to OS/390 temporary data sets. An OS/390 temporary
data set is specified by a data set name beginning with the character & or the
characters &&. OS/390 supports temporary VSAM data sets only with DFSMS.
VSE applications that use permanent partition independent files will require
another data set naming convention to operate correctly under OS/390.
data set is specified by a data set name beginning with the character & or the
characters &&. OS/390 supports temporary VSAM data sets only with DFSMS.
VSE applications that use permanent partition independent files will require
another data set naming convention to operate correctly under OS/390.
VSE/VSAM BACKUP/RESTORE and VSE FASTCOPY
IDCAMS BACKUP/RESTORE is used only for VSE VSAM files, while FASTCOPY is
used for non-VSAM and full volume backups. FASTCOPY has a stand-alone
component. Equivalent functions are provided in OS/390 via Access Methods
Services (EXPORT/IMPORT) for VSAM, DFSMS/MVS utilities (IEBGENER,
IEBCOPY and so on) for non-VSAM, and the Data Set Services component of
DFSMS (DFSMSdss) for data sets (VSAM and non-VSAM) and full volume dumps.
Archive tapes created by VSE/VSAM BACKUP/RESTORE or VSE FASTCOPY
cannot be processed by DFSMSdss. Tapes produced by VSE/VSAM EXPORT or
REPRO may be processed by OS/390 VSAM. Any non-portable archive tapes
should be restored to DASD using the appropriate VSE utilities. Then the DASD
files should be dumped to tape using a backup technique compatible with
OS/390 backup/restore programs such as DFSMSdss. This needs to be done
during the OS/390 migration while both operating systems (VSE and OS/390) are
available.
used for non-VSAM and full volume backups. FASTCOPY has a stand-alone
component. Equivalent functions are provided in OS/390 via Access Methods
Services (EXPORT/IMPORT) for VSAM, DFSMS/MVS utilities (IEBGENER,
IEBCOPY and so on) for non-VSAM, and the Data Set Services component of
DFSMS (DFSMSdss) for data sets (VSAM and non-VSAM) and full volume dumps.
Archive tapes created by VSE/VSAM BACKUP/RESTORE or VSE FASTCOPY
cannot be processed by DFSMSdss. Tapes produced by VSE/VSAM EXPORT or
REPRO may be processed by OS/390 VSAM. Any non-portable archive tapes
should be restored to DASD using the appropriate VSE utilities. Then the DASD
files should be dumped to tape using a backup technique compatible with
OS/390 backup/restore programs such as DFSMSdss. This needs to be done
during the OS/390 migration while both operating systems (VSE and OS/390) are
available.
IKQVDU - Volume Cleanup
This VSE/VSAM utility does not exist in OS/390 VSAM. The IKQVDU functions
″
SCRATCH DSN
″
and
″
RESET OWNERSHIP
″
were used to remove unwanted
VSE/VSAM data spaces from a volume and to turn off the VSAM
″
Ownership Bit
″
124
VSE to OS/390 Migration Workbook