C H A P T E R 4 - Application Utilities

C H A P T E R 4

Application Utilities

The utilities described in this chapter are located in the $UNIKIX/bin directory. These utilities are useful in managing application files and tables.

`kixcisam` - Run an External C Program

The kixcisam utility executes C programs that are not defined as resources within Sun MTP but access VSAM files.

Format:

kixcisam

Before running kixcisam, you must perform the following tasks:

Compile the C program using the C-ISAM libraries.

Configure the VCT.

Set the KIXCISAM environment variable.

Refer to the Sun Mainframe Transaction Processing Software Developer's Guide for detailed procedures.

`kixfile` - Change Dataset Status

You can use the kixfile utility to dynamically change the status of a given dataset, including the associated alternate datasets. Depending on the options you specify, you can disable the specified dataset or give it limited access to certain types of processes. You can execute the utility only from a shell script running as a batch job while a region is executing.

Format:

kixfile {[{-b|-d|-f|-l|-o} Y|N [-r Y|N|C]] | [-c] | [-p]} [-X VSTIME] dataset

where:

`-b`	Sets batch status: `Y`: Batch access only. Batch processes can read or write the file, but online processes cannot read or write the file through any of its dataset names. `N`: Batch access and online access. Both batch and online processes can read or write the file.
`-d`	Sets file permissions: `Y`: Read only for online and batch `N`: Reinstate the read and write permissions in effect at system startup For example, if a dataset has read and write permissions (rw), executing `kixfile -d Y` makes the dataset read only. When all the dataset alias names to the file are in this state, you can create a sequential file using `unikixbld`. If you then execute `kixfile -d N`, the status of the dataset returns to read and write.
`-f`	Sets dataset open or close status: `Y`: Close. If all the dataset alias names to the file are closed, the file is also physically closed, and you can archive or restore the file. `N`: Open. The file is physically open when any of the datasets associated with it are opened.
`-l`	Sets lock status: `Y`: Exclusively lock the file for this batch job. No other batch jobs nor any online transactions can access the file through any of its dataset names. `N`: Unlock the file.
`-o`	Sets dataset online status: `Y`: Online read only for this dataset. Online processes can only read the file through this dataset by this dataset name, but batch processes can read/write the file. `N`: Online read/write for this dataset. Online processes can read/write the file through this dataset by this dataset name.
`-r`	Sets file recovery status: `Y`: Enable recovery for the VSAM file. `N`: Disable recovery for the VSAM file. `C`: Enable use of system cache for the VSAM file, along with disabling recovery. Before recovery can take place, region-wide recovery must be set in the VCT. The `-r` option is used only in combination with one of the previous `kixfile` options, not by itself. It is also ignored if specified with `-f Y`, (dataset close). Enabling/disabling recovery has no meaning when closing a dataset.
`-c`	Examines the specified dataset for a pending lock (PEND) state, as reported by the `kixfile -p` dataset command. If the dataset is in PEND state, `kixfile` determines whether that state is residual and can safely be reset. If all activity on that dataset has quiesced and the requesting process is no longer present, the PEND flag on the dataset is reset. Otherwise, `kixfile` leaves the PEND state intact and reports the state of the activity on the dataset in an error message.
`-p`	Prints the current dataset status.
`-X VSTIME`	Displays the time spent in VSAM code. Refer to the Sun Mainframe Transaction Processing Software Developer's Guide for more information about displaying batch statistics.
dataset	Identifies the dataset to manipulate.This is the name of the primary dataset as specified in the FCT.

When multiple datasets refer to the same physical file, the following additional rules apply:

The -r option is ignored on -f N (open dataset) if the physical file used by that dataset is already open through another dataset name. It is inappropriate to allow recovery to be enabled/disabled when the physical file might already be in use through any other dataset path.

The -r option is not ignored on any of the other kixfile options. All access to the physical file is quiesced; any existing transaction and batch access is allowed to complete, but any new transaction or batch access is halted until the requested option can be acted upon. Access that is in progress completes using the existing recovery option for all dataset paths to that physical file.

The file can have more than one lock specified at a time, but the most restrictive of the specified locks is the one in effect. For example, if you specify both the -o and
-b locks on the same file, option -b overrides option -o.

You can issue the -o, -b, -d, and -l locks before the dataset is opened. When this is done, the dataset is opened based on that option. For example, if you specify kixfile -o Y dataset followed by kixfile -f N dataset, the dataset is opened for online read only.

If the file is opened for output by a batch program, you can use only the -p option online, which prints the status of the dataset.

If any process accesses a file locked by kixfile, it might receive a DISABLED (84) error status for online transactions, or (35) for batch programs, depending on the lock.

The following examples describe how the locking options work.

kixfile -f Y dataset1

Closes dataset1.

Online transactions encounter a NOTOPEN (19) status when trying to access the file using the name dataset1, and batch programs encounter a status (35).

kixfile -o Y dataset2

dataset2 is read only for online access.

Online transactions encounter a DISABLED (84) status for any read for update or write/delete/rewrite requests using dataset2.

kixfile -b Y dataset3

dataset3 is locked exclusively for the batch system.

Online transactions encounter a DISABLED (84) status for all requests using any dataset for that file.

kixfile -l Y -r N dataset4

dataset4 is locked exclusively for this batch job and recovery is disabled for dataset4.

Online transactions encounter a DISABLED (84) status for all requests using any dataset for that file. Batch programs other than programs in this batch job encounter a status (35).

Updates to this batch job are not recoverable.

kixfile -d Y dataset5

dataset5 is read only for online and batch.

Online transactions encounter a DISABLED (84) status for any read for update or write/delete/rewrite requests using dataset5.

Batch programs encounter a status (35) if they try to open the file using that dataset for I/O. With all the dataset alias names to that file in this systemwide read-only mode, you can execute unikixbld to create a sequential file while the file is still available for reads.

If you associate multiple datasets to the same file, you must understand the behavior of kixfile when changing the status of any of those datasets. When either the -b or -1 locks are requested on any dataset associated with a file, kixfile quiesces activity by all datasets associated with the file in order to set this status. When other current dataset activity is affected by this quiescing activity, kixfile displays the following message:

kixfile: dataset-name access is also being quiesced

After setting either of the locks, activity through any of the datasets for that file is affected equally. Resetting the lock removes the effect of that lock on all datasets for that file.

If you close a dataset with the -f option or set a dataset to read-only with the -o or -d option, kixfile also quiesces activity on all datasets associated with that file until the requested dataset is closed or set to read-only. kixfile displays the same message when other current dataset activity is affected. However, the closed/read-only status of that dataset affects only requests using that dataset.

To physically close a file that has multiple datasets (for example, to do backups), you must close all datasets using kixfile. Run kixfile -p using any dataset name to check that the status reports PHY_CLSD.

It is also necessary to run kixfile -o/-d on all datasets associated with the same physical file to ensure that read-only access to the file is permitted. To verify this, run kixfile -p on all datasets associated with the file to check for read-only status.

A message is displayed when kixfile is executed with the -p option.

Format:

where:

`PHY_NOTOK`	Indicates that an error occurred on opening the file for this dataset. For example, file permissions disallow access, or the file does not exist.
`PHY_OK`	Indicates that the system knows about the file for this dataset and its attributes. The next option indicates whether it is currently accessible.
`PHY_OPND`	Indicates that the file for this dataset is open and is accessible.
`PHY_CLSD`	Indicates that the file for this dataset is closed.
`RDONLY`	Indicates that the file for this dataset is open for read only, due to file permissions.
`PEND`	Indicates that the file has an exclusive lock pending. For example, some other process has requested the file for exclusive use or is changing the status of one of its datasets. When this lock is in effect, only the transactions or batch programs already accessed by any of the datasets are allowed.
`RECOVON`	Indicates that the file for this dataset has recovery on.
`RECOVOFF`	Indicates that the file for this dataset has recovery off.
`BTCH_OUTPUT`	Indicates that the file for this dataset is opened for output by a batch program or by `unikixbld`.
`JOB`	Indicates that the file for this dataset is locked for exclusive use by a process, such as `unikixbld` or a batch job stream. At the end of the batch job or shell script, the lock is automatically released.
`UBLD`	Indicates that `unikixbld` has locked the file for this dataset. See unikixbld - VSAM File Builder.
`BTCH_ONLY`	Indicates that the only batch programs can access the file for this dataset.
`OPEN_ONL`	Indicates that the dataset is open and is accessible by online transactions.
`CLSD_ONL`	Indicates that the dataset is closed to online transactions.
`ENBLD_ONL`	Indicates that the dataset is enabled for online transactions.
`DSBLD_ONL`	Indicates that the dataset is disabled for online transactions.
`ONL_RDONLY`	Indicates that the online transactions can only read, not write, the dataset.
`OPEN_BCH`	Indicates that the dataset is open and is accessible by batch jobs.
`CLSD_BCH`	Indicates that the dataset is closed and is not accessible by batch jobs.
`ENBLD_BCH`	Indicates that the dataset is enabled for batch jobs.
`CLSD_BCH`	Indicates that the dataset is disabled for batch jobs.
`BCH_RDONLY`	Indicates that the batch jobs can only read, not write, this dataset.

If the option is not set, an empty field is displayed instead of the keyword. For example, if a dataset is opened for batch only, with recovery on, the following message is displayed:

Dataset dataset PHY_OK,PHY_OPND,,,RECOV_ON,,,,BTCH_ONLY,, CLSD_ONL,ENBLD_ONL,,OPEN_BCH,ENBLD_BCH,

Precautions

If you have defined your VSAM files as recoverable and fail to adhere to the following restrictions when using kixfile batch shell scripts, your data might be corrupted and the files might be unrecoverable.

Multiple background processes accessing VSAM files within the same job is not allowed. For example, do not code an ampersand (&) on the command line to invoke the step in the background.

Do not perform a kill -9 or SIGKILL on the kixfile process ID.

`kixjas` - Extract Data From a Journal File

The kixjas shell script extracts the accounting data portion of the accounting records in the journal file. The conversion program, kixjas, reads a region's journal file and creates an ASCII file containing the same information but excluding accounting journal header information. The program can extract specific types of accounting records, either transaction ID records (record type 0001) or user records (record type 0002).

Note - This affects only accounting records generated by means of the SIT, SNT, and PCT options, not accounting records generated by application programs.

Format:

kixjas -o outputfile [-c [nn]] [-t {tranid|userid}] -iinputfile1, inputfile2, ...

where:

`-o` outputfile	Identifies the file to use when writing out the ASCII records.
`-c [`nn`]`	Continues processing the file(s) until the nnth occurrence of a crash record (type 0006) is encountered. If you do not specify nn, 1 is assumed.
`-t` tranid `\|` userid	specifies the type of record to extract from the input files; either transaction id or user id records. If not specified, both types are processed.
`-i` inputfile1, inputfile2, ...	identifies the journal file(s) to process.

The following command writes ASCII record formats to the out1 file, processes four accounting journal files, and places the report in the file named report.

$ kixjas -o out1 -i JRNL02.jnl JRNL05.jnl JRNL11.jnl JRNL22.jnl 1>report

Precautions

You must type the command arguments in the order specified; otherwise the command will fail.

`kixjournal` - Process a Journal File

The kixjournal shell script processes the current journal file. kixjournal is called when a journal file has reached its maximum size.

By default, kixjournal writes messages to the unikixmain.log file indicating that the journal file was processed. If further processing, such as copying the file to a tape, is required, you must modify the shell script.

Format:

kixjournal

`kixlog` - Write a String to the Log File

The kixlog utility provides an interface between Sun MTP's shell scripts and log files, unikixmain.log, unikixmain.err and unikixmain.dbg. The utility enables you to place a string in the log file of your choice. For example, the kixjournal shell script uses kixlog to write messages to unikixmain.log.

You can only execute this program in a shell script executed by Sun MTP. Sun MTP-invoked batch programs that execute in a shell script can also use the kixlog utility.

Format:

kixlog [-d|-e|-l] string

where:

`-d`	Writes string to the `unikixmain.dbg` file.
`-e`	Writes string to the `unikixmain.err` file.
`-l`	Writes string to the `unikixmain.log` file.
string	Specifies the message to place in the log file. Quotes are required if any spaces are included in the message. By default, string is written to the `unikixmain.log` file.

For example, the following command places a message in the unikixmain.log file.

$ kixlog -l "Accounting file JRNL05.jnl being processed"

The entry in the unikixmain.log file is as follows:

date time kixlog:   Accounting file JRNL05.jnl being processed

where date and time are replaced with the date and time that kixlog was executed.

`kixtran` - Execute a Transaction

The kixtran command starts a transaction from a batch script or from the shell prompt. You can use this utility in a script that is submitted at the prompt or with the UNIX at and cron commands.

Format:

kixtran -t "tranid [data]"

where:

-t "tranid [ data ]"

Identifies the requested transaction. If the transaction contains more than one word, enclose it in quotation marks. For example:

kixtran -t "CSMT SHUT,YES"

Precautions

You cannot use this command for conversational transactions or for transactions that require map input. The transaction can display output, but you cannot respond to what is displayed.

`unikixbld` - VSAM File Builder

The unikixbld utility is used to manipulate VSAM files from a batch job. unikixbld performs these functions:

Builds VSAM files from sequential files.

Builds sequential files from VSAM files.

Builds VSAM files by accepting records from a user program.

Builds user files by providing records to a user program.

Initializes VSAM files.

Rebuilds index files from VSAM data files.

Rebuilds alternate index files from base VSAM files.

Merges multiple sequential files into a single VSAM data file.

Provides update-in-place functionality for the updating of VSAM files from sequential files.

Refer to the Sun Mainframe Transaction Processing Software Developer's Guide for examples of the use of unikixbld.

Formats:

To initialize a dataset:

unikixbld -d dataset -i

To export a non-VSAM file:

unikixbld -d dataset -2 -l bytes -r format -s filename ... -t s -v n-rec

To build a VSAM file from non-VSAM files:

unikixbld -d dataset -2 -f percent -m -r format -s filename ... -t v

To rebuild an alternate index:

unikixbld -d dataset -f percent -t a [-M altkey-mem]

To rebuild the index portion of a VSAM file:

unikixbld -d dataset -t x

To update VSAM files:

unikixbld -d dataset -p [reuse|noreuse] [-k{replace|noreplace}] -W nnn -V

To display all statistics. This example also shows rebuilding the index portion of a VSAM file.

unikixbld -d dataset -t x -X ALL

where:

`-2`	Indicates that the header record is 2 bytes instead of the default 4 bytes, if the record format is variable (`-r recordv`). This applies for both exporting and importing of files. The record header contains the length of the record.
`-a`	Appends records to a target ESDS file. This option is maintained for backward compatibility in this release. Use the `-p reuse` option for the same functionality.
`-d` dataset	Identifies the dataset to process. dataset refers to a dataset defined in the FCT. This parameter is required. If dataset is blank and the `-t s` option is set, the specified sequential file is created and is empty.
`-f` percent	Specifies the fill percentage, which is the amount of free space to leave in each VSAM block. percent is any number from 0 to 99. If you do not use this parameter, the fill percentage defaults to 0. This parameter is valid for VSAM KSDS files only.
`-i`	Initializes a VSAM file. `unikixbld` does not expect the file to be closed before initializing. If the file is accessed by online and/or batch, `unikixbld` quiesces the file, locks it, initializes it, and releases it for further processing. If `reuse` is specified in the VSAM catalog, or `noreuse` is specified and the file contains no records, then the file is initialized. The `-i` and `-t` parameters are mutually exclusive.
`-k [replace\|noreplace]`	Specifies whether the source file record will replace the target VSAM file record. `replace` indicates that the source file record will replace the target VSAM file record, if the same key valued record (for KSDS) exists in both the target VSAM file and the source file. When no record exists in the target VSAM file that corresponds to the source file record, the source record is inserted into the target VSAM file. `noreplace` indicates that the source file record will be ignored and the target VSAM record will remain unchanged, if the same key valued record (for KSDS) exists in both the target VSAM file and the source file. When the record keys match, a "duplicate record" condition message is issued if the verbose mode is set, and the target record is not modified. When no record exists in the target VSAM file that corresponds to the source file record, the source record is added to the target VSAM file. This is the default behavior. The `-k` arguments have meaning only when the `-p noreuse` argument is specified. If you use a `-k` argument with the `-p reuse` argument, the `-k` argument is ignored and a warning message is displayed. Relative record datasets (RRDS) are not currently supported.
`-l` bytes	Builds sequential files from a VSAM dataset. bytes specifies the maximum number of bytes to place in a sequential file. When this number of bytes is reached, the next sequential file is used. This number can be exceeded in the last file, if an insufficient number of sequential files are specified. This value can have a suffix of K, M, or G, which specifies kilobytes, megabytes, or gigabytes, respectively. Use this parameter when building a sequential file that is larger than available disk devices (spanned file).
`-m`	Merges multiple sequential files. Use this option when building a VSAM file from multiple sequential files when the keys are not in ascending order from file to file. This option is not applicable to customized record processing formats such as the `mfrcd` format. Refer to the Sun Mainframe Transaction Processing Software Administrator's Guide.
`-M` altkey-mem	Specifies the amount of space (in MB) allocated by the internal sort utility when alternate keys are sorted. This argument is ignored if there are no alternate keys for the VSAM output file.
`-p [reuse\|noreuse]`	Specifies whether the target VSAM file should be reinitialized. `reuse` indicates that the target VSAM file will be reinitialized and completely rebuilt from the records in the source file. The space is logically reused in its entirety. `reuse` is the default for standard batch. You can configure a Sun MBM subsystem to apply the mainframe default of `NOREUSE`. `noreuse` indicates that the target VSAM (KSDS) file is not reinitialized and update rules are derived from the `-k replace\|noreplace` argument. If the target VSAM file is an ESDS file, all of the sequential input from the source file is appended to the end of the VSAM file. RRDS files are not currently supported for any combination of `-p` and `-k` arguments.
`-r` format	Specifies the record format to use when creating or accessing a sequential file. format is either one of the Sun MTP-supported record formats or a custom record format created using the procedure specified in the Sun Mainframe Transaction Processing Software Administrator's Guide. If you do not use this parameter, the format defaults to record. The supported record formats are: `line`. Line format (linefeed character as delimiter). `record`. Fixed-length record format. `recordv`. Variable-length record format. `mfrcdv`. Micro Focus variable-length record format. The minimum record size is the key size and the maximum record size is the record size as defined in the VSAM catalog. Sun MTP-supplied customized record format: `mfrcd`. Micro Focus fixed-length record format. See Large Files. Refer to the Sun Mainframe Transaction Processing Software Administrator's Guide for information about customizing record processing routines.
`-s` filename	Identifies a file name that specifies a full or relative path name to use for the sequential file. A relative path name is relative to the directory specified by the `KIXSYS` environment variable. When exporting to a non-VSAM file, filename is the file to which the VSAM records are written in the format specified in the `-r` option. When building a VSAM file, filename is the file from which the records are read in the format specified in the `-r` option. When building a VSAM file, also note that: Records in the sequential file(s) must be sorted. If you are specifying multiple sequential files, you must list them in ascending order on the command line with respect to their contents, and the files must contain keys with increasing values. If you are using the `-m` option, this is not necessary. You can specify up to 50 sequential file names. If the input dataset is blank and the `-t v` option is set, filename is initialized just as if the `-i` parameter were set.
`-t [a\|s\|v\|x]`	Specifies the output file type: `a`: Rebuilds an alternate index file. `s`: Creates a sequential file from a VSAM file (see the `-d` option). `v`: Creates a VSAM file from a sequential file (see the `-s` option). `x`: Rebuilds an index file. The `-t` and `-i` parameters are mutually exclusive.
`-v` n-rec	Displays an informational message after n-rec records are processed. This enables you to view the progress of `unikixbld`. The `-v` and `-i` parameters are mutually exclusive.
`-V`	Indicates the verbose option. If specified, "duplicate record" keys are written to the log file. See the `-k noreplace` description. If not specified, no "duplicate record" keys are logged. The log information is a two-line entry that shows the key in both hexadecimal and alphanumeric formats, along with the record number of the input record that contains the duplicate key. For example: `Duplicate Key: Input Record 456` `30313730313841 *017018A`
`-W` nnn	Specifies the number of input records that are passed for each syncpoint whether or not recovery is specified on the target VSAM file. The default (`-W` is not specified) means that no syncpoint is done until the end of the job. nnn must be greater than zero. This argument applies only if `-p noreuse` is specified. If you are working with recoverable files, specify the `-W` nnn argument to ensure that a syncpoint is done after each nnn input records are processed.
`-X [ALL\|PIO\|WTIME]`	Displays statistical information. Valid arguments are: `ALL`: Displays both sets of statistics. `PIO`: Displays physical I/O statistics. `WTIME`: Displays wait times.

Modes of Operation

For sequential-to-VSAM file processing, unikixbld operates in two modes: load and update.

In load mode, unikixbld performs the following actions:

1. Locks the file for exclusive control.

2. Creates a temporary data and index file for the VSAM file.

3. Loads the records into the temporary data file.

4. Builds the temporary index file from the temporary data file.

5. Builds any existing alternate files for each alternate file, as in steps 3 and 4.

6. Copies the temporary files to VSAM files.

7. Unlocks the file.

If unikixbld fails to complete, the temporary file is discarded and the VSAM file is the same as at the beginning of the load process.

In update mode, unikixbld acts like a transaction. When unikixbld is replacing or adding a record from the source sequential file, the VSAM file can be accessed by online and batch utilities. If recovery is enabled for the VSAM file, the record is not available for updating until unikixbld commits the record. This suggests that unikixbld can be a candidate for deadlock situations. If unikixbld fails to complete, the records added or updated since the last syncpoint are restored. If exclusive control of the file is required in update mode, kixfile must be used to lock the file.

Arguments that apply to unikixbld executing in the update mode are: -k, -p, -W, and -V.

Usage Considerations

This section describes issues to be aware of when using unikixbld.

Update in Place

Observe the following restrictions when using unikixbld batch shell scripts:

Multiple background processes accessing VSAM files within the same job are not allowed. For example, do not code an ampersand (&) on the command line to invoke the step in the background.

Do not perform a kill -9 or SIGKILL on the unikixbld process ID. If you must manually terminate the process, you can use the kill pid# command.

If your VSAM files are defined as recoverable and you fail to adhere to these restrictions, your data might be corrupted and the files might be unrecoverable if you perform an asynchronous manual termination.

The -k and -p arguments are for unikixbld sequential file-to-VSAM file processing. VSAM-to-VSAM processing is not supported.

The -k and -p arguments are valid only for KSDS and ESDS VSAM file types. If you use them with RRDS files, unikixbld terminates the process and issues an error message.

Large Files

If you are using the mfrcd record format for input or output with unikixbld, and your files exceed 2 GBytes in size, read this section and perform the necessary configuration tasks.

You must use Server Express COBOL if you are using large files.

Refer to the "File Handler Configuration" section in the Server Express Programmer's Guide for File Handling and familiarize yourself with the information about the handler configuration file. The configuration file must contain, at a minimum, the following statements:

[XFH-DEFAULT]

FILEMAXSIZE=8

Depending on your application, this file can contain other statements as well.

In the region setup file, define the EXTFH environment variable, which specifies the location of the handler configuration file.

`unikixvsam` - COBOL Runtime System

Note - This applies to a standard batch environment only.

To execute a COBOL program inside a shell script, you must execute the program using the unikixvsam COBOL runtime system. You can pass parameters to the COBOL program by including them on the unikixvsam command line. The debugging options of unikixvsam are described in the Sun Mainframe Transaction Processing Software Developer's Guide.

Format:

unikixvsam [-d|-D] progname ["parameters"]
[-X {ALL|VSTIME|WTIME|LIO|PIO|}]

where:

`-d`	Creates a log file of all VSAM requests. The log file is named `unikixmain.dbg` and is located in the `$KIXSYS` directory.
`-D`	Runs the COBOL program under Micro Focus Animator. For this option to work, you must select Animator with the `CEDF` transaction and run the batch process using the `CBCH` transaction. For more information about these transactions, refer to the Sun Mainframe Transaction Processing Software Administrator's Guide.
progname	Identifies the COBOL program to execute. If an extension is given, it should be `.gnt` or `.int`. If no extension is given, `unikixvsam` searches for a `.gnt` version of the program. If no `.gnt` version is found, `unikixvsam` searches for an `.int` version. The program name can include either a full path or a relative path. If a relative or partial path name is given, the path fragment is combined with each directory specified by `$KIXPROGS` to form full path names. The directories are then searched for a matching program name.
"parameters"	Indicates parameters to pass to the COBOL program. For information about passing parameters, refer to the Sun Mainframe Transaction Processing Software Developer's Guide.
`-X` arguments	Displays batch statistics. Use the `ALL` argument to display all statistics or use any combination of the other arguments. `ALL`: Displays all statistics. `VSTIME`: Displays time spent in VSAM code. `WTIME`: Displays wait times. `LIO`: Displays logical I/O statistics. `PIO`: Displays physical I/O statistics. Refer to the Sun Mainframe Transaction Processing Software Developer's Guide for more information about batch statistics.

Usage Considerations

If you have defined your VSAM files as recoverable and fail to adhere to these restrictions when using unikixvsam batch shell scripts, your data might be corrupted and the files might be unrecoverable.

Multiple background processes accessing VSAM files within the same job is not allowed. For example, do not code an ampersand (&) on the command line to invoke the step in the background.

Do not perform a kill -9 or SIGKILL on the unikixvsam process ID.

You must copy programs or shell scripts into a $KIXBTCH directory. Do not move files into $KIXBTCH because after the programs start, they are deleted. When the region looks for programs to execute, it attempts to execute each file in the directory that is executable or that has a .gnt or .int extension. Therefore, use $KIXBTCH directories exclusively for Sun MTP batch programs and shell scripts that are awaiting execution.

kixcisam - Run an External C Program

kixfile - Change Dataset Status

Precautions

kixjas - Extract Data From a Journal File

Precautions

See Also

kixjournal - Process a Journal File

kixlog - Write a String to the Log File

kixtran - Execute a Transaction

Precautions

unikixbld - VSAM File Builder

Modes of Operation

Usage Considerations

Update in Place

Large Files

unikixvsam - COBOL Runtime System

Usage Considerations

`kixcisam` - Run an External C Program

`kixfile` - Change Dataset Status

`kixjas` - Extract Data From a Journal File

`kixjournal` - Process a Journal File

`kixlog` - Write a String to the Log File

`kixtran` - Execute a Transaction

`unikixbld` - VSAM File Builder

`unikixvsam` - COBOL Runtime System