C H A P T E R  2

System Utilities

The utility programs described in this chapter reside in the $UNIKIX/bin directory. These utilities are useful for managing a region.


dfhusdup - Define and Report Resources

dfhusdup is the batch utility used to define and report the resources in the system definition file, including initialization of the DFHUSD file.

You must submit this utility to Sun MTP standard batch with the required options and commands. You can include comments in the batch file by typing an asterisk (*) in the first column of the line. If the command, attribute, or attribute type continues to the next line, you must type an asterisk in column 72.

The following example shows the use of the asterisk to denote a comment and the continuation of a command in a batch file.

*Define a program
DEFINE PROGRAM(SAL001) GROUP(SALES1) DESCRIPTION(Daily sales*
program)



Note - For most attribute values, the text you type is converted to uppercase. The exceptions to this are the values for GROUP, DESCRIPTION, JVMCLASS, and SHLIB, which support mixed case.



Format:

dfhusdup CMDFILE=commands-filename|stdin [PRINTFILE=filename] [PAGESIZE=nnn] [USD=READWRITE|READONLY]

where:

CMDFILE

Specifies either a file name, commands-filename, containing the resource definition commands, or stdin. If stdin is specified, the commands are expected in line in the following format:

dfhusdup CMDFILE=stdin <<!
<dfhusdup commands>
<dfhusdup commands>
!

PRINTFILE

If filename is specified, the report is saved in the specified file. By default, the report is printed to standard out (stdout).

PAGESIZE

Indicates the number of lines in a page; default is 60.

USD

Controls the operations on the system definition file. The default is READWRITE.

READWRITE: Update commands can be issued
READONLY: Only query commands can be issued


The following dfhusdup commands are supported:

COPY
DEFINE
DELETE
INITIALIZE
LIST

See Also

The Sun Mainframe Transaction Processing Software Configuration Guide for information about using alternate resource definition.

The Sun Mainframe Transaction Processing Software Developer's Guide for examples of dfhusdup usage, as well as for information about batch processing.

Your UNIX documentation for information about writing shell scripts.

INITIALIZE Command

The INITIALIZE command initializes the system definition file, DFHUSD. You must initialize the DFHUSD file before you can use any of the other dfhusdup commands or CEDA transactions. You only initialize the DFHUSD once.

Format:

INITIALIZE

DEFINE Command

The DEFINE command defines the resource. Mapsets, programs, and transactions are the supported resource types.

Format:

DEFINE [MAPSET(mapset-name)[attribute(value)...] |
PROGRAM(
program-name)[attribute(value)...] |
TRANSACTION(
transaction-name)[attribute(value)...]]
GROUP(
group-name)

where:

MAPSET(mapset-name)

Identifies the mapset; up to 8 characters without embedded spaces. Do not use any system-supplied program or mapset names beginning with C. Lowercase characters are converted to uppercase.

PROGRAM(program-name)

Identifies the program; up to 8 characters without embedded spaces. Do not use any system-supplied program or mapset names beginning with C. Lowercase characters are converted to uppercase.

TRANSACTION(transaction-name)

Identifies the transaction; up to 4 characters without embedded spaces. Do not use any system-supplied program or mapset names beginning with C. Lowercase characters are converted to uppercase.

GROUP(group-name)

Identifies the group to which to add this resource; up to 8 characters without embedded spaces. If the group does not exist, it is created.

attribute(value) . . .

The attributes of the resource.


MAPSET Attributes

The following MAPSET attributes are supported:

[DESCRIPTION(description)]
[STATUS(ENABLED|DISABLED)]

where:

DESCRIPTION(description)

Describes the mapset; up to 58 characters.

STATUS(ENALBED|DISABLED)

Specifies the mapset's status. ENABLED is the default.


PROGRAM Attributes

The following PROGRAM attributes are supported:

[DESCRIPTION(description)]
[LANGUAGE([ASSEMBLER|C|COBOL|PLI])]
[STATUS(ENABLED|DISABLED)]

where:

DESCRIPTION (description)

Describes the program; up to 58 characters.

LANGUAGE([ASSEMBLER|C|COBOL|PLI])

Identifies the programming language. If not specified, the default is COBOL.

ASSEMBLER: Table referenced by application programs using CICS LOAD and CICS RELEASE commands

C: C language

COBOL: COBOL language

PLI: PL/I language

STATUS(ENALBED|DISABLED)

Specifies the mapset's status. ENABLED is the default.


Remote program attributes:

[EXECUTIONSET(FULLAPI|DPLSUBSET)]
[REMOTENAME(
program-name)]
[REMOTESYSTEM(
system-name)]
[TRANSID(
transid)]

where:

EXECUTIONSET(FULLAPI|DPLSUBSET)

Specifies that the DPL program runs in the local system as if it were a remote system, if the REMOTESYSTEM name is the same as the local system name. Refer to the Sun Mainframe Transaction Processing Software Administrator's Guide for additional information.

FULLAPI: The program can use all the CICS API commands. Default.

DPLSUBSET: The program cannot use any DPL-restricted API.

REMOTENAME(program-name)

Identifies the program in the remote Sun MTP or CICS system. If REMOTENAME is not specified and REMOTESYSTEM is specified, Sun MTP assumes the name in PROGRAM (program-name). Refer to the Sun Mainframe Transaction Processing Software Administrator's Guide for additional information.

REMOTESYSTEM (system-name)

Identifies the remote Sun MTP or CICS system to which, if specified, the Sun MTP region ships a DPL request. The system-name must exist in the TCT - System Entries table.

TRANSID(transid)

Identifies the transaction under which the remote system attaches to the requested program. Refer to the Sun Mainframe Transaction Processing Software Administrator's Guide for additional information.


Javatrademark virtual machine (JVMtrademark) attribute:

[JVMCLASS(class-name)]

where:

JVMCLASS(class-name)

Identifies the main class of the Java program. The class name can be mixed case.


Sun MTP-specific extensions:

[PRELOAD(NO|YES)
[SHLIB(
shared-library-name)]

where:

PRELOAD(NO|YES)

Indicates whether the transaction server should open the shared library at startup.

SHLIB(shared-library-name)

Identifies the shared library, up to 16 characters, that contains the specified program. All entries are assumed to be relative to $KIXSYS unless the KIXLIB environment variable is set to a path name.

This is a Sun MTP extension to the API.


TRANSACTION Attributes

The following TRANSACTION attributes are supported:

[DESCRIPTION(description)]
[PROGRAM(
program-name)]
[TWASIZE(0-32767)]
[STATUS(ENABLED|DISABLED)]

where:

DESCRIPTION(description)

Describes the transaction; up to 58 characters; optional. Text can be mixed case.

PROGRAM(program-name)

Identifies the program name. Program names must be uppercase.

TWASIZE(0-32767)

Specifies the transaction work area (TWA) size in bytes.

STATUS(ENABLED|DISABLED)

Specifies the transaction's status. ENABLED is the default.


Remote attributes:

[LOCALQ(NO|YES)]
[REMOTESYSTEM(
system-name)]
[REMOTENAME(
program-name)]

where:

LOCALQ(NO|YES)

Indicates whether transactions shipped to a remote system are locally queued if the remote system is unavailable. Default is NO.

REMOTENAME(program-name)

Identifies the program in the remote Sun MTP or CICS system. If REMOTENAME is not specified and REMOTESYSTEM is specified, then Sun MTP assumes PROGRAM name. Refer to the chapter on Intersystem Communications in the Sun Mainframe Transaction Processing Software Administrator's Guide for additional information. program-name is limited to 8 characters.

REMOTESYSTEM(system-name)

Identifies the remote Sun MTP or CICS system to which, if specified, the region ships a distributed program link (DPL) request. The 4-character system-name must be in TCT-System Entries table.


Scheduling attribute:

[TRANCLASS(transaction-class)]

where:

TRANCLASS(transaction-class)

Identifies the transaction class to which the transaction is assigned.


Recovery attribute:

[DUMP(YES|NO)]

where:

DUMP(YES|NO)

Indicates whether a transaction dump is produced if the transaction terminates abnormally. The default is YES.


The following attributes are specific to Sun MTP and are not part of the IBM CICS set:

[SCREENSIZE(DEF|ALT)]
[ACCOUNTING(DEF|NO|YES)]
[FILEID(0-99)]
[APPC(YES|NO)]
[TASKREQKEY(
value)]
[TRANSEC(1-64)]

where:

SCREENSIZE(DEF|ALT)

Specifies the default screen size or the alternate screen size.

DEF: Default screen size of 24 lines and 80 columns for Model 2 3270 terminal types.

ALT: Alternate screen sizes of 27 lines and 132 columns for Model 5 3270 terminal types, or 43 lines and 80 columns for Model 4 3270 terminal types.

ACCOUNTING(DEF|NO|YES)

Indicates whether accounting is on or off for this transaction.

YES: Accounting is on for this transaction, if the Accounting field in the SIT is set to Y

NO: Accounting is off for this transaction

DEF: (Default) Accounting is controlled by the SIT Accounting field and the MCT

FILEID(0-99)

Specifies the journal file identifier for this transaction; a number from 1 to 99. If accounting is set to N, this field is ignored.

If File ID is not specified in the JCT, the journal file name is created by concatenating JRNL with the File ID value, creating, for example, a journal file named JRNL05.

APPC(YES|NO)

Indicates if the transaction is a back-end DTP transaction.

YES: Transaction is a back-end DTP program and performs ISC functions.

NO: Transaction is not a back-end DTP program. It can still perform outbound ISC functions, but does not run as expected if started by a remote Sun MTP or CICS region.

TASKREQKEY(value)

Specifies a key that initiates this program as a transaction. If this field is blank, no key initiates this program as a transaction. Valid values are:

PF1 through PF24

PA1 through PA3

TRANSEC(1-64)

Specifies a value from 1 to 64 indicating a transaction security level. This value corresponds to a bit value set in the Security Key area of the SNT associated with the user at the terminal that entered the transaction.

If external security management is enabled (KIXSEC=YES), the value in Trans Sec is ignored.

The Security Key is set for a user by the SNT when the user signs on explicitly with CSSN (CESN), or implicitly when Sun MTP starts and a match is found between the user ID and a user ID in the SNT. By default, each user is allowed to only submit transactions with a security level of 1. All system transactions are set initially to a transaction security level of 1, which allows all users to access them.

Raise the security level for critical transactions, such as CSMT, CEMT, and other transactions that are used to configure the Sun MTP environment. Refer to the "Security" chapter in the Sun Mainframe Transaction Processing Software Administrator's Guide for information about Sun MTP security.


DELETE Command

You can use the DELETE command to delete a resource. You can delete groups or resources.

Format:

DELETE [MAPSET(mapset-name) | PROGRAM(program-name) |
TRANSACTION(
transaction-name)] GROUP(group-name)

where:

GROUP(group-name)

Identifies the group from which to delete the resource(s). If RESOURCE TYPE is not specified, the entire group is deleted, including the GROUP definition.

MAPSET(mapset-name) |
PROGRAM(
program-name) |
TRANSACTION(
transaction-name)

Identifies the resource (mapset, program, or transaction) to delete. You can specify a generic resource name. If the resource specified is the last or group of last resources, the GROUP definition is also deleted.


LIST Command

You can use the LIST command to report groups, resources within groups, and the attributes of each resource.

Format:

LIST GROUP(group-name)| ALL [OBJECTS]

where:

ALL

Reports all the groups in the resource file.

GROUP (group-name)

Identifies the group to be reported. You can specify a generic name.

OBJECTS

Indicates the level of reporting. If specified, it reports the attributes of each resource. If omitted, only groups with the resource names are reported.


COPY Command

The COPY command copies all the resources definitions in one group to another.

Format:

COPY GROUP(group-name1) TO(group-name2) [MERGE|REPLACE]

where:

GROUP (group-name1)

Identifies the group from which to copy the resource. You can specify a generic name.

TO (group-name2)

Identifies the group to which to copy the resource. You can specify a generic name. If the GROUP parameter does not specify a generic name, the TO parameter cannot have a generic name. If a generic name is used in both GROUP and TO parameters, the number of characters in the TO group must be fewer than the number of characters in the GROUP parameter. If the group definition does not exist, it is created.

MERGE

Retains the resource definition of the TO group if the resource exists in the TO group.

REPLACE

Replaces the definition from the group specified with the parameter GROUP, if the resource exists in the TO group.



kixclean - Deallocate IPC Areas

The kixclean utility deallocates IPC (interprocess communication) areas that were allocated by the region and were not automatically freed when the region shut down.

After a region aborts, check the status of the IPC areas using the UNIX ipcs command. If IPC areas are present, execute the kixsnap utility before removing the IPC areas.

kixclean requires that the KIXSYS environment variable be set to the directory containing the system tables for the region to be cleaned.

kixclean with no options performs the following operations:

Format:

kixclean [-a]

where:

-a

Clears all IPC areas. Any messages that are awaiting the print server are lost. If the print processor is still operating, the print queue is removed when it has finished.

Use this option only when a normal shutdown has failed.


Precautions

Restrict access to this utility.

Never use kixclean when a region is executing normally, and do not use it to shut down a region. Severe damage can occur to VSAM files if you use kixclean to shut down a region.

See Also

kixsnap - Take System Snapshot.

kixverify - Display/Reset Activity Counts. After running kixclean, you must run kixverify -rALL before restarting the region.


kixcnvtbl80 - Convert Tables

The kixcnvtbl80 utility converts Sun MTP tables created with Release 4.0, 4.1, 5.0, 5.1, 6.0, and 7.x to the Release 8.0 format. The file names of the tables must have an extension of .tbl.

kixcnvtbl80 makes a copy of the files to be converted by appending .old to them. If any files with an extension of .tbl.old exist when the utility is executed, they are overwritten. The kixcnvtbl80 utility overwrites the existing .tbl files with the new table formats.

Format

kixcnvtbl80 -d directory

where:

-d directory

Indicates the location of the tables to convert. You can specify directory as an absolute path name, a relative path name, or an environment variable such as $KIXSYS.

If you specify a directory that contains the Group Control Table (GCT), kixcnvtbl80 converts all the tables in each of the group directories defined in the GCT.


kixcnvtbl80 creates the $KIXSYS/unikix.dir and $KIXSYS/rdo.dir if they do not already exist.

Precautions

Restrict access to this utility.

Do not use kixcnvtbl80 more than once in the same directory, or the .tbl and the .tbl.old files will be corrupted. If this occurs, restore the original tables from backups, if available, and execute the utility on the restored files.


kixcnvtcat80 - Convert VSAM Catalog

The kixcnvtcat80 utility converts a Sun MTP VSAM catalog created with
Release 5.1 and 6.0 to the Release 8.0 format. If your catalog is in Release 7.x format, you do not need to run this utility.

This utility ensures that the converted VSAM catalog contains valid default values for each dataset defined in the catalog. kixcnvtcat80 uses the specified VSAM catalog (or CATALOG, if no catalog name is specified) in the $KIXSYS directory. First, it invokes the kixexpcat utility to generate an ASCII text file with the new catalog record fields. Then it invokes kiximpcat to rebuild the VSAM catalog using this ASCII text file. See kixexpcat - Export the VSAM Catalog and kiximpcat - Import an ASCII Catalog File for more information.

The kixcnvtcat80 utility makes copies of the existing VSAM catalog .dta and .idx files in the $KIXSYS directory by appending .old to them. If those files already exist in the $KIXSYS directory, they are overwritten when kixcnvtcat80 is executed. The existing .dta and .idx files are replaced with .dta and .idx files that have the new catalog format. kixcnvtcat80 also saves the ASCII text file it created in the $KIXSYS directory, under the name CATALOG.lst or catalog.lst, if a catalog name was specified when the utility was invoked. You can copy this file to another directory or backup medium and use it to rebuild the VSAM catalog with kiximpcat, if necessary.

After you convert the VSAM catalog, the kixcnvtcat80 utility has no effect on the converted catalog. If you need to change the values of fields in the converted catalog, use File Manager.

If, for any reason, you need the earlier release version of the VSAM catalog, you will have to restore the original .dta and .idx files from a backup, or you must rebuild the catalog. Before rebuilding, you must delete the Release 8.0 version of the catalog. After reinstalling the earlier release, you can rebuild the catalog by invoking the kiximpcat utility on the ASCII text file of the earlier-release catalog.

Format:

kixcnvtcat80 -r {Y | N} [-c catalog-file]

where:

-r {Y | N}

Sets batch read-locking field in the VSAM catalog to Y or N.

-c catalog-file

Identifies the VSAM catalog. If this option is not specified, the VSAM catalog is assumed to be CATALOG.




Note - In addition to the batch read-locking field, the VSAM catalog contains a reuse field that denotes the file as reusable. This flag is automatically set to Y by the kixcnvtcat80 utility. (In releases prior to 7.0, reuse-allowed was the default behavior.) Use File Manager to change the value of the reuse field on a file-by-file basis.



If you execute the kixcnvtcat80 utility without specifying any options, these prompts appear:

No batch read-locking option was specified for converting $KIXSYS/CATALOG;
Do you want to continue with the batch read-locking option set to 'Y'?

If you respond Y to the prompt, kixcnvtcat80 assumes the value Y for the -r option and CATALOG for the -c option. If you respond N, kixcnvtcat80 terminates and displays the following messages:

Syntax: kixcnvtcat -r {Y|N} [-c catalog]
	-r set read-locking flag
	-c catalog name; CATALOG assumed if not specified
Please retry with the required option

These messages are also displayed if you make any syntax errors when specifying the command options, and the utility terminates.

If you do not set the KIXSYS environment variable before running the utility, kixcnvtcat80 terminates with an error message.

Precautions

Restrict access to this utility.

If you use kixcnvtcat80 more than once in the same directory, it overwrites the .dta.old and .idx.old versions of the VSAM catalog.

If you want to convert the VSAM catalog again, you must copy back the .dta.old and .idx.old files to .dta and .idx, respectively, and run the kixcnvtcat80 utility.

See Also

The Sun Mainframe Transaction Processing Software Administrator's Guide for information about File Manager.

The Sun Mainframe Transaction Processing Software Developer's Guide for more information about batch read-locking and VSAM RC (read consistency).


kixcontrol - Generate Dump File

You can use the kixcontrol utility to enable or disable the generation of an application dump file. See kixetrace - Trace Facility, which describes an online interface for setting up selective traces for a running region.

Format:

kixcontrol [-E] [-d string] [-h]

where:

-d string

Enables or disables generation of a formatted application dump file. string values are:

y: Generates a formatted application dump file when the runtime system detects an error, when a program uses the CICS ABEND command without a HANDLE ABEND command, or when errors, such as an out-of-storage condition, occur. This is the default.

n: Does not generate a formatted application dump file.

-E

This option is to be used only under the direction of technical support.

-h

Displays the usage message.


You can supply only one option at a time to kixcontrol.

Precautions

Restrict access to this utility.


kixdate - Change the Date/Time

The kixdate date/time configuration utility provides a menu-driven interface to change the date/time for Sun MTP and Sun MBM systems. By default, Sun MTP and Sun MBM reflect the system time. All dates displayed by Sun MTP in its logs, screens, traces, dumps, and reports use four digits for the year (YYYY).

Type kixdate at a command prompt to invoke the Date/Time Configuration Utility menu.

  FIGURE 2-1 Date/Time Configuration Utility ( kixdate )

Screen shot showing the Date/Time Configuration Utility main menu.[ D ]

Precautions

You must use a year between 1970 and 2030.

See Also

The Sun MTP Sun Mainframe Transaction Processing Software Administrator's Guide for instructions on using kixdate.

The Sun Mainframe Batch Manager Software Configuration Guide for information about using the date/time configuration utility with Sun MBM.


kixdump - Display Region Information

The kixdump utility displays information about the operation of a specific region. It can show the transactions that are currently executing, table information and file information, the trace table, and statistical information. This program links to the region's shared memory areas and can run only when these shared memory areas are present. If shared memory is corrupt, the output from kixdump contains information about the cause of the corruption.

Format:

kixdump [-A] [-a] [-G] [-g] [-M] [-P [resource-name]] [-q]
[-s [validate|dumplinks|
address]]
[-S a|cefipqrstuv] [-T] [-u] [-v]

where:

-A

Dumps the asynchronous START queue entries. Asynchronous START queue entries are created in memory by Sun MTP to support interval control commands. Refer to the Sun Mainframe Transaction Processing Software Troubleshooting and Tuning Guide.

-a

Sets all the dump options: gmstTuv.

Never use the -a option when a region is functioning normally.

-G

Displays a formatted dump of the terminal entries in the TCT.

-g

Displays a raw dump of the terminal entries in the TCT. The number of terminals depends on the maximum number of terminals set in the VCT. See Chapter 7 for additional information.

-M

Displays the address values for shared memory, maximum core, and threshold memory. The setting for threshold memory is determined by the -M t and -M c options of the unikixmain command.

-P [resource-name]

Reports the contents of the PPT structure in memory. You can specify a generic name.

If a mapset name is specified, the rescount of the mapset is displayed along with the transaction processor(s) using the map. For example:

To report information about a specific resource, type:

$ kixdump -P INVPGM1

To report information about all resources whose names start with INV, type:

$ kixdump -P 'INV*'

-q

Displays basic information about the active temporary storage queues: queue name, queue type, current size, number of items and the last item read from the queue.

-s validate | dumplinks|
address

Displays shared memory information, which permits a user to perform one of these actions

 

validate

  • Tests the integrity of shared memory. Sun MTP allocates shared memory in large blocks. The size of the shared memory blocks is set by the value of the -S option of the unikixmain command.
  • When shared memory is required for temporary storage (main), VSAM browse control areas, terminal I/O areas, and so on, these blocks of shared memory are broken into smaller areas. C
  • This option checks the headers for all these allocated smaller areas to ensure that no transaction has overwritten any of the headers.

 

dumplinks

  • Dumps the headers of all areas allocated out of shared memory. The information displayed includes the type of area, size, and the transaction processor that allocated it.

 

address

  • Dumps a specific area of shared memory in the format:

-s "0x<hex address> by 0x<hex length>"

Use this option only after you have determined a specific address and length by using the dumplinks option.

-S a | cefipqrstuv

Displays all or selected statistics on the current region.

 

a Displays all statistics; equivalent to setting the cefipqrsuv parameters.

c Displays the CICS command statistics; information about each executed CICS command.

e Displays the environment variables; information about the environment variables that the region is using.

f Displays the file statistics; information about the number of reads and writes for each file.

i Displays the IPC usage (shared memory, message queues, semaphores) for this region.

p Displays the application statistics; information about each transaction that is executing.

q Displays the queue statistics; information about the current status of the IPC queues used by the region.

r Displays the before images statistics; information about the number of before images and the number of flushes to the recovery file.

s Displays the summary statistics; information about the overall system.

t Displays usage statistics for all the transaction classes in a region.

u Displays the CICS transaction statistics; information about each executed transaction.

v Displays the CICS program statistics; information about each executed program.

-T

Dumps the system tables; displays the internal format for all the tables that are loaded into shared memory.

-u

Dumps the user area; gives information about all transaction processors.

-v

Creates a formatted dump of the VSAM data areas, which displays information about each buffer, any active enqueues, any active update queue items, file control blocks, access control blocks, and so on.



kixeformat - Format Internal Trace Dumps

You can use the kixeformat utility to format internal trace dumps.



caution icon

Caution - This utility should only be used under the direction of your authorized service provider.



Format:

kixeformat [-i] [-v] [-a|-b|-o filename] filename

where:

-i

Turns indentation on.

-v

Does not display variable names.

-a

Formats the ASCII trace table file.

-b

Formats the binary trace file.

-o filename

Produces an ASCII trace file from a binary trace file. You must specify a file name for the output file.

filename

Identifies the internal trace dump file to format.



kixetrace - Trace Facility

You can use the kixetrace utility to change the Sun MTP tracing option while the region is running. This command takes no arguments.



caution icon

Caution - This utility should only be used under the direction of your authorized service provider. Refer to the Sun Mainframe Transaction Processing Software Troubleshooting and Tuning Guide.



Format:

kixetrace

After you type the command, the Trace Administration Utility menu is displayed.

  FIGURE 2-2 Trace Administration Utility Menu

Screen shot showing the Trace Administration Utility menu.[ D ]


kixexpcat - Export the VSAM Catalog

The kixexpcat utility performs two functions:

Format:

kixexpcat -c catalog-file [-l ascii-file -x {Y|N}]]

where:

-c catalog-file

Identifies the catalog file to display on standard output or to export to an ASCII file. Required. Do not use the file name extension when typing the name of the catalog file. For example, if your catalog file is CATALOG (comprised of CATALOG.idx and CATALOG.dta), use CATALOG.

When used with the -l option, exports the named catalog file to an ASCII text file.

-l ascii-file

Creates an ASCII text version of catalog-file in the named file. The text version is named exactly as you type ascii-file. If you want it to have, for example, a .lst extension, you must include .lst as part of ascii-file.

-x {Y|N}

Directs kixexpcat to set the "batch read-locking" flag to either Y (read-locking) or N (no read-locking) on the exported VSAM primary cluster definition ("P") records. This option takes effect only on VSAM primary cluster records that have not been updated with any value other than blanks. This option has no effect unless the VSAM catalog file existed in a version of the software prior to Release 8.0.


The following line shows an ASCII record for a primary cluster. The "batch read-locking" field follows the key-ofs field.

P,environment,filename,{F|V},file-type,rcd-len,key-len,key-ofs,{Y|N},{Y|N},,,

Type the following command to display an ASCII text version of the VSAM catalog on your terminal:

$ kixexpcat -c $KIXSYS/CATALOG

The following command creates an ASCII text file of the catalog named test.lst in your current working directory:

$ kixexpcat -c $KIXSYS/CATALOG  -l test.lst

See Also

The Sun Mainframe Transaction Processing Software Administrator's Guide, which describes the format of the ASCII text file.


kixexptbl - Export Tables

The kixexptbl utility exports tables. To execute this utility, change the directory to $KIXSYS and type the kixexptbl command at the prompt. kixexptbl creates .lst files from each of the .tbl files located in the $KIXSYS directory, including the $KIXSYS/unikix.dir directory. If you have groups defined in the Group Control Table (GCT), kixexptbl writes the .lst file to the group directory specified. If you defined your resources in the DFHUSD file, the tables in the $KIXSYS/rdo.dir directory are also exported. This utility has no options.

Format:

kixexptbl

The following table shows how native table files are affected by running the kixexptbl utility.

KIXSYS

unikix.dir

rdo.dir

Group 1

Group 2

Before running kixexptbl

fct.tbl

pct.tbl

ppt.tbl

gct.tbl

fct.tbl

pct.tbl

ppt.tbl

txc.tbl

fct.tbl

pct.tbl

ppt.tbl

 

fct.tbl

pct.tbl

ppt.tbl

tct.tbl

fct.tbl

pct.tbl

ppt.tbl

tct.tbl

After running kixexptbl

fct.lst

pct.lst

ppt.lst

gct.lst

fct.lst

pct.lst

ppt.lst

txc.lst

fct.lst

pct.lst

ppt.lst

 

fct.lst

pct.lst

ppt.lst

tct.lst

fct.lst

pct.lst

ppt.lst

tct.lst




Note - The GCT is always located in the $KIXSYS directory.




kiximpcat - Import an ASCII Catalog File

The kiximpcat utility creates two files (*.dta and *.idx) from the specified ASCII text file. These two files can be used as the VSAM catalog. The Sun Mainframe Transaction Processing Software Administrator's Guide describes the format of the ASCII text file.

Format:

kiximpcat -c catalog-file -l ascii-file

where:

-c catalog-file

Identifies the VSAM catalog, which consists of two files in the VSAM catalog format with catalog-file as the base name and .dta and .idx extensions.

-l ascii-file

Identifies the ASCII text file to use as input to create the .dta and .idx files; must be in sorted order. The block size record (for example, B,4K or B,8K) must be the first record of the file.


You can give the imported and exported files any name. However, if you are using the imported file as the region's VSAM catalog, you must rename the files to CATALOG.idx and CATALOG.dta before starting the region.

The following command creates the files $KIXSYS/CATALOG.dta and $KIXSYS/CATALOG.idx from the ASCII text file CATALOG.lst:

$ kiximpcat -l /tmp/CATALOG.lst  -c $KIXSYS/CATALOG

The following command creates the files /tmp/TESTCAT.dta and /tmp/TESTCAT.idx from the ASCII text file /tmp/fred:

$ kiximpcat -l /tmp/fred  -c /tmp/TESTCAT

Precautions

Shut down the region before running this utility.


kiximptbl - Import Tables

This utility, when used in conjunction with kixexptbl, replaces the functionality of kixbtchtbl. To execute this utility, change the directory to $KIXSYS and type the kiximptbl command at the prompt. kiximptbl creates .tbl files from each of the .lst files located in $KIXSYS. If you have groups defined in the Group Control Table (GCT), kiximptbl writes the .tbl file to the group directory specified.

This utility has no options.

Precautions

Shut down the region before running this utility.


kixinstall - Configuration Utility

The kixinstall utility is used to define application languages, user objects, rules, and commands that are required for building the Sun MTP executables.

The kixinstall utility is also used when integrating one or more relational database management systems (RDBMS) or third-party products into the transaction, batch, and main servers. Based on the selections you make, the makefile, which builds the executables, is updated. kixinstall can also run the make process.

Refer to the Sun Mainframe Transaction Processing Software Installation Guide for instructions on how to use kixinstall. Also refer to the Sun Mainframe Transaction Processing Software Administrator's Guide for information about the make process for building the Sun MTP executables.


kixjob - Move Job to the Batch Queue

When a transaction executes a EXEC CICS WRITEQ TD command to a region's extrapartition transient data queue of the type JOB, the output is collected on a disk in a file named xxxxnnnn.job.

Where:

xxxx

Identifies the transient data queue.

nnnn

Indicates a unique sequential number that is incremented for each print or JOB file.


When a syncpoint is issued (either explicitly by the SYNCPOINT command or implicitly by the end of transaction), the file is closed. At that point, the kixjob shell script starts, changes the mode of the file to enable execution, and then moves the job to the first directory named in the KIXBTCH environment variable. If $KIXBTCH is not set, the shell script leaves the job in the $KIXSYS directory.

Format:

kixjob filename

where:

filename

Identifies the temporary file to use to collect the transient data output.


For example, if a JOB queue named BTCH exists, run kixjob as follows:

$ kixjob BTCH0001.job

where BTCH0001.job is the temporary file used to collect the transient data output. The first four characters of the file name is the queue name used for the writes: BTCH. The next four characters are the sequential number. The final four characters are the .job extension.

Precautions

Restrict access to this utility.


kixkeydef - Create or Edit a Key File

You can use the kixkeydef utility to create or edit a key file. The key definitions in the key file must match the key definitions of your application or emulation. Use this utility to create a definition for a key that is not on your keyboard. For example, if you are working on a system whose keyboard does not have a Reset key, you can define a function key or key sequence to perform the RESET function.



Note - On certain keyboards, you cannot redefine function keys F1 through F5. You must define other key sequences to provide the needed functions.



Format:

kixkeydef keyfile

where:

keyfile

Identifies the key file to create. If keyfile does not exist, it is created.


Whether you edit an existing key file or create a new key file, kixkeydef generates the key file in a set format. Any comments in an existing key file are lost.

FIGURE 2-3 shows an example of the kixkeydef screen. Refer to the Sun Mainframe Transaction Processing Software Configuration Guide for instructions on using the kixkeydef utility.

  FIGURE 2-3 kixkeydef Screen

Screen shot showing the Key Definition Utility screen, which is displayed when you type the kixkeydef command.[ D ]


kixmakecnv - Create a Conversion Table

The kixmakecnv utility creates a conversion table file to use with Sun MTP. The conversion table file is created in $UNIKIX/lib/cnvtbl.

Format:

kixmakecnv

There are no options.

See Also

The Sun Mainframe Transaction Processing Software Administrator's Guide for information about customizing the conversion table for languages other than U.S. English.


kixnrfs - Configure NRFS

The kixnrfs utility program configures the Native Recovery File System (NRFS). The NRFS is used in conjunction with settings in the VCT to provide recovery protection.

Before you use this utility, your system administrator must allocate a raw disk partition for NRFS. The first time you execute kixnrfs, you must be logged on as the root user. After the partition is initialized (see option -c), you can grant permissions to other user IDs, which allows them to use the utility to modify the configuration. Due to the nature of this program, restrict access to the user ID that administers the Sun MTP region.

Format:

kixnrfs [-c devname -n totblks -k kixsys -s startblk -l blocks]
[-a
devname -k kixsys -s startblk -l blocks]
[-r
devname -k kixsys -s startblk]
[-d
devname -k kixsys]
[
devname]

where:

-a devname

Appends new regions to an existing NRFS. You must also specify the -k kixsys, -s startblk, and -l blocks parameters.

-c devname -n totblks

Initializes a new NRFS partition and allocates a portion of the partition to the recovery file or files. You must specify the parameter -n totblks, where totblks is the total number of blocks available in the raw partition.

You must specify the -k kixsys, -s startblk, and -l blocks parameters to allocate the recovery file for a region.

-d devname

Deletes unneeded regions from the NRFS. Requires the -k kixsys parameter.

devname

Identifies a device file name that is the raw UNIX partition that is assigned for use as the NRFS. Using this parameter with the kixnrfs command produces a summary report of the NRFS configuration.

-k kixsys

Indicates the $KIXSYS value for the region that NRFS is to support. You must use a complete path name.

-l blocks

Indicates the number of blocks allocated for the recovery file for this region. You must use a number less than the total number of blocks available to the NRFS.

Total number of blocks available is calculated as:

Available blocks = totblks (sum of all previous blocks)

-r devname

Resets NRFS for a particular value of -k. The effect is to prevent Sun MTP from rolling back protected datasets after a system crash. Requires the -k kixsys and -s startblk parameters.

-s startblk

Indicates the starting block number for the recovery file. You must use a value greater than or equal to 1.


Make sure that the recovery files for multiple regions do not overlap. If this occurs, kixnrfs issues an error message.

Example

You want to use NRFS to support two separate regions. There are two $KIXSYS directories for the regions:

A raw partition of 5,419,008 bytes is located at device /dev/hd3. Because each NRFS block consists of 4096 bytes, to determine the total number of blocks in this partition, divide the number of bytes by 4096. The total number of blocks available is 1323. Of the 1323 blocks, the finance application is allocated 200, the accounting application another 200, and the final 923 blocks are not used.

To configure NRFS to these specifications, run the following command:

$ kixnrfs -c /dev/hd3 -n 1323 -k /users/local/mtp/mtp80/finance -s 1 - l 200 \
	-k /users/local/mtp/mtp80/accounts -s 201 -l 200

This command shows that the NRFS begins at absolute block 0, and the recovery file for the finance region begins at absolute block 1 (0+1). The single block between these is reserved for the NRFS directory. The accounts region starts at absolute block 201 (0+201). The values of -s for both regions are relative to the offset following NRFS Dir in FIGURE 2-4. The values of -s are used in the Offset field of the VCT when you configure recovery.

  FIGURE 2-4 NRFS Region

Diagram showing the NRFS configuration created by executing the kixnrfs command shown in the example.

Precautions

Restrict access to this utility.

The raw partition assigned for use as the NRFS must not be mounted.

See Also

The Sun Mainframe Transaction Processing Software Configuration Guide for the procedures to configure NRFS.

The Sun Mainframe Transaction Processing Software Message Guide for a description of the error messages generated by kixnrfs.

Usage Examples

This section shows how to use the kixnrfs command and its options.

The following code example shows the NRFS configuration report.

CODE EXAMPLE 2-1 kixnrfs Report
Native Recovery File System for Sun MTP version 8.0
 
	Starting block of this NRFS :0
	Number of blocks in this NRFS : 786433
	Number of recovery files in NRFS : 2
 
Recovery file 0:
	KIXSYS            : /myregion1/sys
	Starting Block    : 1
	Number of Blocks  : 524288
 
Recovery file 1:
	KIXSYS            : /myregion2/sys
	Starting Block    : 524289
	Number of Blocks  : 162144
 
Recovery file 2:
	KIXSYS            : /myregion3/sys
	Starting Block    : 686434
	Number of Blocks  : 100000
 


kixprint - Collect Print Output on Disk

During transaction execution, Sun MTP collects print output on disk. When a syncpoint is issued (either explicitly by the SYNCPOINT command or implicitly by the end of the transaction), all spooled output is printed.

Format:

kixprint -p printerid filename

where:

-p printerid

Indicates the value of the Printer ID field in the TCT; maximum of 14 characters.

filename

Identifies the temporary file used to accumulate the print output.


The default print command used within the kixprint shell script is lp -s. You can override this command by setting the SPOOLER environment variable. If a printer identifier is given, then add -d printerid or -P printerid to the command for an AT&T or a BSD spooler, respectively.

See Also

The Sun Mainframe Transaction Processing Software Configuration Guide for information about the kixprint shell script, including how to modify it for your site.


kixprntbl - Print Table Listing

This utility writes formatted reports for each table in a region. The reports are named for the table and have a .prn extension; for example, pct.prn. Each report contains a list of all of the region's entries for that table organized by group. To execute this utility, change the directory to $KIXSYS and type the kixprntbl command at the prompt.

Format:

kixprntbl

CODE EXAMPLE 2-2 shows part of a pct.prn file. The first group of entries, those starting with ACCT and BCCT, are not associated with any group; they are from the Program Control Table (PCT) in the $KIXSYS directory. The group of entries starting with PAYR are from the PCT in the directory defined for the payroll group in the GCT. The entries in the unikix group are from the PCT in the $KIXSYS/unikix.dir directory.

CODE EXAMPLE 2-2 pct.prn File--Example
Sun MTP           Program Control Table     08/27/2002 10:35:06
 
ACCT01  ,,AC01,0,1,DEF,D,0,,,,Y,,KIXDFLT 
ACCT02  ,,AC02,0,1,DEF,D,0,,,,Y,,KIXDFLT 
ACCT03  ,,AC03,0,1,DEF,D,0,,,,Y,,KIXDFLT 
ACCT03  ,,AC05,0,1,DEF,D,0,,,,Y,,KIXDFLT 
ACCT00  ,PA1 ,ACCT,0,1,DEF,D,0,,,,Y,,KIXDFLT 
ACCT03  ,,ACLG,0,1,DEF,D,0,,,,Y,,KIXDFLT 
BCCT01  ,,BC01,0,1,DEF,D,0,,,,Y,Y,KIXDFLT 
BCCT02  ,,BC02,0,1,DEF,D,0,,,,Y,N,KIXDFLT 
BCCT03  ,,BC03,0,1,DEF,D,0,,,,Y,Y,KIXDFLT 
BCCT03  ,,BC05,0,1,DEF,D,0,,,,Y,B,KIXDFLT 
BCCT00  ,,BCCT,0,1,DEF,D,0,,,,Y,Y,KIXDFLT 
BCCT03  ,,BCLG,0,1,DEF,D,0,,,,Y,N,KIXDFLT 
PAYR01  ,,PY01,0,1,DEF,D,0,,,payroll ,Y,,PAYROLL
PAYR02  ,,PY02,0,1,DEF,D,0,,,payroll ,Y,,PAYROLL
PAYR03  ,,PY03,0,1,DEF,D,0,,,payroll ,Y,,PAYROLL
BATCH000,,CBCH,0,1,DEF,N,0,,,unikix  ,Y,,KIXDFLT
KXCCIN  ,,CCIN,0,1,DEF,D,0,,,unikix  ,N,Y,KIXDFLT
CEBR    ,,CEBR,0,1,DEF,N,0,,,unikix  ,Y,,KIXDFLT
CECI    ,,CECI,0,1,DEF,D,0,,,unikix  ,N,,KIXDFLT
CEDF    ,,CEDF,0,1,DEF,N,0,,,unikix  ,Y,,KIXDFLT
CEMT    ,,CEMT,0,1,DEF,N,0,,,unikix  ,Y,,KIXADMIN
CESF    ,,CESF,0,1,DEF,N,0,,,unikix  ,Y,,KIXDFLT
CSSNCESN,,CESN,0,1,DEF,N,0,,,unikix  ,Y,,KIXDFLT
...
...


kixrcvdmp - Display a Recovery File

The kixrcvdmp utility displays the contents of the Sun MTP recovery file or the NRFS recovery file.

Format

kixrcvdmp -f filename [-s blocksize] [-n #] [-e]

where:

-f filename

Identifies the recovery file.

If you are using the standard recovery file, this usually matches the Filename field on the VCT screen.

If you are using NRFS, this is the name of the raw disk partition.

-s blocksize

Indicates the VSAM block size.

If you are using the standard recovery file, this value must match the VSAM block size specified for the region.

If you are using NRFS, this value must be 4096.

-n #

Indicates the NRFS Recovery file number. This number is displayed on the configuration report generated by the kixnrfs devname command.

-e

Indicates that the command must stop at the end of the recovery area.


To dump a standard recovery file that uses a 16 KByte block size, execute the following command, using your recovery file name:

$ kixrcvdump -f MYRECOV.dta -s 16384 -e

To dump an NRFS recovery file, execute the following command, using your NRFS partition:

$ kixrcvdump -f /dev/dsk/c4t0d0s4 -s 4096 -n 7 -e


kixsalvage - Salvage VSAM Data

The kixsalvage utility scans and dumps all salvageable data from a corrupted VSAM file to a new file or files. By default, the data is written out in the Sun MTP recordv format; you must sort the output file(s). As an alternative, use the -c option to specify the Micro Focus variable record output format, which enables you to sort the output with a COBOL sort program.

Format:

kixsalvage [-2|-c] [-l size] [-s] [-v] [-r] [[-o outputfile]...]
datasetname

where:

-2

Writes a 2-byte record header instead of the default 4-byte record header. This option is incompatible with the -c option.

-c

Writes the output file in the COBOL variable record format.

-l size

Indicates the maximum length, in bytes, for an output file. You can modify the size with G, K, and M, indicating GB, KB, and MB, respectively.

-o outputfile

Identifies the output file name(s); up to eight names. If the output files listed with the -o option do not provide enough space to contain the salvaged records, the program creates additional files named:

[datasetname].slvgXXX

where:

[datasetname]: Specifies the dataset name given on the command line.

XXX: Specifies a number between 000 and 999.

-r

Converts the data to machine format. Only for use on reverse-byte systems.

-s

Performs a scan only to display the number of blocks and records that are salvageable. This enables you to determine the number and size of output files that are required. Use this information to determine if the file is worth salvaging.

-v

Activates the verbose flag. With the verbose flag set, the program writes a line of data to the screen for each record that is salvaged. The format of the output is illustrated in the example at the end of this section.

datasetname

Indicates the file name of the dataset to salvage. This parameter is required.


The following example shows the format of kixsalvage output with the -v option:

Key of record 1:
43464544 46494c45 20202020 20204b49     *CFEDFILE      KI*
58535953 20202020 20202020 20           *XSYS            *
Key of record 2:
43464544 46494c45 20202020 20204b49     *CFEDFILE      KI*
58535953 20202020 20202020 31           *XSYS        1   *
Key of record 3:
43464544 4c4f4720 20202020 20204b49     *CFEDLOG       KI*
58535953 20202020 20202020 20           *XSYS            *
Key of record 4:
43464544 52524453 20202020 20204b49     *CFEDRRDS      KI*
58535953 20202020 20202020 20           *XSYS            *
Key of record 5:
4b4b2020 20202020 20202020 20204b49     *KK            KI*
58535953 20202020 20202020 20           *XSYS            *
Key of record 6:
4b585446 494c4520 20202020 20204b49     *KXTFILE       KI*
58535953 20202020 20202020 20           *XSYS            *
processed        1 valid blocks
salvaged         6 records

Precautions

Restrict access to this utility.


kixsnap - Take System Snapshot

The kixsnap script captures information about a region's transaction processors and tables, system processes, and users at the time of an abnormal termination. kixsnap creates the following files:

Format:

kixsnap [-d pathname]

where:

-d pathname

Identifies the directory path name where the files are written.


kixsnap searches for the directory to write the files in the following order. The first directory in the search order that kixsnap can write to is selected.

1. The directory specified in the -d option.

2. The directory specified by the KIXSNAPDIR environment variable.

3. $KIXSYS/debugkix. If a directory is not specified by -d or $KIXSNAPDIR, kixsnap writes the files to this directory. If this directory does not exist, kixsnap creates it.

4. $KIXSYS. If the debugkix directory does not exist under $KIXSYS and cannot be created, kixsnap writes the files to $KIXSYS.

If you log in using a new terminal because your terminal was locked by an abort, you must reset all region environment variables (including $KIXSYS) and verify that $UNIKIX/bin is in your path before you run kixsnap.

The following output shows the kixsnap command, the list (ls) command, and the list of snapshot files.

$ kixsnap
$ ls $KIXSYS/debugkix/snapshot*
snapshot.1204_081930
snapshot.1204_081930.vsam
snapshot.1204_081930.trace

See Also

The Sun Mainframe Transaction Processing Software Troubleshooting and Tuning Guide.


kixstart - Start a Region

The shell script kixstart starts a default version of the Sun MTP server, unikixmain. Note that kixstart does not delete log files as it did in releases prior to 4.1. Messages from subsequent executions of the server are now appended to the log files.

If the unikixmain server process is running when kixstart is executed, the shell script does not start another copy of unikixmain. It returns the following messages:

02/28/2002 09:24:25 unikixmain  :KIX0100E [kxcreateq] UNIX errno 17 from msgget
02/28/2002 09:24:25 unikixmain  :UNIX errno 17 (File exists)
02/28/2002 09:24:25 unikixmain  :KIX0199E IPC create of KXMAINQ (7) failed

Format:

kixstart

The kixstart utility reads the options and parameters and incorporates them into the unikixmain command line. You can also customize a local version of the kixstart shell script--for example, to back up and delete log files from previous executions of unikixmain.

Precautions

Restrict access to this utility.

See Also

unikixmain - Sun MTP Server Process, which describes all the options and parameters that you can include when you invoke kixstart.


kixstop - Shut Down a Region

By default, the kixstop utility performs a CEMT PERFORM SHUTDOWN transaction, which shuts down the region in an orderly manner and allows the region to quiesce prior to being terminated.

Format:

kixstop [-i]

where:

-i

Performs a CSMT SHUT,YES transaction, which causes an immediate shutdown. The immediate shutdown does not allow transactions to terminate normally, thus causing them to roll back.


Precautions

Restrict access to this utility.

See Also

The Sun Mainframe Transaction Processing Software Administrator's Guide, which describes the CEMT and CSMT transactions.


kixupdateGCT - Update GCT

The kixupdateGCT command enables you to update the Group Control Table (GCT) from the command line. Changes made to the GCT do not take effect until the region is restarted.



Note - Execute the command from the directory where gct.tbl is located, or where the new gct.tbl should be created.



Format:

kixupdateGCT -I | -M | -D -g groupname [-r Y | N] [-d directory]

where:

-d directory

Indicates the directory in which the group name is to reside. The path name is a maximum of 50 characters.

-D

Deletes an entry. For an entry to be deleted, the -g groupname option must be present; any other argument is ignored.

-g groupname

Identifies the group to which the action is directed. groupname is a maximum of 8 characters.

-I

Inserts an entry. For an entry to be inserted, all arguments except -r must be present. If -r is not present, the default is Y (entry is read-only).

If no gct.tbl exists, a new file is created as the result of the insert action. If the action is insert and groupname already exists in the table, the action is changed to modify; you cannot insert duplicate groupname.

-M

Modifies an entry. For an entry to be modified, the -g groupname option and one or both of -r and -d must be present.

-r Y | N

Indicates whether groupname is read-only (Y) or has read and write permission (N).


The kixupdateGCT command generates the following error and information messages.

Message

Cause

GROUP name too long

More than 8 characters entered for groupname.

GROUP directory name too long

More than 50 characters entered for directory.

RDONLY option must be Y or N

Something other than Y or N entered as an argument to the -r option.

No Action specified: Must be -M, -I, or -D

No action entered.

No Group specified: Must be
-g dddddd

No groupname entered.

No Group Directory specified

No directory entered for location of groupname.

Group already present -- Modify done

groupname that already exists entered for an insert action.

gct.tbl not present: No action taken

Request for modify or delete action and no GCT exists.

No gct.tbl found -- Insert created gct.tbl

Insert request with valid arguments results in the creation of a gct.tbl when none exists.


See Also

Grouping Table Entries.

Group Control Table (GCT).


kixvalfle - Validate VSAM Clusters

The kixvalfle utility validates a VSAM cluster. Use this utility whenever the structure of a VSAM file is in doubt. If the file is a key-sequenced dataset (KSDS) or alternate index file, kixvalfle also checks the links between the blocks of the index file.

kixvalfle with no options (the default) validates the links between blocks in data files and in index files, if index files exist.

Format:

kixvalfle [ -i -k -v ] datasetname

where:

-i

Verifies that index entries point to valid blocks in the data file. This is the most stringent check.

-k

Verifies each key in the index file to ensure that all records are in ascending key sequence.

-v

Prints a line of data for each block that is processed.

datasetname

Identifies the dataset used by kixvalfle to access the VSAM cluster associated with it. This parameter is required.



kixverify - Display/Reset Activity Counts

The kixverify program displays and resets the activity counts for a VSAM cluster.

If you specify ALL instead of a dataset name, kixverify acts on all the files defined in the VSAM catalog for the region.

Format:

kixverify [[-v | -r [ALL | datasetname]]

where:

ALL

Resets or displays the activity counts for all datasets.

-r

Resets the activity counts for all components of the specified VSAM dataset or all datasets.

-v

Displays the activity counts for all components of the specified VSAM dataset or all datasets in verbose mode.

datasetname

Identifies the primary dataset to verify; must be listed in the File Control Table (FCT).


You must run kixverify -rALL after running kixclean.

Precautions

Restrict access to this utility.


kixview - Display Files

The kixview program displays the contents of a file in a dump format with the hexadecimal representation of the contents on the left side of the display and the text contents on the right side of the display. kixview can display both ASCII and EBCDIC files. For EBCDIC files, kixview converts the bytes into ASCII before displaying the file.

Format:

kixview [-e|-E] [-A conversion-table] file1, file2, ... filen

where:

-e|-E

Specifies that the input files are EBCDIC files.

-A conversion-table

Specifies the EBCDIC to ASCII conversion table to use. If you are viewing EBCDIC files and do not specify a conversion table, the default conversion table is used (IBM-1047 to ISO8859-1).

file1 ... filen

Identifies the names or full path names of the files.


kixview provides two search methods.


procedure icon  To Search for a Hexadecimal Value

1. Type /.

2. In response to the (A)scii or (H)ex prompt, type h. Then type the hexadecimal search value and press Return.

kixview moves the line containing the next instance of that value to the top of the screen and positions the cursor on the value.


procedure icon  To Search for an ASCII (Character) Value

1. Type /.

2. In response to the (A)scii or (H)ex prompt, type a. Then type the ASCII search string and press Return.

kixview moves the line containing the next instance of that value to the top of the screen and positions the cursor on the value.



Note - When viewing EBCDIC files, kixview converts the input ASCII pattern into EBCDIC before matching it with characters in the file.



You can also use the following keys in the kixview display:

q

Quits kixview and returns to the command prompt.

/

Searches forward in the file. kixview displays the (A)scii or (H)ex prompt and moves the line containing the next instance of the value to the top of the screen.

?

Searches backward in the file. kixview displays the (A)scii or (H)ex prompt and moves the line containing the next instance of the value you type to the top of the screen.

n

Locates the next instance in the same direction as the original search.

N

Locates the next instance in the reverse direction of the original search.

^b

Scrolls back one screen.

^f

Scrolls forward one screen.

j

Moves the cursor forward one line.

k

Moves the cursor back one line.

l

Moves the cursor right one character.

h

Moves the cursor left one character.



xxxstart - Specify a Startup Keyboard

Script files are supplied for starting a region in an X server environment with a specific terminal/keyboard combination. The script files, which reside in $UNIKIX/bin, perform the following actions:

Format:

xxxstart

where:

xxx

Indicates a prefix that denotes a particular combination of terminal and keyboard:

ncd101: NCD X terminal 101-key keyboard

ncd97: NCD X terminal 97-key keyboard

ncdvt: VT100-, 200-, or 320-type keyboards

ncd: NCD workstation keyboard

sun: Sun workstation keyboard

xterm: X Terminal 101-key keyboard


To start the region from an NCD X terminal with a 101-key keyboard, type the following command:

$ ncd101start


xxxunikix - Specify a Client Keyboard

Most X servers have a TERM variable value of term or xterms, and each device can have a different keyboard. To handle different keyboards, you can start a region by selecting the appropriate xxxunikix script, which invokes an xterm with special keyboard definition resources. The client keyboard startup files are located in the $UNIKIX/bin directory; for example, $UNIKIX/bin/xtermunikix and $UNIKIX/bin/ncd101unikix. The file xtermunikix defines a 101-key keyboard.

Format:

xxxunikix parameter1 [parameter2]

where:

xxx

Indicates a prefix that denotes a particular combination of terminal and keyboard:

ncd101: NCD X terminal 101-key keyboard

ncd97: NCD X terminal 97-key keyboard

ncdvt: VT100-, 200-, or 320-type keyboards

ncd: NCD workstation keyboard

sun: Sun workstation keyboard

xterm: X terminal 101-key keyboard

dtterm: Desktop terminal window

parameter1

Identifies the Sun MTP client process to execute; for example, unikix. This is the name that will appear in the window's title bar. There is no default value for this parameter.

parameter2

Passes arguments to the xterm -geometry parameter, which specifies the coordinates of the X window on the screen; for example, +400+0. Refer to the man page on xterm for a more detailed description of the format of this parameter. If this parameter is omitted, the window manager might require interactive placement of the window.


To start a client session on an X terminal with a 101-key keyboard, type the following command:

$ xtermunikix unikix

See Also

The Sun Mainframe Transaction Processing Software Configuration Guide for more information about UNIX terminals.