They tend to use common JCL DD identifiers (in the OS, now z/OS operating systems) for their data sets: IDCAMS ("Access Method Services") generates and modifies Virtual Storage Access Method (VSAM) and Non-VSAM datasets.
The dataset has 80-byte records, and the system will choose the block size for the output: In the example above, SYSIN control cards are coming from an in-stream file, but you can instead point to any sequential file or a PDS member containing control cards or a temporary data-set, if you wish.
Therefore, IEBCOMPR is commonly used to verify that a backup copy of a data set is correct (exact match to the original).
So it is very useful when an exact match is expected, such as comparing load modules that have not been reblocked, or checking that a copy worked properly.
Some of the tasks that IEBCOPY can perform include the following: For the IEBCOPY utility, the required job control statements for a copy are as follows: The MYDD1 and MYDD2 DD statements are names chosen by the user for the partitioned input and output data sets, respectively; The defaults are SYSUT1 and SYSUT2.
These DDNAMEs are specified in the utility control statements to tell IEBCOPY the name of the input and output data sets.
Control statements define the fields of the records to be created, including position, length, format, and initialization to be performed.
This IEBEDIT routine copies the selected steps of the job onto the SYSUT2 output file (in this example, the internal reader).
Default: If START is omitted and only one EDIT statement is provided, the first job encountered in the input data set is processed.
If STEPNAME is omitted, the entire input job whose name is specified on the EDIT statement is copied.
Thus many mainframe shops make use of an option that automatically routes such tasks to the sort ICEGENER program instead of IEBGENER.
On some systems it is possible to send email from a batch job by directing the output to the "SMTP" external writer.
Starting in z/OS V1R7, ISAM data sets can no longer be processed (created, opened, copied or dumped).
ICKDSF ("Device Support Facility") installs, initializes and maintains DASD, either under an operating system, or standalone.
IEHDASDR[1]: 161–187 can performs several operations for direct access storage devices[b] (DASD) IBM eventually stopped adding support for new device types to IEHDASDR and directed customers to the free DSF for initializing volumes and to the chargeable DASDR (5740-UT1) and Data Facility/Data Set Services (5740-UT3, DF/DSS) for dump/restore.
IEHIOSUP updates relative track addresses (TTR) links for type IV Supervisor Call (SVC) routines in SYS1.SVCLIB.
[4] OPEN, CLOSE, and EOV functions are performed by a series of SVC modules that execute sequentially.
For performance reasons, to avoid a directory search each time, these tables contain the disk addresses of the modules rather than the names.
An example of an IEHLIST program to list a VTOC is very similar: IEHMOVE moves or copies collections of data.
However, DFSMS (System Managed Storage) environments are now common, and IBM does not recommend using the IEHMOVE utility in those.
The main advantage of using IEHMOVE is that you do not need to specify space or DCB information for the new data sets.
Because of the ease in moving groups of data sets or volumes, the IEHMOVE utility is generally favored by systems programmers.
The SYSUT1 DD statement specifies a DASD volume where three work data set required by IEHMOVE are allocated.
Some of the tasks that IEHPROGM can perform include the following: For cataloging: Select and format SMF records for tape errors.
These programs do not run under the control of an operating system Format direct access volumes and assign alternate tracks.
Verifies and/or replaces instructions and/or data in a load module, program object, or disk file.
Support for second-generation disk drives was provided by IBM program products such as 5734-SM1 and the later 5740-SM1 (DFSORT, alias ICEMAN, also SORT).
Keys can be any combination of EBCDIC or ASCII character data, zoned or packed-decimal, signed or unsigned fixed-point binary, or hexadecimal floating-point.
System Modification Program (SMP) is the vehicle for installing service on OS/360 and successors, replacing, e.g., stand-alone assembly, link edit and IMAPTFLE jobs.
Originally an optional facility, it is mandatory for MVS/SP and later, and the program product version, SMP/E, is included in the more recent systems, e.g., z/OS.