Table of Contents Previous Next PDF


System Commands and Transactions

System Commands and Transactions
System Commands
 
cpy2view32(1)
Name
cpy2view32—Generates Oracle Tuxedo VIEW32 definition file from COBOL copybook file.
Synopsis
cpy2view32 [OPTION...] FILE
Description
This utility parses the COBOL copybook file and generates the corresponding Oracle Tuxedo VIEW32 definition files.
It supports the following options:
-n
Specifies the source copybook is in "normal" format (i.e., copybook contains sequence number area (columns 1 through 6 is the sequence number area, followed by the indicator area)).
-e
Specifies the source copybook is in "exceptional" format (i.e.,copybook does not contain a sequence number area (the first column is the indicator area)).
-o
Specifies the output file name, followed parameter is the output file name. If this parameter is not specified, the output file name changes the suffix of the input file name to .v. For example, abc.cbl is converted to abc.v.
This utility supports the following annotation in the source copybook:
* @binary: by default, copybook data types without the following qualifiers are converted to string: BINARY, COMP, COMP-1, COMP-2, COMP-3, COMP-4, COMP-5, PACKED-DECIMAL. With the * @binary=true annotation, the copybook data types without those qualifiers are converted to CARRAY. * @binary=false changes the conversion rule back to the default. When this annotation is defined on a group, all subordinates in the group are affected.
Environment Variables
PATH
The cpy2view32 utility is written in Java. You must install JDK 1.6 or above and add the Java command "java" to the PATH environment variable.
Example(s)
1.
The following example converts normal copybook file abc_orig.cbl to view file abc_orig.v:
cpy2view32 /home/abc_orig.cbl
2.
cpy2view32 -e /home/abc.cbl
3.
The following example converts normal copybook file abc_orig.cbland outputs to view file xyz.v:
cpy2view32 -o xyz.v /home/abc_orig.cbl
4.
Listing 10‑1 through Listing 10‑4 provide Copybook and view file output examples:
Listing 10‑1 Copybook Example 1
#########################
01 BOOK-INFO.
05 BOOK-ID PIC 9(9) COMP-5.
05 BOOK-NAME PIC X(100).
05 PUBLISHER PIC X(100).
05 PRICE USAGE COMP-1.
#########################
 
Listing 10‑2 VIEW32 Output Example 1
#########################
#type cname fbname count flag size null
 
VIEW book_info
unsignedint book_id - 1 - - -
string book_name - 1 - 100 -
string publisher - 1 - 100 -
float price - 1 - - -
END
#########################
 
Listing 10‑3 Copybook Example 2
#########################
01 COMPUTER.
05 COMPUTER-ID PIC 9(9) COMP-5.
05 COMPUTER-NAME PIC X(20).
05 PRODUCER PIC X(40).
05 FILLER PIC X(4).
 
05 SELL-PRICE USAGE COMP-2.
05 RENTAL-PRICE PIC S9999V999 PACKED-DECIMAL.
05 KEYBOARD-PRICE PIC S9(4) SIGN IS LEADING SEPARATE.
05 MOUSE-PRICE PIC S9(4) SIGN IS LEADING.
 
05 FILLER PIC X(4).
* define other computer components below
05 CPU.
10 MODEL PIC X(20).
10 PRODUCER PIC X(40).
10 PRICE USAGE COMP-1.
05 COMPUTER-MEMORY OCCURS 4 TIMES.
10 MODEL PIC X(20).
10 PRODUCER PIC X(40).
10 PRICE USAGE COMP-1.
05 MAINBOARD.
10 MODEL PIC X(20).
10 PRODUCER PIC X(40).
10 PRICE USAGE COMP-1.
05 MONITOR.
10 MODEL PIC X(20).
10 PRODUCER PIC X(40).
10 PRICE USAGE COMP-1.
05 HARDDISK.
10 MODEL PIC X(20).
10 PRODUCER PIC X(40).
10 PRICE USAGE COMP-1.
#########################
 
Listing 10‑4 VIEW32 Output Example 2
#########################
#type cname fbname count flag size null
 
VIEW cpu
string model - 1 - 20 -
string producer - 1 - 40 -
float price - 1 - - -
END
 
VIEW computer_memory
string model - 1 - 20 -
string producer - 1 - 40 -
float price - 1 - - -
END
 
VIEW mainboard
string model - 1 - 20 -
string producer - 1 - 40 -
float price - 1 - - -
END
 
VIEW monitor
string model - 1 - 20 -
string producer - 1 - 40 -
float price - 1 - - -
END
 
VIEW harddisk
string model - 1 - 20 -
string producer - 1 - 40 -
float price - 1 - - -
END
 
VIEW computer
unsignedint computer_id - 1 - - -
string computer_name - 1 - 20 -
string producer - 1 - 40 -
string filler1 - 1 - 4 -
double sell_price - 1 - - -
carray rental_price - 1 - 4 -
string keyboard_price - 1 - 5 -
string mouse_price - 1 - 4 -
string filler2 - 1 - 4 -
struct cpu cpu 1 - - -
struct computer_memory computer_memory 4 - - -
struct mainboard mainboard 1 - - -
struct monitor monitor 1 - - -
struct harddisk harddisk 1 - - -
END
#########################
 
Limitations
The following are general cpy2view32 limitations:
1.
This tool does not parse REDEFINES clause, REDEFINES clause and their subordinate items are skipped.
2.
POINTER phrase, FUNCTION-POINTER phrase and PROCEDURE-POINTER phrase are skipped in the conversion.
3.
VALUE clause is skipped in the conversion.
4.
SYNCHRONIZED clause is skipped in the conversion.
5.
JUSTIFIED clause is skipped in the conversion.
6.
BINARY, COMP, and COMP-4 are synonyms, they are converted to CARRAY in view file.
Mif2View32(1)
Name
Mif2View32—Generates VIEW32 definition file according to the metadata input file and updates the given FML32 definition file.
Synopsis
Mif2View32 -i miffile -o viewfile -f fml32file -w webservice.desc [-v]
Description
Mif2View32 generates VIEW32 definition file according to the metadata input file and updates the given FML32 definition file. The generated nest VIEW32 definition file keeps the same structure with MIF; therefore, we can map the C structure to an FML32 structure.
Options
Mif2View32 supports the following options.
-i miffile
Specifies the metadata input file name.
-o viewfile
Specifies the output View32 definition file name.
-f fml32file
Specifies the updated FML32 definition file.
-w webservice.desc
Specifies webservice.desc configuration file.
-v
Indicates whether to output details or not.
Example(s)
1.
Listing 10‑5 provides an MIF example.
Listing 10‑5 MIF Example
############
# SERVICE: * DFH0XCMNOperation
############
service=DFH0XCMNOperation
servicetype=service
export=Y
inbuf=FML32
outbuf=FML32
tuxservice=DFH0XCMNOperation
errbuf=FML32
servicemode=webservice
param=DFH0XCMNOperation
count=1
requiredcount=0
fldnum=10025
type=fml32
access=in
paramschema=XSD_E:DFH0XCMNOperation@http://www.DFH0XCMN.DFH0XCP3.Request.com
(
param=ca_request_id
count=1
requiredcount=0
fldnum=10019
type=string
access=in
paramschema=XSD_E:ca_request_id@http://www.DFH0XCMN.DFH0XCP3.Request.com
primetype=string
param=ca_response_message
count=1
requiredcount=0
fldnum=10021
type=string
access=in
paramschema=XSD_E:ca_response_message@http://www.DFH0XCMN.DFH0XCP3.Request.com
primetype=string
param=ca_inquire_request
count=1
requiredcount=0
fldnum=10009
type=fml32
access=in
paramschema=XSD_E:ca_inquire_request@http://www.DFH0XCMN.DFH0XCP3.Request.com
(
param=ca_list_start_ref
count=1
requiredcount=0
fldnum=10017
type=short
access=in
paramschema=XSD_E:ca_list_start_ref@http://www.DFH0XCMN.DFH0XCP3.Request.com
primetype=unsignedShort
param=ca_cat_item
count=15
requiredcount=0
fldnum=10001
type=fml32
access=in
paramschema=XSD_E:ca_cat_item@http://www.DFH0XCMN.DFH0XCP3.Request.com
(
param=ca_item_ref
count=1
requiredcount=0
fldnum=10013
type=short
access=in
paramschema=XSD_E:ca_item_ref@http://www.DFH0XCMN.DFH0XCP3.Request.com
primetype=unsignedShort
param=on_order
count=1
requiredcount=0
fldnum=10029
type=short
access=in
paramschema=XSD_E:on_order@http://www.DFH0XCMN.DFH0XCP3.Request.com
primetype=unsignedShort
)
)
)
 
2.
Listing 10‑6 provides a VIEW32 output file example.
Listing 10‑6 VIEW32 Output Example
VIEW ca_cat_item_v
#TYPE CNAME FBNAME COUNT FLAG SIZE NULL
short ca_item_ref_v_times ca_item_ref_times 1 - - 0
short ca_item_ref_v ca_item_ref 1 - - 0
short on_order_v_times on_order_times 1 - - 0
short on_order_v on_order 1 - - 0
END
 
VIEW ca_inquire_request_v
#TYPE CNAME FBNAME COUNT FLAG SIZE NULL
short ca_list_start_ref_v_times ca_list_start_ref_times 1 - - 0
short ca_list_start_ref_v ca_list_start_ref 1 - - 0
short ca_cat_item_v_times ca_cat_item_times 1 - - 0
struct ca_cat_item_v ca_cat_item 15 - - 0
END
 
VIEW DFH0XCMNOperation_v
#TYPE CNAME FBNAME COUNT FLAG SIZE NULL
short ca_request_id_v_times ca_request_id_times 1 - - 0
string ca_request_id_v ca_request_id 1 - 255 '\0'
short ca_response_message_v_times ca_response_message_times 1 - - 0
string ca_response_message_v ca_response_message 1 - 255 '\0'
short ca_inquire_request_v_times ca_inquire_request_times 1 - - 0
struct ca_inquire_request_v ca_inquire_request 1 - - 0
END
 
tcxcsdcvt (1)
Name
tcxcsdcvt -- translates RDO file to all z/OS resource configuration files.
Synopsis
tcxcsdcvt [-option] [Filename]
Description
tcxcsdcvt translates RDO files to all z/OS resource configuration files.The generated resource configuration files by default are found in the current directory where this tool is run.
tcxcsdcvt supports the following options:
-h
Display help information for this tool.
-d <director>
Specifies the target directory for generated configuration files.
-D
Generate log file in case there is error information during conversion.
Example(s)
To convert the RDO file "lirgao.cicsb.dfhcsd", enter following command:
tcxcsdcvt lirgao.cicsb.dfhcsd
tcxmapgen(1)
Name
tcxmapgen — CICS Runtime MAPSET Generator.
Synopsis
tcxmapgen [-options] <file>
Description
CICS Runtime provides a mapset generator to compile BMS macro source files, to produce a physical (binary) file and a symbolic (copybook) file. There is also an option to produce a listing file. During execution, the mapset generator validates the syntax and level of support for each BMS macro statement.
The generated physical (binary) file should be used in the MAPSET configuration file. See “Mapset Configuration File” in CICS Runtime Configuration Files.
The generated symbolic (copybook) file should be included when you compile the CICS/COBOL program which uses the MAP in this MAPSET
Options
The command options are:
[-c]
Specifies that only COBOL copybook (.cpy) output file is generated.
[-l]
Specifies a listing output file (.lst) is produced.
[-m]
Specifies that only binary mapset file (.mpdef) is produced.
[-o file]
Specifies the name used for the generated output files. The compiler uses the file name with an appended extension when creating the output file names.
[-u]
Specifies that the output fields are not sorted but kept in the defined order. Without specifying this option, all fields in a map are sorted according to their positions by default.
[-A]
Generates aligned map. In aligned map, the length field associated with a BMS data field in the BMS DSECT is always aligned on a halfword boundary.
Note:
With -A, users can generate aligned map; without -A, users can generate unaligned map (default behavior).
Example(s)
To compile the BMS source file file.map,use the following command:
$ tcxmapgen -o file file.map
The resulting binary mapset file is file.mpdef.
artadmin (1)
Name
artadmin — ART CICS Runtime administration.
Synopsis
artadmin [-p <profile>]
Parameter
Profile
The name of the profile file used for authentification. This parameter is useful for secure Oracle Tuxedoconfiguration. The profile file must be created with genappprofile. If no file name is provided, it defaults to ~/.ADMINappProfile.
Description
In some cases it is necessary to modify the configuration while the system is running. Normally, configuration changes which are relative to performances are managed by Oracle Tuxedo or the RDBMS level using commands (for example, tmadmin) or Oracle TSAM for Oracle Tuxedo dynamic configuration.
However, if the requirement is more functional (for example, needing to put some transactions online, installing a hot fix for some programs and screens, or changing some resource configurations), you must use artadmin.
artadmin is useful when making hot configuration changes in the CICS resources of a running ART CICS system. It allows the administrator to:
artadmin is launched interactively (similar to tmadmin). When the artdmin is launched and connects to Oracle Tuxedo successfully, it returns a prompt requiring you to enter the commands.
artadmin commands
Commands can be entered either by full name or abbreviation (as given in the parenthese), followed by any appropriate arguments. Arguments appearing in the square brackets [] are optional, and those in curly braces {} indicate a selection from mutually exclusive options.
To let a set of commands be executed together, the administration comannds entered are kept in the buffer and performed only when the administrator enters a perform commmand.
The commands with their abbreviation and options are described below.
clear (cl)
Resets the commands buffer.
config_update (cu) [on|off] (default is on)
Propagates the configuration changes and requests the application servers to take in the changes in the configuration.
help (h) [command]
Without extra argument: prints a list of all the commands.
With a command argument: prints the synopsis of the command.
list (l)
Displays the commands buffer.
If the buffer is empty, the message " WARNING: No command in buffer." is displayed.
newcopy (n) {p|s} object_name 1 object_name2 ...
Enters a newcopy command for screen or program object types.
perform (p)
Performs the commands submitted to the server and clears the commands buffer.
If the buffer is not empty, the buffer container is displayed and a confirmation is required.
If the submission fails, the message " Perform cancelled." is displayed, and the error is logged into the USERLOG.
quit (q)
Quits this session.
If the buffer is not empty, the buffer container is displayed and a confirmation is required.
sysid (s) {*:SSSS}
By default, the administration commands are transmitted to all servers in the ART CICS system. The configuration is global. For the newcopy, you may want to limit it to some specific servers. The sysid command is used to limit the command effect to the servers with a specific SYSID.
Limitations
The transactions.des TRANCLASS parameter cannot be changed dynamically.
kixrpt (1)
Name
kixrpt.shARTKIX transaction/command report utility.
Synopsis
kixrpt.sh [-d "YYYY/MM/DD[hh:mm:ss]"] [-D "YYYY/MM/DD[hh:mm:ss]"] [-c] trace
Description
kixrpt reports transaction/command timing statistics information, including total number of transactions/commands running in specified time slot, total time cost, the average running time, etc. For each transaction/command, such tool reports the details of running information: total number, total time cost, average time cost, failure count, etc.
kixrpt analyzes the standard output of ARTKIX servers to provide a summary of transaction / command processing time within the servers. The report shows the number of times dispatched and average elapsed time in milliseconds of each transaction / command in the covered period. kixrpt takes its input from the ARTKIX trace file or a directory (like KIX_TRACE_PATH) including trace files. The traces are valid by being set as below:
KIX_TRACE_LEVEL=1 (or higher level)
Options
kixrpt supports the following options:
-d "YYYY/MM/DD[ hh:mm:ss]"
Limits the start time. The default is no limitation.
-D "YYYY/MM/DD[ hh:mm:ss]"
Limits the end time. The default is no limitation.
-c
Generates the clear trace output instead of statistics report.
Example
1.
KIX_TRACE_LEVEL=1
TP_USER_TRACE=SID
TRACE_PATH=${APPHOME}/LOGS/traces
2.
After running some time, the statistic tool, kixrpt.sh, can be used to generate the report with given time slot.
$ kixrpt.sh -d 2012/06/21 -D 2012/06/22 $TRACE_PATH
3.
Listing 10‑7 provides the output example:
Listing 10‑7 kixrpt Output Example
Transactions:
------------------------------------------------------------
CPMI(10000)totalTime(2254147)avgTime(225)errNum(0)
------------------------------------------------------------
totals(10000)totalTime(2254147)avgTime(225)
 
Commands:
------------------------------------------------------------
KIX__LINK(10000)totalTime(1047970)avgTime(104)errNum(0)
KIX__DELETEQ_TS(20000)totalTime(9377)avgTime(0)errNum(0)
KIX__RETURN(20000)totalTime(1016)avgTime(0)errNum(0)
KIX__WRITEQ_TS(380000)totalTime(153888)avgTime(0)errNum(0)
KIX__ASSIGN(300000)totalTime(19702)avgTime(0)errNum(0)
------------------------------------------------------------
totals(730000)totalTime(1231953)avgTime(1)
 
Programs:
------------------------------------------------------------
TUX2CXD(10000)totalTime(1047970)avgTime(104)
------------------------------------------------------------
totals(10000)totalTime(1047970)avgTime(104)
 
System Transactions
Authentication Transactions
CESN
The CESN transaction uses MAPSET CSIGNON. The following MAPSET definition must be added to the MAPSET configuration file ${KIXCONFIG}/mapsets.desc if CESN transaction is required:
[mapset]
name=CSIGNON
filename="<${KIXDIR}>/sysmap/csignon.mpdef"
Using this default MAPSET definition, CESN supports a maximum eight-character password. If the following MAPSET definition is added to the MAPSET configuration file, CESN allows a maximum 32-characters password.
[mapset]
name=LSIGNON
filename="<${KIXDIR}>/sysmap/lsignon.mpdef"
If two MAPSET definitions are both added to the MAPSET configuration file, the default MAPSET definition CSIGNON is used. CESN, in this case, allows a maximum eight-character password.
The CESN transaction ignores the UCTRAN setting in the TYPETERM configuration file. The username and password entered from terminal are always case-sensitive, no matter which UCTRAN value is set.
CESF
No special configuration is required for CESF transaction.
CSGM
Oracle Tuxedo Application Runtime for CICS provides a default "Good Morning" transaction CSGM, which can be added to the Transaction configuration file ${KIXCONFIG}/transactions.desc.
The default CSGM transaction uses MAPSET ABANNER. So the following MAPSET definition must be added to the MAPSET configuration file if the default CSGM transaction is configured:
[mapset]
name=ABANNER
filename="<${KIXDIR}>/sysmap/abanner.mpdef"
 

Copyright © 1994, 2017, Oracle and/or its affiliates. All rights reserved.