Utility programs are pre-written programs, widely used in mainframes by system programmers and application developers to achieve day-to-day requirements, organising and maintaining data. A few of them are listed below with their functionality:. No operation utility. Used to return control to user and terminate. It is usually used to create empty dataset or delete an existing dataset. These utility programs need to be used with appropriate DD statements in a JCL in order to achieve the specified functionality.
|Published (Last):||17 December 2007|
|PDF File Size:||9.22 Mb|
|ePub File Size:||2.29 Mb|
|Price:||Free* [*Free Regsitration Required]|
MTO has a number of utility programs. Many of these emulate the functions of commonly-used mainframe batch utilities. This chapter also describes how, if required, you can write your own utility program; see the section Writing Your Own Utility Programs for details.
This section describes the mainframe emulation utilities. You can invoke these utilities in a JCL jobstream or REXX exec by using the same program names, data sets and commands as on the mainframe. The mainframe utilities emulated by MTO are:. This section describes the special considerations that apply when you use these utilities in a MTO environment.
It does not include information on behavior that is the same in mainframe and MTO environments. For full information on the mainframe utilities referred to in this section, see the relevant IBM documentation.
For example:. The rules for coding the statements are identical to the mainframe utility. Please refer to the mainframe documentation for instructions on writing and testing exit programs. It is compatible with the mainframe utility and should be defined as follows:. MFJSORT recognizes the same return codes from exit programs as the mainframe utility, as listed in the following table:.
This utility unloads some or all rows from up to XDB tables. You can unload data of any XDB built-in data type or distinct type. You can use some of these services for sequential data sets, partitioned data sets and generation data groups. These files usually have filename extensions of. Although the two-file structure affects the way that IDCAMS commands are processed, it does not change the final outcome of the commands.
The results of executing commands in a non-mainframe environment is the same as on the mainframe. All other parameters are ignored. For example, ABC. FILE is not permitted. It also automatically reindexes the data set to maintain consistency between the data and index files on the PC.
The alternate index is contained within the same file as the primary index. It creates the data and index files on the local machine and catalogs the data set name. The data set is not needed for any other purpose because MFJAMS implements this function in a different way to the mainframe. It deletes the local files associated with the data set and removes the entry from the catalog. It prints a complete data set or part of a data set in character format, hexadecimal format or both formats.
The data sets can have either VSAM or sequential organization. In both cases, the highest valid value is The data set is assumed to be readable if it can be opened without error or if it is locked to another process.
If the index is found to be unusable, the VERIFY command rebuilds the index by creating a new index file for the primary key and all alternate keys. The data portion of the data set is not changed.
It provides a dummy program facility by simply returning to the caller. It can be used, for example, in a job step to delete data sets at the appropriate time.
You can also use it to replace a program that does not have a version on the local machine, so that you can still test data set allocation and disposition for the job step. Input for such applications is, at a minimum:. How to You must also include any DD statements for sequential and VSAM data sets that are accessed by the application program. It accepts any record format, record length or data set organization supported by your COBOL development system.
If the data sets match, it ends with a return code of 0. If the two data sets do not match, when the MFJMATCH utility finds the first mismatch it writes the two records that differ to a third data set with asterisks under the columns that differ , then ends with a return code of Records following the first mismatch are not compared. The program control statements define search criteria that limit matching to a particular range of records and to portions of the record.
For VSAM keyed files, the KEY defaults to the actual key, although, as the files are processed sequentially, any field can be defined as the key for the purpose of specifying a range for record matching. You might need to write your own utility programs or obtain them from other software vendors.
The utility program should inspect the parameter data, determine its data representation and convert it, if necessary, to the representation used by the program. Note: The utility program must be compiled within your COBOL development system to ensure that all interactions with the system are handled correctly. All rights reserved. Note: You can only use this utility with XDB databases. Indicates the end of the program control statements. Includes records from the input data set based on comparison testing of one or more fields in the input record.
Supports substring comparison and bit logic bit operator and bit comparison tests. You can specify up to 16 conditional expressions. Rearranges input records before sorting or merging. Defines a merge operation. You can select portions of the input data sets for merging. You can define up to 32 control fields, but the total length of the control fields must not exceed 1, bytes. You can request ascending or descending sequences for the following control field types: AQ.
Floating point. Only 4-byte and 8-byte forms are supported. Two-digit, two-byte character or zoned decimal year data, with special indicators. Specifies the names of the E15 and E35 exit programs. Other exits are not supported. Excludes records from the input data set based on comparison testing of one or more fields in the input record.
Writes multiple output files. The OUTREC operand provides editing and control of the way numeric fields are presented with respect to length, leading or suppressed zeros, symbols, and so on. Use the CHANGE option to select a character or hexadecimal string for output from a lookup table, based on a character, hexadecimal or bit string as input. Rearranges output records after sorting or merging. It can also insert literal variables into the output record. Supports reformatting of records as well as the creation of formatted reports.
Specifies record length information. Only the first value of this statement, which specifies the maximum record length, is used; all other values are ignored. Defines a sort operation. You can request ascending or descending sequences for the same control field types as described for the MERGE statement.
Produces only one output record for records with duplicate sort fields. Optionally, numeric fields in the duplicate records can be summed in the output record.
The sum operation can be done for the following control field types: BI. Exit area scratchpad used by the exit to maintain variables between calls to the exit program. Delete the current record. For E15, the record is not sorted. For E35, the record is not written to the output data set. Do not call this exit again; exit processing is no longer required. Insert the current record. For E15, the record is inserted for sorting. For E35, the record is written to the output data set.
The job step is terminated with the condition code set to Alter the current record. For E15, the altered record is passed to the sort. For E35, the altered record is written to the output data set. Length and offset, relative to 0, of the alternate key field. The offset must be within the first 4, bytes of the record.
Length plus offset must not exceed the maximum length of the record. The default is KEYS 64 0. Name of a cataloged VSAM data set to which the alternate index is to be related.
KEYS length offset. Length and offset, relative to 0, of the primary key field for a KSDS data set. The offset must be within the first bytes of the record.
JCL - Utility Programs
Mainframe sort merge